COPYRIGHT (C) 1984-2007 MERRILL CONSULTANTS DALLAS TEXAS USA
CHANGE 11.11
=========================member=CHANGE11================================
/* COPYRIGHT (C) 1984-1994 MERRILL CONSULTANTS DALLAS TEXAS USA */
This is Production MXG Version 11.11, dated Mar 26, 1994.
MXG Production 11.11 was dated Mar 26, 1994, thru Change 11.361
MXG Newsletter TWENTY-FIVE, Mar 26, 1994, thru Change 11.347
Early PreRelease 11.11 was dated Mar 9, 1994, thru Change 11.338
MXG PreRelease 11.10 was dated Feb 14, 1994, thru Change 11.316
MXG PreRelease 11.09A was dated Jan 10, 1994, thru Change 11.290
MXG PreRelease 11.09 was dated Dec 17, 1993, thru Change 11.266
Early PreRelease 11.08 was dated Nov 1, 1993, thru Change 11.238
MXG PreRelease 11.07 was dated Oct 4, 1993, thru Change 11.203
Early PreRelease 11.07 was dated Oct 1, 1993, thru Change 11.192
MXG PreRelease 11.06 was dated Sep 1, 1993, thru Change 11.164.
MXG PreRelease 11.05 was dated Aug 10, 1993, thru Change 11.150.
MXG PreRelease 11.04 was dated Aug 10, 1993, thru Change 11.149.
MXG Newsletter TWENTY-FOUR, Aug 2, 1993, thru Change 11.140.
MXG PreRelease 11.03 was dated Jul 26, 1993, thru Change 11.140.
MXG PreRelease 11.02 was dated Jul 6, 1993, thru Change 11.126.
MXG PreRelease 11.01 was dated May 20, 1993, thru Change 11.084.
Early PreRelease 11.01 was dated May 15, 1993, thru Change 11.068.
Prior Production 10.10 was dated Mar 15, 1993.
Member CHANGES repeats sections I, VIII, and IX of MXG Newsletter 25,
but you MUST also read MXG Newsletter 25 in member NEWSLTRS for major
technical discussions that are not repeated herein.
Contents of member CHANGES
0. HOT FLASH NOTES AFTER NEWSLETTER TWENTY-FIVE WAS PRINTED
I. MXG Software Production Version 11.11, dated March 26, 1994
VIII. Incompatibilities and Installation of MXG 11.11.
IX. Documentation of MXG Software.
X. Changes Log
0. HOT FLASH NOTES AFTER NEWSLETTER TWENTY-FIVE WAS PRINTED
OPC Version 1.2.0 had INPUT STATEMENT EXCEEDED error, new subtype that
is now supported, and still exposure. See Change 11.356.
MXG Tape Mount and Allocation Monitor now works at 2 out of 3 sites.
See Change 11.358.
Problem with zeroes in Cache RMF Reporter Records (Newsletter 25 MVS
Techical Note) is a fixed problem, but maybe not just due to RMF. I
missed phone call with all the details! Fax if you need update.
I. MXG Software Production Version 11.11, dated March 26, 1994, was
shipped with MXG Newsletter TWENTY-FIVE.
Critical notes about MXG Version 11.11:
- Products that require MXG 11.11 because of incompatible records:
DB2 Version 3.1.0.
Landmark's CICS/ESA Version 1.1.
LEGENT's TPX Release 3.5.
Software AG's COM-PLETE Release 4.5
Sterling's NDM, now Connect Direct 1.7.01.
- ANALDB2R users must use MXG 11.11 because of report corrections.
- You MUST use member CONFIG from this MXG SOURCLIB or you will get
many strange errors! (If you are still stuck at SAS 6.06, see Change
11.187 and use CONFIG06). Member CONFIG executes %VMXGINIT with
INITSTMT='%INCLUDE SOURCLIB(VMXGINIT); %VMXGINIT;' to initialize the
internal macro variables introduced in Change 11.150.
- If any of these members exist in your USERID.SOURCLIB(s) libraries:
ASUMDBDS ASUMDB2A ASUMDOS ASUMHPCS ASUM70PR
DAILYDSN GRAFDB2 GRAFLPAR TRNDDB2A
or if you use %VMXGSUM in your own report/summarization programs,
then you MUST read the incompatibility details in Section VIII and
in Change 11.309 and you will need to re-tailor your changes.
- MXG 11.11 requires SAS 6.08 at maintenance TS407 plus Zap Z6088203
Previously, I also said Z6086442 was required, but SAS Technical
Support corrected me; Z6086442 is already included in TS407.
MXG Version 11.11 was shipped along with Newsletter TWENTY-FIVE, and it
should be installed immediately as it provides these major enhancements:
These major enhancements were added in MXG 11.11 dated Mar 26, 1994
Support for STK's ICEBERG device user SMF record.
Support for Boole & Babbage CICS/Manager Type 110 Statistics records.
Support for Candle's Omegamon II for SMS user SMF record
Support for ISOGON's SoftAudit product's externalized files.
CICS/ESA Shutdown Statistics Report (DFHSTUP) now produced by MXG.
Sterling's NDM, now Connect Direct 1.7.01 incompatible changes.
Partial support for LEGENT's MIM Release 4.0.
Enhancements and corrections to ANALDB2R DB2PM-like reports.
Enhancements to VMXGSUM summarization routine.
Feedback that ASMIMSLG does not fail with IMS 4.1 log records.
These major enhancements were added in MXG 11.10 dated Feb 14, 1994
Support for IBM's OPC/ESA Release 2.1.
Support for LEGENT's NETSPY Release 4.4.
Support for CA's ACF2 Releases 6.0 and 6.1.
Support for Candle's Deltamon SMF record.
Performance improvements for VMXGSUM (used in most ANALxxxx members).
The ANALSMF "Simulator" analyzes SMF VSAM CI Size impact on your site.
These major enhancements were added in MXG 11.09A dated Jan 10, 1994
Support for Landmark CICS/ESA Version 1.1 (incompatible) records.
Summarization of Amdahl's APAF in ASUMAPAF.
Support for ZARA Release 1.1.
Corrections to ANALDB2R reports.
Performance enhancements in VMXGSUM execution.
These major enhancements were added in MXG 11.09 dated Dec 17, 1993
Support for DB2 Version 3.1.0 incompatible changes to DB2 SMF records.
Support for NPM Version 2.1.0.
Support for AS/400 Version 2.3 Performance Data.
Support for Memorex Telex LMS Version 2.17
Support for BatchPipes/MVS type 91 SMF record.
Support for Mobius' INFOPAC-RDS user SMF record.
Support for Integris UniKix records (both ASCII and Binary format).
Support for Novell Network Navigator User SMF record.
Support for Softwork's Performance Solution I/O Plus & Hiperload SMF.
Support for NETWISE RPC EXEC type 33 SMF record.
Performance enhancement of VMXGSUM algorithm
Utility to count type 110 records by application.
These major enhancements were added in MXG 11.08 dated Nov 1, 1993
Support for Amdahl APAF Version 2.1
Support for FOCUS MSO Release 6.8.
Support for IBM's ADSM subtype 14 type 42 SMF record.
CICS "Requested Reset Statistics" now processed into PDB.CICRRTRV.
These major enhancements were added in MXG 11.07 dated Oct 4, 1993
Support for DFSMSrmm (Removable Media Manager) two SMF records.
Support for DFSMSrmm Extract Files created by IBMs EDGHSKP utility.
Support for AS/400 Release 2.2, all records, labels, formats, etc.
Support for SAP's IMS log record type 'AE' for SAP IMS Accounting.
Support for AICorp Central Server SMF record.
Support for Type 42 Subtype 4 Concurrent Copy & Extended Sequential.
Support for Sterling's NDM, Network Data Mover SMF record.
Support for 4th Dimension's CONTROL-D Release 3.0.0 SMF record.
Support for NETVIEW APAR OY66237 change to TYPE37 SMF record.
Graphics enhancements for consistency, better pictures, in GRAFxxxx.
These major enhancements were added in MXG 11.06 dated Sep 1, 1993
Support for TCP/IP 2.2.1 APAR PN40511 (API Calls, FTP/TELNET Client)
Support for ASTEX Release 1.7 SMF record
Support for Software AG's COM-PLETE Release 4.54 SMF record
Support for Laser Access Corp's Optical Disk System's 3 SMF records
Support for LEGENT's SAR product User SMF record.
MXG 11.05 was a checkpoint version after Change 11.150.
MXG 11.04 was a checkpoint version before Change 11.150.
These major enhancements were added in MXG 11.04 dated Aug 20, 1993
Support for LEGENT's SAR product's User SMF record.
Support for Laser Access's Optical Disk System User SMF records.
Final (?) correction to ASUM70PR.
These major enhancements were added in MXG 11.03 dated Jul 26, 1993
Asynchronous Data Mover Facility APAR OY65142 for SMF type 30.
OMEGAMON/CICS VSAM,DLI,IDMS,ADABAS,SUPRA,DATACOM SPE QOC0553
These major enhancements were added in MXG 11.02 dated Jul 6, 1993
Support for VM/ESA Release 2.1.
Support for Top Secret Release 4.3.
Support for NPM APAR OY54370.
Support for RMF APAR OY64585.
Support for SAP Releases 4.3.J and 5.0.
Support for DOS/VSE POWER 5.1.
Support for OMEGAMON 2.60 Audit Record changes.
Support for APPC Deaccumulation APAR OY63634.
These major enhancements were added in MXG 11.01 dated May 20, 1993
Support for ZARA, The Tape Media Manager from Altai.
Support for SYNCSORT Release 3.5 SMF record.
Support for HMF, Host Monitoring Facility user SMF record.
Support for Corporate TIE user SMF record.
Support for STOPX37 Release 3.5 mis-documentation.
Enhanced ANALRMFR for RMF look-a-like reports from MXG.
Validation of Candle's ITRF (Omegamon/IMS Version 110).
Validation and correction of SMSDATA operand of DCOLLECT
Each of those enhancements are described in the Change Log, below.
Table of availability dates for the IBM products and MXG version:
Availability MXG Version
Product Name Date Required
RMF 4.1.2 (for MVS/ESA 3.1.3) Sep 7, 1990. 8.8
RMF 4.2 (for MVS/ESA 4.1) Oct 26, 1990. 8.8
MVS/ESA 4.1 Oct 26, 1990. 8.8
MVS/ESA 4.2 Mar 29, 1991. 9.9
RMF 4.2.1 (for MVS/ESA 4.2) Mar 29, 1991. 9.9
MVS/ESA 4.2.2 Aug 1991. 9.9
RMF 4.2.2 (for MVS/ESA 4.2.2 Aug 1991. 9.9
MVS/ESA 4.3 Mar 23 1993. 10.10
RMF 4.3.0 (for MVS/ESA 4.3) Mar 23 1993. 10.10
MVS/ESA 5.1.0 ??Summer 1994?? 12.??
CICS/ESA 3.2 Jun 28, 1991. 9.9
CICS/ESA 3.3 Mar 28, 1992. 10.01
DB2 2.2.0 1990 8.8
DB2 2.3.0 Oct 28, 1991. 10.01
DB2 3.1.0 Dec 17, 1993. 11.09
VM/ESA 1.1.1 Dec 27, 1991. 10.1
VM/ESA 2.0 Dec 23, 1992. 10.4
VM/ESA 2.1 Jun 27, 1993. 11.02
These products still had open problems or were potentially incorrect
when MXG 11.11 was built. Contact Merrill for current status.
TYPEZRB - RMF III VSAM file for MVS/ESA 4.2 and 4.3 is not correct.
Huron - Huron SMF record is not supported yet; no sample data SMF
data was provided, and the printed DSECTs were massive and
needed in machine readable form. Planned for 2nd quarter.
EPIC - LEGENT has not provided the format of their tape catalog;
instead, they want you to use the output of their extract
program, which means double processing and kludgy coding.
Nothing planned until LEGENT supplies needed formats.
NDM - Connect/Direct has only been validated for some records.
See Change 11.326.
VIII. Incompatibilities and Installation of MXG 11.11.
1. Incompatibilities
a. MXG's summarization member, %VMXGSUM was changed incompatibly, but
it should affect only the very small number of (sophisticated) users
who have tailored MXG summarization/trending members:
If any of these members exist in your USERID.SOURCLIB(s) libraries:
ASUMDBDS ASUMDB2A ASUMDOS ASUMHPCS ASUM70PR
DAILYDSN GRAFDB2 GRAFLPAR TRNDDB2A
or if you use %VMXGSUM in your own report/summarization programs,
then you MUST read the details in Change 11.309 and you will need to
re-tailor your changes.
The incompatibility is somewhat obscure; to reduce CPU time and to
minimize temporary DASD space used during summarization, %VMXGSUM
now determines which variables are needed, and keeps only the needed
variables from the input data set. The problem arises only if you
use the INCODE= parameter (it lets you insert SAS code into the
summarization logic, and is used in those nine members), and even
then, only if you reference variables in your INCODE= logic that are
not going to be kept in the output summarized dataset. In that rare
case, you must list those un-kept variables in the new KEEPIN= parm.
The above members in MXG 11.11 contain the needed KEEPIN= statement.
(If you overlook this note, you still should detect the problem in
your testing, because you will normally see UNINITIALIZED VARIABLE
messages on the SAS log to alert you to your error!)
b. Make sure you are using the CONFIG member from the MXG 11.11 library
in your JCL, either with the MXGSAS JCL Procedure, or on your EXEC:
// EXEC SAS,CONFIG='MXG.V1111.SOURCLIB(CONFIG)'
You will get many, strange syntax errors (ERROR 180 or 200) if you
do not use the MXG 11.11 CONFIG member.
If you are migrating to MXG Version 11.11 from MXG Version 9.9 or
earlier, AND you have tailored your MXG installation (with EX... or
IMAC.... members), you must read the MXG 10.10 compatibility section
in member CHANGESS; find the text "member=CHANGE10" and read on!
c. MXG Version 11.11 requires SAS Version 6.08 at maintenance TS407,
plus SAS Zaps Z6088203 and Z6086442 for MVS and CMS. For WINDOWS,
SAS 6.08 at TS407 is required. For all UNIX, except for AIX, SAS
6.09 is required. For AIX, the second maintenance to 6.09 will be
required. For OS/2, SAS 6.10 will be required. (Both AIX and OS/2
do not currently properly support VBS record processing; their fixes
are due out this summer.) MXG has been tested error-free with the
above SAS versions, and I strongly suggest you ensure that your SAS
System is at the above level of SAS maintenance. (While most of MXG
may execute successfully with lower maintenance, you may encounter
known errors if you are not at the above level.)
d. Observation counts may change in PDB.JOBS and PDB.NJEPURGE because
of Change 11.226. More observations may be seen in PDB.TYPE74 due
to Change 11.170.
2. Installation and re-installation procedures are described in detail:
in member INSTALL, and sample JCL is in member JCLINSTL. Summary:
a. Install member MXGSAS as JCL Procedure MXGSAS in your PROCLIB.
b. Allocate a 83-cyl PDS: MXG.V1111.MXG.SOURCLIB, and use IEBUPDTE
to read the MXG tape to create the 2000+ member Source Library.
c. Allocate a 1-cyl PDS: MXG.V1111.USERID.SOURCLIB for your site
"Installation Tailoring" Source Library. Installation specific
tailoring (like telling MXG your shift hours, which performance
groups are TSO, CICS, etc.) is done by copying and modifying MXG
source members into V1111.USERID.SOURCLIB.
d. Allocate a 1-cyl SAS Data Library: MXG.V1111.MXG.FORMATS and
execute SAS to create the library of Formats required by MXG.
e. If this is the initial install of MXG, tailor these members into
your MXG.V1111.USERID.SOURCLIB tailoring library:
IMACACCT (Account Length),
IMACSHFT (Shift Definitions),
IMACWORK (Performance Group to Workload mapping), and
IMACSPIN (for BUILDPDB).
Each IMAC member is self-documenting, and IMACAAAA is the index
of all of the IMACs. You should at least scan IMACAAAA to see
the acronyms MXG uses for the many products MXG supports.
e. If re-installing MXG, copy your existing USERID.SOURCLIB library
members into the MXG.V1111.USERID.SOURCLIB. Then compare your
IMACs with those that were changed (see the alphabetical list of
changed members in member CHANGES). If any members in your
MXG.V1111.USERID.SOURCLIB were changed, you must reinstall your
site's tailoring for that IMAC, starting with the IMAC member
from the MXG 11.11 Source Library.
f. EDIT and submit member JCLTEST6 to verify that your tailoring
did not create any errors.
g. EDIT and submit JCLPDB6 to create a Daily PDB for testing. Or
use the TYPE.... members to process specific data sources, use
the ANAL.... members for report examples, the GRAF.... members
for SAS/GRAPH reports.
You have now installed MXG 11.11 in its own set of libraries. When
parallel testing is complete and are ready to implement MXG 11.11
in production, rename your three current MXG Production Libraries
(MXG.MXG.SOURCLIB, MXG.USERID.SOURCLIB, and MXG.MXG.FORMATS) to
(MXG.BACK.MXG.SOURCLIB, MXG.BACK.USERID.SOURCLIB, MXG.BACK.MXG....)
and rename the MXG.V1111.x.y libraries to their Production names!
Again, detailed installation instructions are in member INSTALL
Always read comments in the CHANGES member for compatibility issues, as
well as for any last minute changes.
Whenever you install changes or test a new version of MXG (or even your
own reports), be extra careful to look on the SAS log for any real error
conditions. Search for all occurrences of "ERROR:" and "ERROR :" and
"UNINITIALIZED" and "NOT CATLGD", as they may indicate a serious error.
A PROC PRINT and a PROC MEANS of each new MXG-built SAS dataset can help
you to understand their contents, and should be used to examine any
unusually large, negative, or suspicious values. Print all variables in
the dataset, and read the variable's descriptions in its ADOC member.
IX. Documentation of MXG Software.
Member CHANGES identifies the Version and Release of MXG Software, and
describes all changes made in that Release. The text of each change
names the members that were added or altered by that change. Member
ChangeS is designed to be read online (with SPF BROWSE), so that you can
search for specific product name references (CICS, MVS/ESA, etc.), or
the MXG member name or product acronyms.
Member CHANGESS contains ALL changes in ALL versions of MXG.
Member NEWSLTRS contains the text of all newsletters. You can search
NEWSLTRS for product name or acronym to find the technical notes, APARs,
etc., from all MXG newsletters. Since the Change Log portion of each
newsletter is in member CHANGESS, they are not repeated in NEWSLTRS.
The MXG Technical Newsletter is typically published twice a year, with
one printed copy sent to each licensed site, and it describes changes
and enhancements to the software, provides APARs and PTFs affecting MXG
users, and provides technical papers of interest to MXG users.
Member DOCVER lists alphabetically ALL datasets and variables that are
built by this MXG Software Version.
Members DOCVERnn are the "delta-documentation" between MXG versions, and
list only those datasets and variables that were added/deleted/changed
by version "nn".
Members ACHAPxxx are the text chapters from the 1984 MXG Guide and the
1987 MXG Supplement, to which the text of newsletters and changes has
been added. At present, these chapters are very rough; in a few cases
the chapter has actually been completed and revised, but most of these
chapters delivered in MXG 11.11 are little more than a concatenation of
the original text, and there are no figures nor tables. This is clearly
work in progress, but at least the old books are now machine readable!
When all 42 chapters are completely revised and updated in the source
library, I will decide if any will also be made available in printed
form, but the primary source of all future documentation will be the MXG
source library itself, which can now be updated when changes occur!
Members ADOCxxxx are what were in Chapter FORTY, and should be the first
place you look for information about MXG variables and/or datasets. The
ADOCxxxx members alphabetically describe each dataset and all variables
that are created by product xxxx, the instructions on how to enable that
product, bibliography of the vendor documentation, sample PROC PRINT and
PROC MEANS of real datasets, references to MXG reports that use these
datasets, and the MXG member names that you use to process that product.
There is an IMACxxxx member for every product supported by MXG. Once
you know the xxxx suffix for a product, you then know the names of all
of the MXG members for that product:
IMACxxxx - Defines record IDs, and "_K,_L" macros for product xxxx.
ADOCxxxx - "Chapter FORTY" style dataset and variable documentation.
VMACxxxx - The "real" source code member, often extensively commented.
TYPExxxx - Standalone member to test or process product xxxx records.
ASUMxxxx - Summarization example (only for some products)
TRNDxxxx - Trending example (only for some products)
ANALxxxx - Reporting/analysis example (only for some products)
GRAFxxxx - SAS/GRAPH report example (only for some products)
EXyyyzzz - OUTPUT exit for each dataset. There can be more than one
dataset per product. The EX member name suffix yyyzzz is
the same as the suffix of "_L" and "_K" macros defined in
IMACxxxx for the product. See further discussion under
"Using the MXG Exit Facilities" in ACHAP33.
Member IMACAAAA is an index of all IMACs, and is the best place to begin
to find what xxxx suffix Merrill chose for which product! You can often
find additional documentation by searching members NEWSLTRS or CHANGESS
for the xxxx suffix.
Finally, remember that MXG is source code, so you can often find your
answer by BROWSING the source members, especially the VMACxxxx, ANALxxxx
members. The MXG Variable name is often the DSECT's field name, and if
not, the vendor's field name is often in adjacent comments in the INPUT,
so you can cross reference to the vendor's documentation of their data!
X. 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 of the MXG SOURCLIB will always be more accurate than
the printed changes in a Newsletter, because the software tapes are
created after the newsletter is sent to the printer!
Member CHANGES always identifies the actual version and release of
MXG Software that is contained in that library.
The actual code implementation of some changes in MXG SOURCLIB may be
different that described in the change text (which might have printed
only the critical part of the correction that can be made by paper).
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 since MXG 10.10:
Member Change Description
All 11.150 Rewrite to support execution under ASCII SAS versions
ANALCISH 11.329 CICS/ESA DFHSTUP Shutdown Statistics Reports added.
ANALDASD 11.288 Sample prime-time cross-system DASD report.
ANALDB2R 11.007 Fails with PDB=SMF if account reports suppressed.
ANALDB2R 11.036 Suspension counts twice actual value.
ANALDB2R 11.037 Total Read IOs miscalculated on Statistics Summary
ANALDB2R 11.042 DB2 PMACC02 count of OPENS actually counted FETCHES.
ANALDB2R 11.043 DB2 PMSTA02 count of SUSPENDS usually zero.
ANALDB2R 11.143 OVERFLOW HAS OCCURRED, OUT OF MEMORY errors.
ANALDB2R 11.237 ANALDB2R can now report from a PDB on tape.
ANALDB2R 11.286 Continued enhancement and error corrections.
ANALDB2R 11.330 DB2 Audit Detail Report Completion Code still wrong.
ANALDSET 11.048 ERROR 455-185 for dataset TYPE30OM.
ANALDSET 11.291 TYPE64 records now sorted consistent with non-VSAM.
ANALRACF 11.260 UNINITIALIZED variable due to SAS Usage note 6886.
ANALRMFR 11.024 Report fails with PDB=SMF, works with PDB=PDB.
ANALRMFR 11.069 Continued enhancement of RMF look-a-like reports.
ANALRMFR 11.231 Additional RMF report enhancements and corrections.
ANALRMFR 11.256 Correction of CPU percentages and type 74 reports.
ANALSMF 11.300 The "Simulator" analyzes SMF VSAM CI Size impact.
ASMIMSLG 11.157 IMS log processing type 36 changed.
ASMTAPES 11.360 MXG Tape Mount and Allocation Monitor works 2/3.
ASMTMNT 11.154 0C4 abend in MXGTMNT at one site.
ASMVTOC 11.257 No output records under MVS/ESA 4.2 and earlier.
ASUM70PR 11.022 PDB.RMFINTRV may be corrupted by ASUM70PR.
ASUM70PR 11.027 LP0MGTTM not in RETAIN list (affects only MDF)
ASUM70PR 11.041 ASUM70PR new variables, and mini-tutorial.
ASUM70PR 11.087 LP0MGTTM (Amdahl MDF only) incorrect.
ASUM70PR 11.145 ASUM70PR still wrong in MXG 11.03.
ASUMAPAF 11.290 Summarization of MDF APAF records similar to PR/SM.
ASUMDB2A 11.038 QTXAIRLM omitted from SUM= list
BUILD006 11.320 PDB logic enhanced for APPC tasks (no purge record).
BUILDPDB 11.025 Building your PDB on tape.
BUILDPDB 11.089 Purge records lost if PRPRTY=4-7 or 12-15.
BUILDPDB 11.226 JES2 NJE Purge records for JT were mis-recognized.
BUILDPDB 11.228 Open Edition/MVS (OMVS) TYPE30OM added to PDB.
BUILDPDB 11.269 PDB.JOBS ACCOUNTn/RESTARTS wrong for MULTIDD jobs.
BUILDPDB 11.320 PDB logic enhanced for APPC tasks (no purge record).
CHANGESS 11.074 New member CHANGESS contains ALL changes ALL Versions
CICINTRV 11.224 CICS "Requested Reset Statistics" now processed.
CLTIMER 11.035 STOP statement required by SAS Version 6.
CONFIG 11.306 For MVS, MEMSIZE=32MB now default value.
CONFIG07 11.129 SAS Error 76-322 with numbered + unnumbered lines.
DAILYDSN 11.076 Typos misspelled output datasets.
DIFFDB2 11.282 New dataset PDB.DB2STATS now created for reports.
DIFFHSM 11.019 Member did not use the "_L" macro names.
Doc 11.013 Change 10.175 typo, two _KTY0 should be _LTY0
FMXGUCBL 11.088 Archaic UCBL function corrected.
GRAFLPAR 11.079 Error "OUT OF MEMORY" due to SAS Error 6719.
GRAFTRND 11.216 Not all workload data was plotted if workload unused.
GRAFWORK 11.311 Workload graphs enhanced with memory frames in use.
GRAFxxxx 11.173 Enhancements, common structure for GRAFxxxx members.
IMACACCT 11.104 "VARIABLE SACCT1 NOT FOUND" can occur.
IMACCICS 11.224 "CICRRTRV NOT FOUND" errors using old IMACCICS
IMACICBB 11.347 Support for Boole & Babbage CICS Manager Statistics.
IMACICDL 11.268 Omegamon CICS/ESA type 110 may have wrong DL/I counts
IMACICSA 11.110 Support for SAP Releases 4.3.J and 5.0.
IMACICSA 11.148 SAP Release 4.3 requires one change to MXG.
IMACICSA 11.211 CICS SAP variables STCDB1-STCDB5 should be CHAR.
IMACPDB 11.155 ACCOUNTn variables no longer limited in IMACPDB.
IMACPDB 11.214 JES3 variable CLASS added to JES3 PDB.JOBS.
IMACPDB 11.258 Variables ACTDLYTM,DSPDLYTM,RESDLYTM now in PDB.JOBS
JCLIMSLG 11.109 MXG 10.10 had wrong JCL in this example JCL member.
JCLTEST 11.012 SAS 5.18 WORK.#DIRMACR is out of space condition.
JCLTEST6 11.093 0C4 ABEND in SASXKERN if IBM exit IFGOEXOB used.
MONTHBLD 11.040 Error "DATASET TAPEMNTS NOT SORTED".
MONTHBLD 11.206 DATA SET TAPEMNTS IS NOT SORTED error.
Many 11.302 Additional ASCII/EBCDIC differences resolved.
RMFINTRV 11.008 TYPE74 tape counts in AVGRSPMS, DEVACTTM, etc.
RMFINTRV 11.264 Variable PGPERBLK in RMFINTRV is incorrect.
SPIN 11.184 SPIN library can fill if Change 11.060 not installed.
TRND70 11.240 Trended variables READY12-READY15 have wrong value.
TRND71 11.222 Variable VIO value incorrect in TRND71.
TRNDDB2A 11.038 QTXAIRLM omitted from SUM= list
TRNDVMXA 11.235 VM/ESA Trending had logic errors.
TRNDxxxx 11.227 Trending now includes the MVS/ESA 4.3 variables.
TYPE102 11.085 Variables QW0145SC/QW0145LL not input.
TYPE102 11.107 IFCID 53 and 58 records may have been dropped.
TYPE110 11.023 Omegamon V550 APAR QOC0451/QOC0534 bad record error.
TYPE110 11.080 STARTIME in CICINTRV dataset is actually ENDTIME.
TYPE110 11.138 Skip over SAP Journal Records circumvention.
TYPE1415 11.266 Variable TEMP in dataset TYPE1415 may be misset.
TYPE28 11.116 Support for NPM APAR OY54370.
TYPE28 11.246 Support for NPM Version 2.1.0
TYPE30 11.002 INVALID OMVS TRIPLET message, no observations.
TYPE30 11.003 Type 30 Interval INTBTIME/INTETIME wrong in MVS 4.3.
TYPE30 11.004 Variable DSSIZHWM is incorrect.
TYPE30 11.033 Small negative values for ACTDLYTM.
TYPE30 11.060 JELAPSTM and others large (positive or negative).
TYPE30 11.126 Type 30 APPC fields accumulation corrected OY63634.
TYPE30 11.140 Asynchronous Data Mover read/writes in APAR OY65142.
TYPE30 11.199 Variables INTBTIME/INTETIME off by 100 seconds.
TYPE30 11.229 GMT Offset was still wrong sometimes, by 100 seconds.
TYPE33 11.243 Support for NETWISE RPC EXEC type 33 SMF record.
TYPE37 11.001 INPUT STATEMENT EXCEEDED RECORD LENGTH
TYPE37 11.031 Undocumented LAN variables BRFSMADR BRFSMNAM added.
TYPE37 11.119 INPUT STATEMENT EXCEEDED RECORD LENGTH.
TYPE37 11.202 Support for NETVIEW APAR OY66237 (Hardware Log).
TYPE39 11.280 TYPE39_8 variables all incorrect.
TYPE42 11.021 New TYPE42DS has GMT values in INTERVAL record.
TYPE42 11.179 Support for Concurrent Copy & Extended Sequential DS.
TYPE42 11.235 Support for IBM's ADSM subtype 14 type 42 SMF record.
TYPE42 11.325 TYPE42 subtype 6 STOPOVERs if VSAM SMF data is read.
TYPE57 11.215 Type 57 ESS variables non-blank if no ESS installed.
TYPE60 11.203 Storage and Data Class missing in NVR TYPE60 records.
TYPE6156 11.223 INVALID DATA for OWNEXPDT corrected.
TYPE7072 11.016 TYPE72MN dataset contains only one PERFGRP.
TYPE7072 11.152 TYPE70 dataset now supports CPUIDs of 0 thru 15.
TYPE7072 11.229 GMT Offset was still wrong sometimes, by 100 seconds.
TYPE7072 11.265 Boole CMF Type 72 Subtype 2 INPUT STATEMENT EXCEEDED.
TYPE7072 11.275 IBM APAR OY67002 corrupts TYPE70,TYPE70PR,ASUM70PR
TYPE72 11.177 SERVICE can be zeroed if it overflows ==> zero obs!
TYPE72MN 11.171 Zero obs in TYPE72MN for MVS/ESA 4.2 or earlier.
TYPE73 11.015 TYPE73 contains observations for dummy CHPIDs
TYPE73 11.102 Zero observations in TYPE73.
TYPE73 11.114 PNCHANBY (EMIF Partition Channel Busy) added.
TYPE73 11.195 Variable PNCHANBY propagated into inactive records.
TYPE74 11.170 TYPE74 not output if only allocated but not used.
TYPE80 11.117 Support for Top Secret Release 4.3.
TYPE80 11.207 Support for TOP-SECRET records written to log.
TYPE80A 11.017 INPUT STATEMENT EXCEEDED error.
TYPE80A 11.054 TYPE80A fails with INPUT STATEMENT EXCEEDED.
TYPE90 11.158 TYPE90 variable ACTIVE renamed to ACTIVEMN.
TYPEACF2 11.315 Support for CA's ACF2 Releases 6.0 and 6.1.
TYPEAICS 11.180 Support for AICorp Central Server SMF record.
TYPEAPAF 11.225 Support for Amdahl APAF Version 2.1
TYPEAPAF 11.267 APAF V2.1 dataset APAFCHAN was trashed.
TYPECIMS 11.073 INVALID VALUE FOR TH corrected.
TYPECOMP 11.156 COM-PLETE Release 4.5 SMF record supported.
TYPECOMP 11.209 Variable ULOGCPUT incorrectly input.
TYPECTLD 11.174 Support for 4th Dimension's CONTROL-D Release 3.0.0.
TYPEDB2 11.005 INVALID 3rd ARGUMENT IN SUBSTR, variable JOB blank.
TYPEDB2 11.006 Variable QDSTQDBT is incorrect.
TYPEDB2 11.050 DB2ACCT variable NETSNAME incorrectly padded.
TYPEDB2 11.255 Support for DB2 Version 3.1 incompatible changes.
TYPEDCOL 11.057 DCOLLECT SMSDATA (SMS constructs) cause STOPOVER.
TYPEDCOL 11.151 Variables DCUSYSID/DCUTMSTP not kept in constructs.
TYPEDLMN 11.308 Support for Candle's Deltamon SMF record.
TYPEDMON 11.162 Support for LEGENT's ASTEX Release 1.7.
TYPEDOS 11.106 Support for DOS/VSE POWER 5.1.
TYPEDOS 11.149 Variables STARTIME/STOPTIME may be wrong.
TYPEEDGR 11.190 Support for DFSMSrmm Extract Files (EDGHSKP utility).
TYPEEDGS 11.189 Support for DFSMSrmm SMF Audit and Security records.
TYPEEDGS 11.209 Several MVT... variables incorrectly input.
TYPEF127 11.210 FACOM pseudo-RACF type 127 FUNCTION CHAN IS UNKNOWN.
TYPEFOCU 11.219 Support for FOCUS MSO Release 6.8.
TYPEHMF 11.049 Support for HMF, Host Monitoring Facility product.
TYPEHSM 11.078 New HSM dataset HSMFSRBO, IMACHSM changed.
TYPEICE 11.340 Support for STK's ICEBERG SMF record.
TYPEIMS 11.181 Support for SAP's IMS log record type 'AE'.
TYPEIPAC 11.252 Support for Mobius' INFOPAC-RDS user SMF record.
TYPEMEMO 11.032 New variables TRANTIME TRANCOST added.
TYPEMIM 11.317 Partial support for LEGENT's MIM Release 4.0.
TYPEMON8 11.230 INVALID ARGUMENT TO FUNCTION MDY TIESDATE INVALID.
TYPEMON8 11.270 Support for Landmark CICS/ESA Version 1.1 INVALID DO.
TYPEMON8 11.278 ERROR3.LANDMARK.MONITOR due to invalid record.
TYPEMON8 11.327 INVALID DATA FOR TIAPREQ with MXG 11.0x-11.10.
TYPENDM 11.175 Support for Sterling NDM Network Data Mover 1.4.0.
TYPENDM 11.326 Sterling's NDM, now Connect Direct 1.7.01, incompat!
TYPENSPY 11.009 INVALID ARGUMENT TO FUNCTION DATEJUL error.
TYPENSPY 11.029 Variable SNITIME incorrect.
TYPENSPY 11.130 LEGENT LANSPY #DGL249 circumvention.
TYPENSPY 11.159 NETSPY fix changed again by LEGENT.
TYPENSPY 11.316 Support for LEGENT's NETSPY Release 4.4.
TYPEODS 11.147 Support for Laser Access Corp's Optical Disk System
TYPEOMAU 11.092 Omegamon 2.60 Audit Record moved OMSUBSID.
TYPEOMCI 11.115 OMEGAMON V550 SMF record INPUT STATEMENT EXCEEDED.
TYPEOMCI 11.136 OMEGAMON/CICS VSAM,DLI,ADABAS,IDMS,SUPRA,DATACOM.
TYPEOMCI 11.313 OMEGAMON user SMF record INPUT STATEMENT EXCEEDED.
TYPEOMSM 11.332 Support for Candle's Omegamon II for SMS user record.
TYPEOPC 11.122 Variables added to OPC24_6 and OPC24D_C datasets.
TYPEOPC 11.304 Support for OPC/ESA Release 2.1.
TYPEPOOL 11.141 INPUT STATEMENT EXCEEDED LENGTH with POOL/DASDSMF.
TYPEPRFS 11.262 Support for Softworks' Performance Solution SMF data.
TYPEQAPM 11.166 Support for AS/400 Release 2.2, all records now!
TYPEQAPM 11.254 Support for AS/400 Version 2.3 Performance Data.
TYPEQAPM 11.319 AS/400 system name AS400SYN was blank.
TYPESAR 11.146 Support for LEGENT's SAR product SARSRQU3 SMF record.
TYPESFS 11.250 Xerox SFS accounting record INVALID ARGUMENT error.
TYPESFTA 11.321 Support for ISOGON's SoftAudit externalized files.
TYPESTC 11.124 Missing values for several variables corrected.
TYPESYNC 11.056 Support for SYNCSORT Release 3.5 new variables.
TYPETAO 11.034 "INVALID DATA FOR TAOSTYP" messages.
TYPETCP 11.028 TCP/IP addresses reformatted.
TYPETCP 11.163 Support for TCP/IP 2.2.1 APAR PN40511 new fields.
TYPETPX 11.167 Support for LEGENT's TPX Release 3.5 (incompatible).
TYPEVM 11.113 Support for VM/ESA Release 2.1 Accounting record.
TYPEVMXA 11.047 VM/ESA "UNEXPECTED/INVALID CONTROL RECORD" message.
TYPEVMXA 11.112 Support for VM/ESA Release 2.1 Monitor records.
TYPEVMXA 11.142 VM/ESA duration variables could be truncated.
TYPEVMXA 11.261 VXSYTCPU dataset variable LCUCLPTM not kept.
TYPEVVDS 11.103 Blank values for SMS Storage, Data, etc., Classes.
TYPEVVDS 11.204 Variable VVRBSENM can be blank.
TYPEX37 11.070 STOPX37 Release 3.5 records incorrectly documented.
TYPEX37 11.091 Variable MESSAGE not decided in STOPX37 Rel 3.5.
TYPEX37 11.133 STOPX37 undocumented VOLSER,MSGCODE found.
TYPEZARA 11.059 Support for ZARA, The Tape Media Manager from Altai.
TYPEZARA 11.276 Support for ZARA Release 1.1 (incompatible)
UCICSCNT 11.244 Utility to count type 110 records by application.
VMACDB2H 11.242 DB2 variable NETSNAME can still mismatch CICSTRAN.
VMXGHSM 11.131 HSM BCDS dataset MCB incomplete, too few obs.
VMXGHSM 11.194 Not all observations output in dataset DSR.
VMXGHSM 11.259 HSM BCDS and MCDS data value errors.
VMXGSUM 11.281 Performance enhancement of MXG summarization
VMXGSUM 11.309 Execution improved by creating KEEP= for input.
VMXGSUM 11.309 INCOMPATIBLE exposure if you have tailored members.
VMXGVTOF 11.030 Variable DS4IVTOC was not kept.
WEEKBLD 11.040 Error "DATASET TAPEMNTS NOT SORTED".
WEEKBLD 11.206 DATA SET TAPEMNTS IS NOT SORTED error.
WEEKBLDT 11.172 WEEKBLD with no rewinds/remounts of WEEK tape.
Inverse chronological list of all Changes:
NEXTCHANGE: Version 11
Change 11.361 The offset for MCCAVSN was hardcoded and thus wrong for
VMXGHSM some levels of HSM; now, instead of INPUT +16, the logic
Mar 25, 1994 is OFFV=65+MCCNVSNO; INPUT @OFFV ....
Thanks to Gary Matney, Twentieth Century Investors, USA.
Change 11.360 The MXG Tape Mount and Allocation Monitor is a major
ASMTAPES extension to MXG's existing MXGTMNT Tape Mount Monitor.
Mar 24, 1994 Now, both tape mounts and tape allocation-deallocation
events are recorded in SMF so you can measure how long
each tape drive was used by what job. The new monitor is
provided in ASM source code in member ASMTAPES and works
fine at two sites (one using MVS/ESA 4.3 with MIM plus
SMS, the other is at MVS/ESA 4.2), but at MVS/ESA 3.1.3
site with both MIM and SMS, the new monitor program
either waits doing nothing or ABENDS gracefully. So if
you really need this monitor now, read Change 11.101 and
then assemble member ASMTAPES (it still creates program
named MXGTMNT) and check it out. I think it is highly
likely it is ok with MVS/ESA 4.2 or 4.3, but your
feedback as to where it works and when it doesn't will
help validate for everyboth. Since both MIM and SMS get
involved in allocation, they may or may not be the
trigger, but we are actively working on the SRB dumps to
understand and fix the program for all environments.
Thanks to Bill Fairchild, Royal Associates, USA
Thanks to Chuck Hopf, Primerica, USA
Change 11.359 If you modified the interval in ASUMTMNT, GRAFTMNT will
GRAFTMNT not correctly place the points on the graphs since it
Mar 24, 1994 was using the HOUR of the time as the axis. It now uses
the time at 3600 second intervals.
Thanks to Chuck Hopf, Primerica, USA
Change 11.358 ASUMHSM, TRNDHSM, GRAFHSM provide some ability to report
ASUMHSM on dataset movement caused by HSM. Since this can be a
TRNDHSM significant contributor to batch run times as well as TSO
GRAFHSM response, you may find these summarization, trending, and
Mar 24, 1994 graphical analysis of HSM useful.
Thanks to Chuck Hopf, Primerica, USA
Change 11.357 The second pair of variables named LLSNAFB/LLSNAFN are
VMACNSPY now named LLSNAEB/LLSNAEN, and LLSNAEB was added tothe
Mar 24, 1994 MGBYTES format (the "E" vars are for SNA over Ethernet).
Thanks to Warren Hayward, TJX, USA.
Change 11.356 Change 11.352 was revised after new iterations. Type 35
VMACOPC caused ABEND that was fixed, and subtype 'G' is now
Mar 24, 1994 supported. There are some spanned subtype 24 records
that MXG does not yet handle correctly; at present all I
could do was to recognize I missed a spanned record with
a message on the log; this only affects the OPC24xxx
data sets, and will be fixed soon. Fax if you need it.
Thanks to Randy Shumate, Mead Data Central, Inc.
Thanks to Maureen Walshe, IBM Nordiska Laboratoirer, SWEDEN.
Change 11.355 Change 11.351 was revised after the Mar 23 early tapes
BUILDPDB were sent. The WEEKBLD/WEEKBLDT/MONTHBLD members had not
Mar 24, 1994 been revised until Mar 24.
Change 11.354 CICS Statistics variables A21LUTTM and A21SNTTM were not
VMAC110 correct; a real value of 30 minutes was reported as only
Mar 24, 1994 .03 seconds.
==Changes thru 11.353 were in MXG 11.11 created March 23, 1994===
Change 11.353 LEGENT SAR records had a number of fields added in 1993
VMACSAR that are now supported in MXG. The maintenance has no
Mar 23, 1994 version/release, only Change #05- Change #9 in DSECT!
Thanks to Bob Mattingly, ARCO-EIS, USA.
Change 11.352 OPC records caused INPUT STATEMENT EXCEEDED RECORD LENGTH
EXOPC24X for TRLRCTYP=35 (delete all references to TRLPOS35). For
IMACOPC TRLRCTYP=24 MT0TYPE=9 (expand IF MT0TYPE NE 6 THEN to
VMACOPC IF MT0TYPE NE 6 AND MT0TYPE NE 9, and expand 7 LE MT0TYPE
Mar 23, 1994 LE 8 to 7 LE MT0TYPE LE 9). Support was added for the
Mar 24, 1994 MT0TYPE='G' (MT0TYPE is a number, so character 'G' =199)
which creates new dataset OPC24_G (not to be confused
with existing dataset OPC24D_5, which caused the new exit
and dataset macros to be EXOPC24X for OPC24_G dataset).
OPC support was revised after March 23 tapes shipped.
Thanks to Randy Shumate, Mead Data Central, USA
Change 11.351 RMF dataset TYPE77 is now automatically created by MXG's
BUILDPDB BUILDPDB/BUILDPD3 algorithms. TYPE77 reports ENQUE
BUILDPD3 conflicts and delays, and is expected in ANALRMFR for
BUILD001 replication of IBM RMF reports from MXG datasets. Logic
BUILD003 in WEEKBLD/WEEKBLDT/MONTHBLD now also expectes the TYPE77
BUILD518 dataset. Added Apr 18: This change is INCOMPATIBLE if
BUILD606 you have tailored BUILDPDB to add TYPE77 processing. See
WEEKBLD text of Change 12.013. This change was also incomplete
WEEKBLDT for JES3.
MONTHBLD
Mar 24, 1994
Change 11.350 Additional CICS Shutdown Reports were added. One problem
ANALCISH with Mode Table report (many pages, all zeros) with all
Mar 23, 1994 APPLIDs went away when a single APPLID was reported, but
this will be investigated as soon as data tape received.
Also, Last Reset time is different between IBM & MXG.
Thanks to Neil Ervin, Huntington Bank Service Company, USA.
Change 11.349 Variable SHEETPRN is now automatically added to PDB.PRINT
IMACPDB to count sheets printed.
Mar 22, 1994
Thanks to Jill Hansen, South Dakota Education, USA.
Change 11.348 Variable DVLNUCBA in dataset DCOLVL is now formatted as
VMACDCOL HEX8 and is LENGTH 5 (because it is numeric, five bytes
Mar 22, 1994 are required to store all possible hex digits).
Thanks to Al Rozewski, Parker Hannifin, USA.
==Changes thru 11.347 were printed in MXG Newsletter 25 dated 26Mar94===
Change 11.347 Support for Boole & Babbage CICS/Manager Statistics data
EXCICBBD in type 110 SMF record, subtype BB02 (which MXG sets back
EXCICBBF to SUBTYPE=2 for processing), Statistic STIDs:
EXCICBBG STID DATASET DESCRIPTION EXIT MEMBER VARS
EXCICBBL 200 CICSBBSI SIT EXCICBBS 52
EXCICBBR 201 CICSBBRC RCT EXCICBBR 47
EXCICBBS 202 CICSBBLT LT X EXCICBBL 55
FORMATS 203 CICSBBFC FCT EXCICBBF 57
IMACCICS 204 CICSBBGL GLOBAL PERFORMANCE EXCICBBG 37
IMACICBB 205 CICSBBDL DLI EXCICBBD 44
VMAC110 Those 6 datasets are created, but they will have zero obs
Mar 20, 1994 and only 15 variables unless you enable processing - see
member IMACICBB for enablement procedure and comments.
Adding this support uncovered several errors in field
alignment (three sets of CPU fields) that will be fixed
by Boole's PTF BPC2312 which you must request and install
for that dataset to be valid.
Thanks to ???, VW Wolfsburg, GERMANY.
Change 11.346 Netmaster 2.2 added new variable SMFNCUSR to type 39 data
VMAC39 that is now decoded and added the TYPE39 datasets. This
Mar 19, 1994 is the only reported change in Netmaster 2.2 records.
Thanks to Colin Bowen, Old Mutual, SOUTH AFRICA.
Change 11.345 TCP/IP addresses contained blanks when only one digit was
VMACTCP used for a node; now the blanks are stripped out by using
Mar 19, 1994 TELLOCAL=COMPRESS(TELLOCAL); on all addresses.
Thanks to Wanda Prather, Johns Hopkins University APL, USA.
Change 11.344 Support for CADAM V3R2 Statistical Data plus corrections
VMACCADM to MXG were provided by this user enhancement. See the
Mar 18, 1994 excellent notes at the beginning of the member.
Thanks to Jouke van Schepen, Fokker Aircraft BV, NETHERLANDS.
Change 11.343 NPM Type 28 NPMLANOD dataset (added in NPM Version 2) did
VMAC28 not decode CSL section correctly, causing INPUT STATEMENT
Mar 18, 1994 EXCEEDED with NPMSUBTY='A0'x, which is 4-bytes shorter
than the 'A1'x subtype. The four final fields LCSLRPTO-
LCSLRSFR are now input only for NPMSUBTY=0A1X and three
new variables LCSLPDUD,LCSLMFRD,LCSLURFR are instead
input for NPMSUBTY=0A0X.
Thanks to Pat McGuire, Texas Instruments, USA.
Change 11.342 CA-DISPATCH 5.1 corrupts READTIME in TYPE6 records - the
VMAC6 date can be 1-2 days in the future! CA stores a 01x in
Mar 18, 1994 the 1st byte of READTIME as a flag. A real read time of
Sep 22, 1994 00021CE8x (00:23:04) is corrupted to 01021CE8x (47:59:16)
and those 48 hours are added to midnight of read in date!
My guess was that CA decided that since 0083D600x is 24
hours, they could use the 1st byte of time for DISPATCH,
(just like CA uses the first byte of date for CA7), but
that is not the case; CA now acknowledges that READTIME
field is being corrupted and CA Level 2 is working at the
one reporting site to develop a fix. I had already added
protection in MXG 11.11 to reset the first byte to zero:
Replace READTIME SMFSTAMP8. @;
with READCADI $CHAR8. @;
IF SUBSTR(READCADI,5,1) GT '01'X THEN
SUBSTR(READCADI,5,1)='00'X;
READTIME=INPUT(READCADI,SMFSTAMP8.);
but now the site reports the READTIME is off by 2 hours,
so it appears the time part of READTIME is just bad,
until CA develops a fix.
See Revision by Change 12.199; 1,1 changed to 5,1.
Thanks to Giovanni Dossena, Einchem Elastomeri S.R.L., ITALY.
Change 11.341 TYPE94 variables SMF94Axx were labeled as EJECT when they
VMAC94 should are AUDIT, and variable SMF94EIN/SMF94EPM were
Mar 17, 1994 dropped from the KEEP= list, as they do not exist, and
could be confusing!
Change 11.340 Support for STC ICEBERG 9200 Disk Array Storage Subsystem
EXICECHA creates four datasets, one for each subtype of the SMF
EXICEDEV interval record which are provided by StorageTek:
EXICEDRV ICEBRGSY - Capacity and Space Utilization - per Subsys
EXICESYS ICEBRGCH - Channel Interface Statistics - per channel
IMACICE ICEBRGDV - Device and Its Cache Statistics - per device
TYPEICE ICEBRGDR - Drive Module Statistics - per drive module
VMACICE The range and content of the ICEBERG statistics are quite
Mar 9, 1994 impressive & comprehensive for this new technology, with
utilization counts and durations provided. This support
has been syntax checked, and simulated test data has been
processed, but no real-world users have used the data yet
Change 11.339 MXG 11.08 thru MXG 11.10. the last 380 lines of this RMF
ANALRMFR Report member were inadvertently deleted. The lines were
Mar 7, 1994 restored in MXG Early 11.11, without a Change number.
Thanks to Norbert Korsche, OMV-AG, AUSTRIA.
==Changes thru 11.338 were in the MXG Version Early 11.11 dtd Mar 8, 94=
Change 11.338 APAR UW04108 adds new variables to TYPE42 datasets:
VMAC42 TYPE42SR: ICLS RCLS SEQIOS
Mar 7, 1994 TYPE42DS: ICLS RCLS SEQIOS
Sequential I/Os are now counted separately (SEQIOS) and
are NO LONGER included in cache statistics (candidate
I/Os and hits). RLCS are Record Level Caches, ICLS are
Inhibit Cache Loads. ICLS only include those ICLS that
are set by DCME, not those by the STARTIO driver.
An additional APAR due out later this year adds even more
valuable instrumentation to the data set statistics:
TYPE42DS: BLKSIZE DEVNR STORCLAS VOLSER
S42AMDRB S42AMDRR S42AMDWB S42AMDWR
S42AMSRB S42AMSRR S42AMSWB S42AMSWR
S42AMZRB S42AMZRR S42AMZWB S42AMZWR
The long-needed VOLSER and DEVNR will be the first volume
for most multi-volume or striped datasets; however, for
sequential SAM access, there will be one record per
volume. The new Access Method fields (S42AMxxx) are
generated only for access methods that support DCME; the
new S42AMxxB variables count blocks read/written for
sequential/direct/directory and the S42AMxxR fields will
contain the corresponding I/O delay time (they are not
yet implemented). The directory counts do not include
STOW or BLDL yet, and there's more design ongoing to
capture as much as possible (eg., VIO and PDSEs). Note
how IBM is making life simple for us both, providing me
with early documentation so this support is already in
place in MXG 11.11 for when you get the APARs!
Thanks to Jeff Berger, IBM SSD, USA.
Change 11.337 CA's TMS can cause a type 80 (RACF) record to be created
VMAC80A for BLP processing, (a ZAP from CA is required to enable
Mar 7, 1994 creation of the records), but they exposed an MXG design
error: variable RESNAME was blank and variable OLDDSN
contained resource name. MXG now correctly inputs the
Resource Name into variable RESNAME; I should then store
RESNAME into OLDDSN only if RACFEVNT=04 (a RENAME), but
since OLDDSN always has contained the Resource Name, and
since you should not have to change your reports, I chose
to continue to put Resource Name in both RESNAME and
OLDDSN variables.
Thanks to Simon Hendy, Reader's Digest European Systems.
Change 11.336 Boole & Babbage CMF PTF BPM4681 adds new variables to
VMACCMF these existing datasets:
Mar 6, 1994 CMF27C93 C279WEH,C279WER,C279WFM
CMF27CSD CMF27CHN,CMF27CU2,CMF27DEV,CMF27LCU,
CMF27MDR,CMF27OBR,CMF27UA1,CMF27UA2,
CMF27uty, and CMF27VOL (the VOLSER!)
In the CMF27CSD dataset, the existence of the new fields
can be identified by testing CMF27VOL; if it is non-blank,
the record was created after PTF BPM4681.
Thanks to Matthew McCue, United Parcel Service, USA.
Thanks to John Piccone, United Parcel Service, USA.
Change 11.335 A minor correction to the revised VMXGSUM summarization;
VMXGSUM if the first data step was not required by the SORT, the
Mar 6, 1994 PROC MEANS looked for MXGSUM1 when it wanted MXGSUM2;
also, a specious error message when the length of the
INDATA= string was less than 40 bytes was eliminated. It
needs to be stressed that the changes made to VMXGSUM are
INCOMPATIBLE if you have tailored any of these members:
ASUMDBDS ASUMDB2A ASUMDOS ASUMHPCS ASUM70PR
DAILYDSN GRAFDB2 GRAFLPAR TRNDDB2A
You must retrofit your tailoring, starting with the new
member in MXG 11.11 (see the text of Change 11.309).
Change 11.334 Batch LSR for VSAM can produce incredible savings, by
ANALDSET using memory for buffers instead of repetitive I/O to the
ADOCBLSR same record. Jobs cost less, use less CPU, fewer I/Os,
ANALBLSR and run in tens of minutes instead of tens of hours. This
Mar 6, 1994 new analysis by Chuck Hopf adds new variables in existing
ANALDSET program (that reads SMF and combines type 14/15,
type 64, and type 30 data) to its output dataset DSETOPEN
which is then used as input to ANALBLSR's algorithms to
identify the jobs and VSAM files that could benefit from
BLSR. ANALBLSR also reports any existing Batch LSR usage
and will suggest increase or decrease in buffering where
appropriate. Implementing Batch LSR requires no change
to the application; only a simple JCL change is required,
and example JCL is in member ANALBLSR. Chuck's full
research paper on this timely subject will be in member
ADOCBLSR when it is available. Chuck points out that for
random access to the same records/index, increasing the
number of buffers (BUFNI,BUFND) does not eliminate I/O.
You would expect that if the data was in the buffer VSAM
would find it there, but actually without Batch LSR, I/O
is done instead of lookaside into the buffers! One case
of an Index with only 6 records had one million EXCPs for
a single step; using BLSR with 10 buffers reduced the I/O
count to seven! ANALBLSR lets you set thresholds of the
amount of memory you want to use, and the percentage of
the total I/O for the step, before it will be selected as
a candidate for Batch LSR, and is self-documenting. This
is still ongoing research.
Thanks to Chuck Hopf, Primerica, USA.
Change 11.333 ANALDB2R PMAUD02 Authorization Failure report had N/A for
ANALDB2R table/object name, when there should have been a name.
DIFFDB2 The length of a SUBSTR() was incorrect, causing tests for
IMACDB2 character values to be incorrect. The DB2PM manual was
READDB2 used to decide when a Target/Owner is printed, and it
Mar 6, 1994 says that they are not printed for "ARCHIVE", yet their
report does print it, so we revised our logic to match!
ANALDB2R PMSTA01 Statistics report timestamps printed
were unclear or misleading. There are two sets of
timestamps; the first is the time range of the data that
was read, the second is the range of data summarized on
that page, if INTERVAL= is specified. Also, DIFFDB2,
IMACDB2, and READDB2 were corrected to use _LDB2STA
instead of the hardcoded PDB.DB2STATS, and IMACDB2 and
READDB2 now know about the new DB2 3.1 dataset DB2ACCTP.
Thanks to Wai Choong Mak, Development Bank of Singapore, SINGAPORE.
Change 11.332 Support for Candle's Omegamon II for SMS user SMF record
EXOMSMDV creates two new datasets:
EXOMSMJB OMSMSDEV - DASD Device Statistics
IMACOMSM OMSMSJOB - JOB and DSNAME activity on each volume.
TYPEOMSM This code has been tested with actual data, but has not
VMACOMSM been extensively validated by real users, yet!
Mar 5, 1994
Change 11.331 The contributed RACF reports program WPDBRACF had to be
ANALRACF changed due to an apparent change in the way that some
Mar 4, 1994 formatted values were named in the PROC TRANSPOSE. The
RENAME= list for dataset RACFREP2 was revised.
Thanks to Neil Campbell, Inland Revenue, ENGLAND.
Change 11.330 DB2 Audit Detail report, Completion Code, was incorrect,
ANALDB2R causing "INVALID NUMERIC DATA" message on the SAS log.
Mar 4, 1994 Two tests for QW0083AD=0 and two tests for QW0087AD=0
should have tested for hexadecimal character zero instead
of numeric. The two pairs of statements now reading :
IF QW0083AD=0 THEN .... and IF QW0087AD=0 THEN ....
must be changed to read:
IF QW0083AD='00'X THEN ... and IF QW0087AD='00'X THEN ...
Thanks to Wai Choong Mak, Development Bank of Singapore, SINGAPORE.
Change 11.329 CICS/ESA DFHSTUP Shutdown Statistics Reports can now be
ANALCISH printed by MXG, either from a raw SMF file, or from a PDB
VMAC110 library (with minor modifications to BUILDPDB). This is
Mar 4, 1994 a significant contribution that uses ESA CICS datasets to
replicate the important IBM Shutdown reports. You can
// EXEC MXGSAS
//SMF DD DSN=YOUR.SMF.TYPE110.records,disp=shr
%ANALCISH(PDB=SMF);
to generate all reports from raw SMF data. You can also
generate these reports regularly, from your PDB, but you
will need to tailor BUILDPDB so that it copies all of the
CICS statistics datasets from the WORK file into the PDB.
You must add, in member EXPDBOUT, this code:
PROC COPY IN=WORK OUT=PDB;
SELECT CIC:;
and then you can invoke %ANALCISH(PDB=PDB); to print
shutdown reports for all CICS regions. Additional macro
arguments let you select date/time/region, and to select
only the desired report.
An minor error in VMAC110 was also corrected; member
IMACCICS is now included by its VMAC, instead of in its
TYPE member or by BUILDPDB. This clerical oversight only
affected me when exploiting my new "_L" logic, but should
have no effect in the field!
Note for the experts: I needed to do this so that I
could null out the CICSTRAN data set (which has high
volume, and is not currently used by ANALCISH) when
I ran against SMF data, and the mislocated %INCLUDE
did not let me. Normally you would null out a dataset
by EDITing the product's IMACxxxx member and change
its "_L" macro's dataset name to "_NULL", but you can
also null out any MXG dataset on the fly, without EDIT
of the IMACxxxx member, by using this syntax:
%INCLUDE SOURCLIB(VMACSMF,VMAC110);
MACRO _LCICTRN _NULL_ %
DATA _VAR110; _SMF; _CDE110;
(You must be at SAS 6.08 for the _NULL_ operand to be
a valid argument of the OUTPUT statement!)
In addition to producing the CICS Shutdown Report, member
ANALCISH lets you see what variable from what MXG dataset
is used for what report field, by reading the code! This
set of reports has been long overdue; the most important
reports have been implemented for both CICS 3.2 and 3.3,
but there are more reports (especially the detail reports
by transaction) that were not finished in time for 11.11.
Thanks to Willi Weinberger, Gothaer Versicherungsbank, GERMANY.
Thanks to Siegfried Trantes, Gothaer Versicherungsbank VVAG, GERMANY.
Change 11.328 Division by zero if there were no TSO transactions in an
TRNDRMFI interval. Change PCTTRIV=TRIVTRAN/TSOTRAN*100; to read
Mar 4, 1994 IF TSOTRAN GT 0 THEN PCTTRIV=TRIVTRAN/TSOTRAN*100;
Thanks to Norbert Korsche, OMV-AG, AUSTRIA.
Change 11.327 MXG 11.09A and 11.10 only. Change 11.270 caused INVALID
TYPEMON8 DATA FOR TIAPREQ in the MONISYST dataset if the Landmark
Mar 4, 1994 record was from 8.1 with an archaic history segment (i.e.
when LENGTH=2276). The test in MXG for IF LENGTH GE 1464
should have been IF LENGTH EQ 1464. (The error did not
affect the MONITASK dataset, and the history segment is
no longer created by Landmark.)
Thanks to John Goodstat, Gardner Merchant, ENGLAND.
Change 11.326 Sterling's NDM has been renamed to Connect Direct 1.7.01
VMACNDM and the format of the PT record changed, causing INVALID
Mar 4, 1994 DATA for HH messages. Replacing the single line reading
Mar 21, 1994 INPUT +30 with LOC=LENGTH-21;INPUT @LOC corrected some
records, but there are "PT" records with invalid values
for date/times of 000000000001000Ax & 2800000000FC5B10x
that I need to talk to Sterling about, but I can't find
anyone there to return my call, and I only have the PT,
CT, & MC segments corrected thus far, and I still have
no response from Sterling. If you need to process NDM
records now Connect Direct, send us a fax request, ande
we will advise you of the current status.
Thanks to John Goodstat, Gardner Merchant, ENGLAND.
Change 11.325 Type 42 subtype 6 read from VSAM SMF caused STOPOVER.
VMAC42 (There was no error when dumped BSAM SMF was read.)
Mar 1, 1994 Calculation of these three offsets did not include the
"+OFFSMF" at the end of the line. They should read:
OFFJDDSO=OFFJDDSO-3+OFFSMF;
OFFDSIOO=OFFDSIOO-3+OFFSMF;
OFFJDDSO=OFFDSNXT-3+OFFSMF;
The GMT conversion algorithm should also be changed to:
GMTOFF42=100*FLOOR((SMFTIME-SMF42PTE+10)/100);
Thanks to H. Placht, RWD Gmbh Datenverarbeitungsgesellschaft, GERMANY
Change 11.324 Variables SAMPSKPD, RMFIIIRC and INTRVSYN were always
VMAC7072 blank, because variable CONVFLAG should have been input
VMAC71-VMAC79 as PIB1 instead of PIB2.
Thanks to Scott Ashby, Wachovia Operational Services Corp., USA.
Change 11.323 MXG 11.09-11.10 only. Change 11.246 added support for
IMAC28 NPM 2.1.0, but in IMAC28, macro _L028NWD should have
VMAC28 spelled its dataset name as NPMNWDWD instead of NPMNWCWD.
Feb 28, 1994 In addition, causing confusion but no execution error,
comments in VMAC28 were misspelled; NPMCLLAN should be
NPMCMLAN, and RMSTR should be RMSTA in all occurrences.
Thanks to Ann Wheeler, American President Lines, USA.
Change 11.322 TYPE72MN variables WSETFIX and WSETASM were incorrect.
VMAC7072 They are now calculated as:
Feb 18, 1994 WSETFIX=FRAMEFIX/AVGUSER;
WSETASM=FRAMEASM/AVGUSER;
Thanks to Jan van Kemenade, Universitair Centrum Info., NETHERLANDS.
Change 11.321 Support for ISOGON's SoftAudit Product Usage File and
EXSFTAM Module Usage File creates two datasets by reading the two
EXSFTAP separate SoftAudit flat files:
IMACSFTA MXG Dataset DDname Description
TYPESFTA SOFTAUDM XPUSAGEM Module Usage File
VMACSFTA SOFTAUDP XPUSAGEP Product Usage File
Feb 17, 1994 Both files will be read if data exists in either DDname:
// EXEC MXGSAS,USER=PDBSFTA
//XPUSAGEM DD DSN=MODULE.USAGE.FILE,DISP=SHR
//XPUSAGEP DD DSN=PRODUCT.USAGE.FILE,DISP=SHR
//PDBSFTA DD DSN=WHERE.YOU.WANT.OUTPUT,DISP=(,CATLG),
// UNIT=SYSDA,SPACE=(CYL,(10,10))
%INCLUDE SOURCLIB(TYPESFTA);
If you only want to process one of the two files, use
DD DUMMY in your JCL for the unwanted file.
Change 11.320 APPC tasks do not go thru JES, so there will be no type
BUILDPDB 26 purge record to match up with APPC type 30 records. As
BUILD006 a result, all APPC work would be held in the SPIN library
Feb 16, 1994 until SPINCNT in IMACSPIN is exceeded. Even if there are
type 6 records for APPC tasks, there is no way to know
they exist, so there is no reason to SPIN APPC tasks, and
therefore, the BUILDPDB logic for outputting APPC tasks
to the PDB.JOBS and PDB.STEPS datasets was revised to
send APPC tasks to the PDB as soon as both a type 30
subtype 4 (step) AND type 30 subtype 5 (job) record have
been found. If there were any type 6 records for the
same JOB JESNR READTIME combination in today's SMF data,
then PDB.PRINT will have the APPC tasks print data with
accounting fields from the type 30. An isolated type 6
record for an APPC task will be output when found, i.e.,
it will not be sent to the SPIN library. The insert:
ELSE IF TYPETASK=:'A' THEN DO;
IF IN30_5 THEN OKFLAG=1;
ELSE IF IN6 AND NOT IN30_4 THEN OKFLAG=1;
END;
Thanks to Don Friesen, B.C. Systems, CANADA.
Change 11.319 AS/400 variable AS400SYN was blank, because the %MACRO
VMACQAPM variable &AS400SY was not passed correctly, and was being
Feb 16, 1994 reinitialized to blanks in QAPMCONF. The three SYMPUTS
in _CQAPCON were enclosed in IF _N_=1 THEN DO; ... END;.
All occurrences of AS400SYN="&AS400SY"; were changed to
read AS400SYN=SYMGET('AS400SY'); Also, the single
occurrence of NRCPUS="&AS400CP"; was changed to read
NRCPUS=SYMGET('AS400CP');
Thanks to Greg Scriba, Budget Rent-A-Car, USA.
Change 11.318 CICS Statistics variable A20E1HWM (Peak Contention Users)
VMAC110 was left out of the KEEP= list for dataset CICCONMR.
Feb 14, 1994
Thanks to Don Deese, Computer Management Sciences (CPExpert), USA.
Change 11.317 Partial support for LEGENT's MIM Release 4.0 enhances the
VMACMIM MIMTAPE dataset for the new release, but additional work
Feb 14, 1994 is needed to decode new subtypes in this release. This
code is functional, and hence included, but test data for
other subtype is needed before full support is provided.
Thanks to Doug Drain, National City Bank, USA.
==Changes thru 11.316 were include in MXG PreRelease 11.10 dtd 14Feb94==
Change 11.316 Support for LEGENT's NETSPY Release 4.4.
EXNSPYET -Dataset NSPYAPPL, new variables APOTLN62, APOTNN62 count
EXNSPYFR the outbound bytes for LU 6.2 and non-LU 6.2 sessions.
FORMATS -Dataset NSPYLU, new variable RESPNOTC='Y' if response
IMACNSPY time is collected. IF RESPNOTC='N', then variables:
VMACNSPY LRSPHOST LRSPNET WRSPHOST WRSPNET CRSPHOST CRSPNET
Feb 13, 1994 NETRSPNO T1RSPNO T2RSPNO T3RSPNO T4RSPNO
are now set to zero by MXG, as LEGENT says "these fields
may have data in them, however they should not be used
when reporting".
-New Dataset NSPYFRLY for Frame Relay Statistics
-New Dataset NSPYETHR for Ethernet Statistics.
-Several new values for NSPNSUBT are now decoded by
MXG format MGNSPEL, and logic for recognition of which
sub-subtype of the type 'N' was clarified.
Change 11.315 Support for CA's ACF2 Release 6.0 and 6.1 added seventeen
VMACACF2 new variables to type 'V' record, and one to type 'D'.
Feb 12, 1994 Renames of ASSSPCOD to ASSPPCOD and ACFGFOE to ACFGFDEN
correct my misspellings. The use of LENGTH-COL-1 (to know
how many bytes are left in the record) should have been
LENGTH-COL+1 (this could have caused new variables to not
be read in, although no one seems to have noticed!).
In this revision, I have also decoded the LIDREC and the
LIDXARE of the type 'J' record, labelled and formatted
the several dozen new variables, but did not add any of
those variables to the ACF2JR data set; instead, if you
decide you need those variables, you can use the MXG
macro _KACFJR in member IMACACF2 to add them. (Only one
site had requested the LID fields.)
Change 11.314 For developers, this is my recommended test protocol:
Testing
Feb 12, 1994
You need to ALWAYS test it ONE MORE TIME!
When you think your code is done:
Run it once more, as a batch job, and while that job
that job is running, use SPF 3.12 COMPARE to examine
every difference between the before-and-after source
members.
Then,examine the batch job's output:
- The SYStemLOG, for any Operating System warnings,
- The SASPRINT report output, for any differences,
- The SASLOG log output, for any occurrence of each
of these strings (blanks are important!):
"ERROR:" "ERROR :" " UNINIT"
"NEVER BEEN" "NOT FOUND" "CONVERT"
"NOT CATLGD" " NOT " "TRUNCATED"
Change 11.314 MXG 11.09A Only, PMACC02 Report, DB2 Accounting Detail
ANALDB2R Trace was in error due to insufficient testing. The data
Feb 12, 1994 was summarized when it should only have been sorted.
Thanks to Jeff Marsh, Twentieth Century Services, USA.
Change 11.313 OMEGAMON for CICS V550/V551 User SMF record subtype 100
VMACOMCI sub-subtype 2 caused INPUT STATEMENT EXCEEDED RECORD LEN.
Feb 12, 1994 The code expected the same number of segments for EGROUP
as for ETRNAME, but they are unrelated tables. The code
was corrected, but for simplicity both EGROUP and ETRNAME
segments are still output in dataset OMCITRAN; you can
identify which is which by testing :
IF ETRGRPM NE . ==> ETRNAME and ETRGRPM are valid
IF ETRGRPM EQ . ==> EGROUP, EGRPNAM, EGRPESNR are valid
This change supercedes Change 11.115.
Thanks to Ron BLeeden, Jewel Food Stores, USA.
Thanks to Bill Wieland, EDS Westlake, USA.
Change 11.312 Variable AVGENQMS (Average ENQUE time in milliseconds)
VMAC74 was calculated but not KEPT, LABELed nor FORMATted, but
Feb 9, 1994 now it is.
Thanks to Waldemar Schneider, SAS Institute Europe, GERMANY.
Change 11.311 GRAFWORK was enhanced with a new graph of memory usage by
GRAFWORK workload (using the ACTFRMTM-based measure of resident
Feb 7, 1994 memory frame seconds in the xxxxMEMR variables). GRAFWORK
now provides graphic depiction of CPU, I/O, and MEMORY
resource usage by workload.
Change 11.310 GRAFRMFI was revised to include new variables added to
GRAFRMFI RMFINTRV recently, and the internal logic revised to make
Feb 7, 1994 maintenance easier.
Change 11.309 This major revision to VMXGSUM reduces runtime and CPU
VMXGSUM time, by keeping only the variables and datasets that are
ANALDB2R needed during the input for summarization, and executes
ANALPRTR only the steps required (i.e., it will bypass PROC SORT
ASUMCICS if it can). If you have tailored some MXG members that
ASUMDBDS invoke %VMXGSUM, you MUST examine the INCOMPATIBILITY
ASUMDB2A note, below, and you MAY have to update your tailored MXG
ASUMDOS members. If you have used %VMXGSUM in your own reporting
ASUMHPCS programs, you may also be vulnerable to required changes.
ASUMJOBS -Changed the logic for MINTIME= and MAXTIME=. No longer
ASUMTMNT are variables named MINTIME/MAXTIME created; instead, the
ASUMVDEV variable name(s) passed into VMXGSUM are retained, which
ASUMVMON permits bypassing the first data step to reduce costs.
ASUM70PR -NOSORT= parameter was added, which allows the sort to be
DAILYDSN bypassed if you KNOW the data is already in order.
GRAFDB2 -Initialization to protect for "UNINITIALIZED VARIABLE"
GRAFLPAR message (the series of IF X=. THEN X=.; statements) was
TRNDDB2A relocated to execute only once.
TRNDDB2S -New logic automatically figures out what variables need
Feb 7, 1994 to be kept (by looking at all variables that are in any
text of of the list-of-variable parameters), so the _KMXGSUM
change was syntax that was added in MXG 11.09 is no longer used.
revised -The new KEEPIN= parameter is required if you have INCODE=
Mar 6, 1994 specified, and if there are unique variables used in your
INCODE= logic that are not referenced by other VMXGSUM
list-of-variable-parameters (SUM= SUMBY= MIN= ... etc.)
-INCOMPATIBILITY NOTE
If there is an INCODE= parameter (for sophisticated use
you can insert SAS code with this parameter), AND only
if there are variables referenced in your INCODE= logic
that are not referenced by the other VMXGSUM parameters
(SUM= SUMBY= MIN= ... etc.),
Then you MUST add a KEEPIN= parameter to your %VMXGSUM
invocation so that those unique variables exist during
the INCODE= code execution.
These MXG-supplied members had to be changed in the MXG
Source Library because all had un-kept variables that
had to be listed in the KEEPIN= parameter:
ASUMDBDS ASUMDB2A ASUMDOS ASUMHPCS ASUM70PR
DAILYDSN GRAFDB2 GRAFLPAR TRNDDB2A
If any of those 9 members are in your USERID.SOURCLIB
tailoring library, you MUST refit your changes,
starting with the MXG 11.11 member that contains the
required KEEPIN= parameter.
You must scan your USERID.SOURCLIB(s) for any of your
own programs that invoke %VMXGSUM, and see if any of
them meet both conditions (INCODE= and nonkept variable
referenced in that INCODE= logic).
Examine the SAS log of your test runs for UNINITIALIZED
VARIABLES messages; that is a sure sign that you have
INCODE= variables that do not exist!
DO NOT OVERLOOK THIS CRITICAL INCOMPATIBILITY, which
should affect only the very small number of sites that
have tailored the MXG summarization or trending code.
As long as you are executing those 9 MXG members
unmodified from the MXG 11.11 library, there is not any
incompatibility with this change.
-All MXG invocations of VMXGSUM were examined and INVOKEBY
was added so the caller would print on the SAS log.
-Especially with a large input dataset (eg., CICSTRAN with
594,000 observations, the keeping of only the needed
variables significantly saves resources. Using:
%VMXGSUM(INDATA=CICSTRAN.CICSTRAN,
OUTDATA=CICSSUM,
DATETIME=STRTTIME,
INTERVAL=HOUR,
SUMBY=APPLID DATETIME,
FREQ=NUMTRANS,
SUM=IRESPTM TASCPUTM);
Showed these comparisons before and after this change:
Run COMPRESS CPU EXCP Memory DASD
Option SEC count used tracks
Before NO 120 21843 4973K 10699
After NO 83 12920 4902K 943
Before YES 650 25330 4913K 7129
After YES 135 13255 4902K 1111
The elapsed times were also significantly reduced. The
37 minutes required for the "before" compressed run was
reduced to 11 minutes for the "after" compressed run.
Thanks to Chuck Hopf, Primerica, USA.
Change 11.308 Support for Candle's Deltamon SMF record creates new MXG
EXTYDLMN dataset TYPEDLMN, which reports activity (ADD,UPDATE,
FORMATS DELETE, or RENAME) at the PDS member level.
IMACDLMN
TYPEDLMN
VMACDLMN
Feb 7, 1994
Thanks to Chuck Hopf, Primerica, USA.
Change 11.307 ASTEX variable RCHCNT=SUM(RHTRD,RHTRDS,RHTDFW,RHTCSW) was
VMACDMON added after the INPUT of the four arguments. In prior
Feb 7, 1994 versions of ASTEX, RCHCNT was directly input, but now it
must be calculated from its four arguments.
Thanks to Jay Stewart, Honda, USA.
Change 11.306 For MVS execution, MEMSIZE=32MB is now the default value
CONFIG in CONFIG. The default BUILDPDB failed "OUT OF MEMORY"
Feb 7, 1994 with MEMSIZE=24MB, and 32MB protects for the future.
Change 11.305 Variable CMF09UIC from Boole's CMF must be divided by the
VMACCMF number of samples:
Feb 7, 1994 IF CMFHDSAM GT 0 THEN CMF09UIC=CMF09UIC/CMFHDSAM;
Variable CMF05NUM is now format HEX4.; variable CMF19TPG
no longer formatted HEX2.!
Thanks to Joanne Turpie, Department of Labour, NEW ZEALAND.
Change 11.304 Support for OPC/ESA Release 2.1 has added 5 new datasets
EXOPC34 (and corrected INVALID MTD SUBTYPE messages):
EXOPC35 OPC24_H MTD Delete/Change CM
EXOPC36 OPC24_I MTD Hold Operations
IMACOPC OPC34 Catalog Management
VMACOPC OPC35 Backup Event
Feb 6, 1994 OPC36 CP Backup Log
Finding all the IBM manuals for this release was a chore;
comments in VMACOPC identify what is documented where!
And I learned that you cannot order Licensed IBM Pubs if
you use your "IBM Customer Number", but if you give the
same number as your "IBM Enterprise Number", the Pubs
clerk discovers you are authorized for Licensed Pubs!
Thanks to Alan Phelan, Allied Irish Bank, IRELAND.
Thanks to Wolfgang Vierling, Vereinte Versicherungen, GERMANY.
Change 11.303 TYPE71 variable AVLEXTMN, "Minimum ESTORE Available", can
VMAC71 be negative, according to IBM, so its input was changed
Feb 5, 1994 from &PIB.4. to &IB.4. The actual value of the field is
"number of extended storage e-frames currently on the
available sets excluding those reserved for pref steal."
This means that when the value is zero, all of RSM except
for pref steal will accept that there are "no" available.
If the value is less than zero, pref steal will check to
see if there are any in reserve and will use these.
Thanks to Hr. Leineweber, HUELS AG, GERMANY.
Change 11.302 Testing of TYPEVMXA (VM/ESA) under UNIX, OS/2 or WINDOWS
AUTOEXEC found glitches (but this change is NOT needed if you run
VMACVMXA MXG under either the MVS or VM versions of SAS):
Feb 5, 1994 -AUTOEXEC had blanks inside quotes, which is no problem
Changed due for WINDOWS or OS/2, but UNIX did not tolerate, so they
to $VARYING: were removed. Also, a new Filename statement was added:
ANALSNAP FILENAME INSTREAM 'C:\MXG\USERID\INSTREAM.SAS'
IMACACCT and must be suffixed .SAS, because it is written to and
SYSLOGJ3 then %INCLUDEd (to build formats "instream").
UTILXREF -Some variables input as $EBCDIC were not character data
VMACACF2 but were binary data and are now input as $CHAR. Some
VMACASXT also required addition of $HEX formats, and most were in
VMACCMA seldom-to-never-used VM data sets.
VMACDB2 -The building of the "instream" PROC FORMAT failed with
VMACHMF INVALID HEX DATA, because of $EBCDIC versus $CHAR input
VMACPOOL format that was corrected.
VMACTSOM -Discovered that EBCDIC algorithm to identify numeric
VMACVMON EBCDIC characters from alphabetic characters, using
VMACVMXA LT '0' ==> alphabetic GE '0' ==> numeric
VMACVVDS is invalid under ASCII execution. EBCDIC algorithm works
VMAC102 because EBCDIC numbers are 'F0'x thru 'F9'x, which is
VMAC24 larger than EBCDIC letters of '81'x thru 'C1'x (lower
VMAC33 case) and 'C1'x thru 'E9'x (caps), but the ASCII numbers
VMAC37 are '30'x thru '39'x, which is smaller than ASCII
VMAC4789 letters '41'x thru '5A'x (caps) and '61'x thru '7A'x
VMAC59 (lower case). The parsing algorithm was redesigned to
VMAC60 scan for non-blank versus blank, and one more difference
VMAC6156 between ASCII and EBCDIC execution is documented!
VMAC80 -Use of $VARYING200. input for printable characters was
VMAC83 resolved. $VARYING acts like $CHAR instead of $EBCDIC,
VMXGHSM so strings that are to be printed need conversion. The
XMACNCCF WINDOWS conversion algorithm is:
INPUT variable $VARYINGnn. lenvar @;
variable=INPUT(variable,$EBCDICnn.);
variable=TRANSLATE(variable,' ','80'x);
Note: only the INPUT function should be required, but
The TRANSLATE was unexpectedly needed because the
$EBCDIC was found to convert '20'x ASCII blanks at
the end of the string to '80'x. SAS Institute
suggested that using INPUTC(string,format,length);
instead of INPUT(string,format) would have eliminated
the need for the TRANSLATE() function, but my code
works, whereas (Jun 24, 1997 update:)
when I tried INPUTC under SAS 6.12 TS020 Windows 95
I got these errors pointing to the $EBCDIC128. when
I tried to use VAR=INPUTC(VAR,$EBCDIC128.,LEN);
386-185 Expecting Arithmetic Expression and
200-322 The Symbol is not recognized
underscored for format $EBCDIC128.. Problem
will be opened with SAS: That's the way it is!
The $VARYING conversion required examination of each
occurrence to see if the field is a printable (text)
string, and if so, insert the above conversion code.
(This also required creation of DO group in some cases.)
Thanks to Chris Powell, Vancouver Stock Exchange, CANADA.
Change 11.301 Labels for the four new SYNCSORT variables SYNDSMVL,
VMACSYNC SYNFMAVL, SYNFMALO, and SYNMMUSE were added; originally
Feb 2, 1994 they were not provided in SYNCSORT documentation.
Thanks to John Borland, Citibank, USA.
Change 11.300 An SMF Writer "Simulator" has been added to ANALSMF, to
ANALSMF examine your SMF data and tell you what is the optimum
Feb 2, 1994 CI Size of your VSAM data set. See the MVS Technical
Note in Newsletter TWENTY-FIVE for a complete discussion
of the impact of the wrong CI Size on the SMF Writer.
You need only to EDIT ANALSMF to set the CI Size of your
VSAM file (in macro _MYCISIZ), and then point the SMF DD
to a dumped SMF file, and the report of DASD Space and CI
Writes at different CI Sizes will be produced. Several
additional reports were added to describe how seldom the
SMF Writer actually writes, and the Statistics from
TYPE23 are also printed, along with a tabulation that
shows the contents (count and bytes) of where your SMF
data records come from.
Change 11.299 The example of the ZARA LIST command to create an OUTFILE
TYPEZARA needs to have the SSFN operand added so that "secondary"
VMACZARA files (i.e., second and subsequent files on a volume) are
Feb 2, 1994 created in the OUTFILE. Without SSFN, you only see the
first dataset on each volume in ZARADSN. Correct is:
LIST OUTFILE ACTIVE SSFN $$
In addition, variable LSTTYPE, type of tape (AUTO,ACTIVE,
SCRATCH) was added to ZARAVOLS and ZARADSN datasets.
Also, variable FILTIMEL may contain trash (seems to be
for volumes converted to ZARA from CA-1); the "??" was
added to the INPUT FILTIMEL ?? &PD.4. statement.
Thanks to David Childress, Lowe's Companies, Inc., USA.
Thanks to Neil Ervin, Huntington Bank Service Company, USA.
Change 11.298 The JCL in this example to analyze all records from a
ANALALL specific job was partially for SAS 6.08 and partially for
Jan 18, 1994 SAS 5.18, causing confusion for novices. The JCL example
now is for SAS Version 6.
Thanks to Rosie Jergovic, Pacific Bell, USA.
Change 11.297 Variable TIC_UTIL in NETSPY is incorrectly computed. The
VMACNSPY BYTSENT+TRTPBYTS should be BYTSENT*TRTPBYTS in both of
Jan 18, 1994 the equations for TIC_UTIL.
Thanks to Linda Liu, Transamerica, USA.
Change 11.296 This analysis of the size of an SMF file was enhanced to
ANALSMF report SMF type 23 statistics, and the categorization of
Jan 18, 1994 SMF record IDs for JOB-IO now includes all VSAM activity.
Change 11.295 Missing value for FATNUM, UTNUM, or MRONUM cause INVALID
TYPEMON8 DO ARGUMENT message if Change 11.270 was not installed to
Jan 17, 1994 circumvent new format of Landmark data. While 11.270 did
avoid these errors, the missing value protection was now
added, just in case!
Thanks to Hr. Dungl, CA-Inform, GERMANY.
Change 11.294 MXG 11.09A only. Accounting detail report not produced
ANALDB2R if time selection was used and DB2ACCT was used as input.
Jan 13, 1994 Find "%MACRO PMACC02;", then find "MINTIME=QWACBSC;".
Insert after that line the statement "MAXTIME=QWACESC;"
Thanks to Jeff Marsh, Twentieth Century Services Inc., USA.
Change 11.293 Additional refinements in the RMF reporting from MXG data
ANALRMFR were added. The time selection logic was corrected so a
Jan 13, 1994 report for 10am-12am Mon-Fri can be requested, and CPUIDs
thru 15 CPUs is now supported.
Change 11.292 MXG 11.09A only. The KEEP= logic did not include &MEAN.
VMXGSUM The three lines starting with &MAX &MAXTIME need to have
Jan 12, 1994 &MEAN added after &MAXTIME. Only if you invoked VMXGSUM
with the _KMXGSUM operand, and had MEAN= parameter, would
this change have had any effect. Change 11.309 revised.
Change 11.291 Analysis of VSAM datasets were sorted by SMFTIME instead
ANALDSET of the STEP initiate time; logic was added to store and
Jan 11, 1994 retain the SORTTIME of each STEP record in STEPTIME, and
then store STEPTIME into SORTTIME for TYPE64 observations
so VSAM is consistent with non-VSAM sort order.
Thanks to Gary Matney, Twentieth Century Investors, USA.
==Changes thru 11.290 were included in MXG 11.09A dated Jan 10, 1994====
Change 11.290 Member ASUMAPAF, a user contribution, summarizes Amdahl's
ASUMAPAF APAF records from MDF, similar to ASUM70PR summary of
TYPEAPAF IBM's PR/SM records. TYPEAPAF was cosmetically changed
Jan 8, 1994 to use __NRLPS to control all of the LPAR variables to
be kept (previously, some variables were controlled by
__NRLPS and some were kept for all possible 15 LPARS).
The value of __NRLPS is set in IMACAPAF.
Thanks to Brian LeBlanc, Candle Corporation, USA.
Change 11.289 AS/400 data sets are now fully documented in this new
ADOCQAPM ADOC chapter, although it has not been final-pass edited.
Jan 8, 1994
Change 11.288 This example of a prime-time cross-system DASD report
ANALDASD from PDB.TYPE74 may be of use in tracking DASD activity
Jan 8, 1994 across multiple systems.
Thanks to Dan Kaberon, Hewitt Associates, USA.
Change 11.287 Preliminary testing under CMS of MXG 11.09 found that the
REXXTES6 REXX sample did not include VMXGINIT nor did it contain
Jan 6, 1994 the correct FILEDEFs to concatenate USERID and SOURCLIB
MACLIBs. See also the circumvention in Change 11.067 to
remove CICS and DB2 processing to run BUILDPDB. This
text will be revised when testing under CMS is completed.
Thanks to Jerry Maier, NBD Bank, USA.
Change 11.286 DB2PM-like reports have been revised to correct all
ANALDB2R reported errors and now exploit fields added by DB2 2.3.
Jan 6, 1994 Many of the TRACE reports (notably AUDIT, LOCKING, SQL)
were heavily modified, and all reports now use ANALDBTR
pairing where appropriate. Input can now be from a PDB
library on tape, and one new report has been added:
PMLOK04 - Lock Detail Trace report.
Thanks to Mike Skopec, Platinum Technology, USA.
Thanks to Wai Choong Mak, Development Bank of Singapore, SINGAPORE.
Thanks to Andy Vick, Allied Dunbar Life Assurance, ENGLAND.
Thanks to H. Lugert, Datav, GERMANY
Change 11.285 Pairing logic for IFCIDs 114-115 was added, the T102S054
ANALDBTR dataset was added to the S044S045 pairing. Also, all
Jan 6, 1994 observations of T102S063 (SQL text) are now output (only
the first 200 bytes of text was previously output - this
change in ANALDBTR will now cause the ANALDB2R SQL trace
report to now print all of the SQL text). Also, if the
input datasets are from a PDB library, the intermediate
T102Sxx datasets in the WORK file are now deleted.
Change 11.284 Some variables needed for ANALDB2R were not kept in some
FORMATS T102Sxxx datasets, and compressed data in IFCID 21 and 54
VMAC102 are now decoded, using the new $MGDB2XX format. Three
Jan 6, 1994 labels that exceeded 40 bytes were shortened.
Change 11.283 A minor correction: if IFCID=ALL was specified, the
READDB2 output T102Sxxx datasets were not copied to the output
Jan 6, 1994 PDB library, but now they are.
Change 11.282 New dataset PDB.DB2STATS is now created by merging the
DIFFDB2 three DB2 statistics datasets (DB2STAT0, DB2STAT1, and
Jan 6, 1994 DB2STAT2) for ease in statistics reports. Eventually,
the new dataset will be used by ANALDB2R reports, and you
should use DB2STATS in your own reports. As these
statistic datasets are small, there is little cost for
the redundancy.
Change 11.281 Major reduction in VMXGSUM resources (CPU,DISK) are now
VMXGSUM completed. Originally planned as Change 11.245, those
Jan 6, 1994 changes were not implemented until now, because the NODUP
SAS option and the MXG _KMXGSUM operand were in conflict;
NODUP dropped observations that were not duplicate, but
looked like dupes because of the reduced variables kept.
So the NODUP option on the SORTs in VMXGSUM were removed
(although a new option NODUP= lets you reinstate them if
you need them and know what you are doing!), and these
changes in the architecture of VMXGSUM were validated:
- The first data step is bypassed if there is no INCODE=,
no INTERVAL=, no SHIFT=, and no NORMx= arguments, and
if there is only one input dataset.
- The PROC SORT is bypassed if there is no SORTBY=.
In another enhancements, three new symbolic arguments
TEMP01,TEMP02,TEMP03 (which default to WORK) are used as
the high-level node of the work datasets, which permits
placing one or more of the work datasets on tape,
reducing the DASD requirement for VMXGSUM processing. If
all three TEMPxx parameters point to the same DDNAME,
then a PROC DATASETS is run at the end of processing to
clean up the temporary space, but if they are different,
we cannot clean up as we have no way to tell if this is a
tape or disk data set. VMXGSUM now uses DKRICOND=NOWARN
as the default (so input datasets with non-existent
variables do not raise a warning), but DKRICOND=WARN is
reset at the end of VMXGSUM execution.
Yet another enhancement is the new argument TIMERNGE=.
If TIMERNGE= is specified, four macro variables are then
constructed to determine the date, time, or datetime
range of the TIMERNGE= argument across the entire input
datasets. The macro variables created are:
MAXINDT - Maximum datetime value for the input data
MAXSLDT - Maximum datetime value for the output data
MININDT - Maximum datetime value for the input data
MINSLDT - Maximum datetime value for the output data
(You must supply the appropriate FORMAT if you print the
value of these four new variables.)
Note: The VMXGSUM architecture was further enhanced in
Change 11.309. This text was edited after that change.
Change 11.280 TYPE39_8 (Netview Session Awareness) LSAWxxxx variables
VMAC39 are wrong because the INPUT statement was off by 4 bytes.
Jan 6, 1994 Also, variables LSAWPSPU and LSAWPSPM were not input.
Change the LSAW section logic to read:
INPUT @OFFSAW REVISION &PIB.2.
+2
LSAWASBC &PIB.4.
- - - - - - - - - - - - - - 17 lines not displayed
LSAWRDQM &PIB.4.
@;
SKIP=LENSAW-80;
IF SKIP GE 8 THEN DO;
INPUT LSAWPSPU &PIB.4.
LSAWPSPM &PIB.4.
@;
SKIP=SKIP-8;
END;
IF SKIP GT 0 THEN INPUT +SKIP @;
END; /* SAW SECTION */
and add LSAWPSPM and LSAWPSPU to the KEEP= list for
TYPE39_8.
Thanks to Hr. Schulte, GRZ, GERMANY.
Change 11.279 MXG 11.07 thru MXG 11.09 did not process TPX Version 3.0
VMACTPX records (but prior MXG versions did), because the LEGENT
Jan 6, 1994 change in format of TPXVER did not document the 3.0 value
to be expected. The conversion code now reads:
IF TPXVER EQ '100 ' THEN TPXVER=' 1.0';
ELSE IF TPXVER EQ '200 ' THEN TPXVER=' 2.0';
ELSE IF TPXVER=:'3.0' THEN TPXVER=' 2.0';
ELSE IF TPXVER=:'3.5' THEN TPXVER=' 3.5';
ELSE IF TPXVER=:'1.0' THEN TPXVER='10.0';
Thanks to Jan Decuypere, Gemeentekrediet N.V., BELGIUM
Change 11.278 Landmark CICS variable TIESDATE (start date) can be null
TYPEMON8 if PTF U200952 is not installed. MXG uses TIESDATE to
Jan 5, 1994 validate that DUMP CONVERT was specified when you dumped
Feb 16, 1994 the Landmark data (see their examples TMON9DBU/TMON9FSU),
and MXG generates the "ERROR3.LANDMARK.MONITOR" error
message "INVALID FORMAT FOR TIESDATE" when TIESDATE is
null. Install the PTF. However, if you encounter that
error message, and know that your data was converted,
you can suppress the ABEND by commenting out the "ABORT
ABEND 1099" statement in member TYPEMON8, until the PTF
is installed. This change text was revised Feb 16, 1994.
Thanks to Mark Holland, State Energy Commission, AUSTRALIA
Change 11.277 If ASUMDB2A is executed separately from BUILDPDB, there
ASUMDB2A will be errors because %INCLUDE SOURCLIB(IMACDB2); did
Jan 5, 1994 not exist in member ASUMDB2A, but now it does.
Thanks to Steve Bryant, Belk Stores Services, USA.
Change 11.276 Support for ZARA Release 1.1 added 36 bytes to the sort
VMACZARA key and header area. You will have zero observations in
Dec 15, 1993 the ZARAVOL and ZARADSN datasets until you change all of
the @xxx values that are now greater than 100 by adding
36 to the present value. Thus the @172 VRCDTYP became
@208 VRCDTYP, the @183 VOLCHAIN became @219 VOLCHAIN,
and so forth.
Thanks to David Childress, Lowe's Companies, USA.
Change 11.275 IBM APAR OY67002 reports that if the number of LCPUs is
VMAC7072 changed in an LPAR, the data for that RMF interval
Dec 15, 1993 contains the accumulated values from IPL, and there are
no PR/SM segments in the type 70 for the interval.
This corrupts TYPE7072 variables LCPUEDTM,LCPUPDTM,
PCTCPBYx,PCTTIPx, corrupts TYPE70 variables CPUEDTMx,
CPUPDTMx,PCTCPBYx, and PCTTPIx, and corrupts essentially
all ASUM70PR variables for that interval. MXG detects
that the number of LCPUs changed, and sets LPARCHRN='Y'
in TYPE70PR (the Label for LPARCHNR now reads NUMBER OF
LCPUS*IN PARTITION*CHANGED?), but you MUST install the
PTF associated with the APAR if you change the number of
LCPUs in an LPAR while the system is up.
Thanks to Gary Hoover, American Express IPS, USA.
Thanks to Roger Zimmerman, Kemper Services Company, USA.
Change 11.274 Three new variables were added to the SAS User SMF record
VMACSASU in SAS 6.07/6.08. Variables SASVAFF (Vector Affinity CPU)
Dec 15, 1993 SASVUSE (Vector Usage CPU), and SASHSP (Hiperspace CPU)
are now input and formatted TIME12.2.
Thanks to Bruce Lietz, Cessna Aircraft Company, USA.
Change 11.273 Some TRND71 variables were not calculated. In the NORM2=
TNRD71 list, the first occurrence of SLOTNVAV should be SLOTNGAV
Dec 15, 1993 and variables ASMNVSC ASMSLOTS ASMSLOTX and ASMVSC were
added to the NORM2= list.
Thanks to Carl Tosetto, E-Systems Garland Division, USA.
Change 11.272 TYPE64 records with SITUATN='COMPONENT CLOSED' are the
ADOC64 only valid records to use for counting EXCPS, etc. The
ANALDSET type 64 records with NO SPACE AVAIL or VOL SWITCHED do
Dec 15, 1993 not contain the "delta" EXCP count, but instead have the
accumulated EXCP count from open to the time of that
event. As a result of this discovery, member ANALDSET
now keeps only TYPE64 observations for Component Closed.
Thanks to Scott Ashby, Wachovia Operational Services Corp, USA.
Change 11.271 Statement DEVASID DS XL2 has an asterisk in column
ASMTAPES 72 which causes the Assembly to fail. This member is
Dec 15, 1993 still in internal testing. See Change 11.360.
Change 11.270 Support for Landmark CICS/ESA Version 1.1 records. That
TYPEMON8 new version added 44 fields to the end of the MONISYST
Dec 14, 1993 interval record, causing "INVALID DO LOOP CONTROL" error.
This error can be circumvented by inserting "HITI=1;"
just before the "DO _I_=1 TO HITI;" statement, but you
will then get "INVALID DATA FOR TASKCPTM" and hex dumps
twice, because Landmark's field TIAPLCPU (MXG variable
TASKCPTM) is invalid until you install Landmark ZAP for
Problem Number U201102. (You can still process without
their ZAP as all other variables in MONISYST are valid,
and only the MONISYST data set was affected by the new
version!). In the actual change, the DO group to read
the history segment was removed, as that segment has not
existed for some time, and MONIHIST always has zero
observations. However, I did not delete the MONIHIST
dataset nor its _L,_K macro names, since that might have
caused a syntax error if you reference MONIHIST in your
report programs. Take heed, though, and remove MONIHIST
references so that I can deleted it in a later version.
Setting HITI=1 has the same effect as skipping the
history record; the TI record is now 1464 bytes long.
Thanks to Mark Holland, State Energy Commission of Western Australia.
Change 11.269 Dataset PDB.JOBS variables ACCOUNTn may be blank, and
BUILDPDB variables RESTARTS, JINLTIME, and NRTRANS can be missing
BUILDPD3 for jobs with MULTIDD='Y' (that is, multiple type 30s due
BUILD005 to many DD segments, typical only for long running jobs
Dec 13, 1993 like SAR, RMDS, CA-DISPATCH, etc., that have lots of
dynamic DDs). The MULTIDD='Y' observations must be
deleted during the second occurrence of the creation of
GOOD30_5 dataset. Find this block of code:
ELSE IF IN30_5 THEN DO:
IF MULTIDD5=' ' THEN RESTART+1;
OUTPUT GOOD30_5;
END;
And change it to read:
ELSE IF IN30_5 THEN DO:
IF MULTIDD5='Y' THEN DELETE;
RESTART+1;
OUTPUT GOOD30_5;
END;
The actual change also cleaned up references to MULTIDD
and TEMP3 which are no longer needed, but which are now
superfluous and safe to leave until you get a tape!
Thanks to Mark van der Eynden, Ferntree Computer Services, AUSTRALIA.
Change 11.268 CICS DL/I counts with CICS/ESA Version 3.3 Omegamon 110
IMACICDL records may be wrong. First, the test in IMACICDL needs
IMACICDA to be changed to IF SMFPSRVR GE 3 instead of EQ 3.
VMAC110 Second, if you have not added a "USERCHAR" optional data
Dec 14, 1993 field in your type 110 record, you must comment out the
statement "%INCLUDE SOURCLIB(IMACICDU);" in member
IMACICDA (because if that statement is present, MXG
always read at least one byte, causing wrong alignment).
Commenting out that %INCLUDE will generate an
"UNINITIALIZED VARIABLE USERCHAR" message, which is
not a problem, but in member VMAC110, I have added
"IF USERCHAR=" " THEN USERCHAR=" "; after both of the
%%INCLUDE SOURCLIB(IMACICDA); statements to correct.
The notes in IMACICDA and IMACICDL were updated to list
the CMODHEAD field names of the DL/I counters to make it
easier for you to know what sections you do or do not
have in your SMF type 110 record from Omegamon, using MXG
program UTILCICS to examine your dictionary.
This text was revised Dec 14, 1993, after MXG 11.09.
Thanks to Khin Zaw, Nordstrom, USA.
Change 11.267 APAF V2.1 dataset APAFCHAN is trashed, because the offset
VMACAPAF had a spelling error. Inside the SUBTYPE=5 DO group, the
Dec 13, 1993 statement LOC=OFFLP-3+OFFSMF should have been written as
LOC=OFFCHPID-3+OFFSMF;
Thanks to George Scott, Rockwell International Corporation, USA.
==Changes thru 11.266 were included in MXG 11.09 dated Dec 17, 1993=====
Change 11.266 Dataset TYPE1415 variable TEMP='TEMP' was incorrectly set
VMAC1415 if DISP1='.......1'B, so that part of the test to set
Dec 12, 1993 TEMP has been removed.
Thanks to Bruce Hudson, Payless Shoe Source, USA.
Change 11.265 Boole and Babbage CMF Type 72 Subtype 2 record is invalid
VMAC7072 and causes INPUT STATEMENT EXCEEDED error. There is only
Dec 10, 1993 one SWAP section, instead of one SWAP section for each
Performance Group, and other fields in TYPE72MN dataset
may be trashed. Boole anticipates a fix in their 9402
maintenance release. MXG changed IF OFFSWP GT 0 THEN DO;
to IF OFFSWP GT 0 AND OFFSWP+60 LE LENGTH+1 THEN DO; to
prevent the STOPOVER condition.
Thanks to Gavin Ring, Alcatel Australia, Australia
Change 11.264 Variable PGPERBLK in RMFINTRV was incorrectly normalized.
RMFINTRV The two lines in which PGPERBLK was multiplied/divided by
Dec 8, 1993 DURATM were deleted, and the division by BLKSAUIN was
protected for zero divide.
Thanks to Dan Squillace, SAS Institute Cary, USA.
Change 11.263 Members CHANGE01,CHANGE02... are redundant with CHANGESS,
CHANGESS which contains all changes ever made to MXG in one place,
Dec 4, 1993 so the individual CHANGEnn members now only point to the
member CHANGESS, reducing the size of the MXG library.
Searching for all MXG enhancements now involves looking
only two members: CHANGESS or NEWSLTRS. Member CHANGES
will continue to exist, repeated in CHANGESS.
Change 11.262 Support for Softworks' Performance Solution SMF records.
ADOCPRFS Three new datasets are created:
EXPRFSHL Dataset SMF Subtype Description
EXPRFSVI PRFSVIO 00 I/O Plus for VSAM Close
EXPRFSXI PRFSXIO 01 I/O Plus for XSAM Close
IMACPRFS PRFSHLP 02 HiperLoad Plus for VSAM
TYPEPRFS These data records describe the before and after buffers,
VMACPRFS etc., to track the effectiveness of this product.
Dec 2, 1993
Thanks to Yao-chun Rickert, First Chicago, USA.
Change 11.261 VM/ESA dataset VXSYTCUP (PR/SM and MLPF LPAR measurement)
VMACVMXA did not keep LCUCLPTM (LPAR Management time), so it was
Dec 1, 1993 added to the KEEP= list in macro _VSYTCUP, and is DIF'ed
in macro _DSYTCUP. Also, for inactive LPARs, MXG output
an observation, but variables LCUCPUID LCUCWGHT LCUCFLGS
LCUCACTM LCUCLPTM LCPUDED LCPUWAIT LCPUCAPD are not input
and could contain values from a prior LPAR; now they are
initialized. Similarly, VXSYTCUM logic for inactive LPARs
now initialized the un-read variables.
Thanks to Angie Olver, PERSETEL, South Africa.
Change 11.260 SAS Usage note 6886 identifies a SAS error when blank
ANALRACF characters appear between non-blank characters in an ID
Dec 1, 1993 value with PROC TRANSPOSE. In 6.06 the variables were
incorrectly left as blanks instead of being replaced by
underscores (as they were in 5.18, and are now in 6.07
and 6.08), and MXG code was actually modified between
5.18 and 6.06 to compensate. Now, however, UNINITIALIZED
variable messages result, so MXG has been re-modified to
correct. Variables _5_DATA, _6_RACF, _7_DATA,_8_NAME,
and _52_DSN are now spelled with an ending underscore:
_5_DATA_,_6_RACF_,_7_DATA_,_8_NAME_, and _52_DATA_.
Thanks to David Vaughan, Shropshire County Council, ENGLAND.
Change 11.259 A collection of data value errors have cropped up in the
VMXGHSM processing of the HSM BCDS and MCDS datasets:
Dec 3, 1993 -"Error 180" results because a semicolon is in the wrong
place. The semicolon after RECTYPE='REC TYPE ...' must
be removed, and instead a semicolon must be added to the
following line, after the label for TYPE='MCKTYPE ...'.
-"Invalid data for INPUT" results because "INPUT" should
removed from the line now reading "INPUT @65 BCRFLAGS..."
-Invalid argument for DATEJUL occurs if MCDEXPDT=99366,
95366,98000,99999,9999999 (which are invalid dates). The
calculation for MCDEXPDT was changed to set these invalid
data values to '31DEC2099'D (i.e., far into the future):
IF MCDEXPDT=99366 OR MCDEXPDT=95366 OR ...
THEN MCDEXPDT='31DEC2099'D;
ELSE IF MCDEXPDT GT 0 THEN MCDEXPDT=DATEJUL(MCDEXPDT);
ELSE MCDEXPDT=.;
-MHCRBGNT,MHCRENDT,and MHCRNXTT are now input &PIB.4.2 and
not &PK.4, the three PK1 fields after each time were
deleted, the +1 before the three dates was removed, and
the three HMS() calculations were deleted.
-DATEJUL(MHCRENDD) was changed to DATEJUL(MHCRNXTD).
-Two lines calculating DSRDATE were moved to before the
line DO I=1 to 11;
-Change DO C=1 TO MCPDGNCT; to read
IF MCPDGNCT GT 0 THEN DO C=1 TO MCPDGNCT;
-Change input of BCRTCAB from &PK.4. to BCRTCABC $CHAR4.,
delete input of BCRTCABH,BCRTCABM,BCRTCABH and following
+1, replace the BCRTCAB=HMS() line with
BCRTCAB=INPUT(BCRTCABC!!'00000000'X,TODSTAMP8.);
remove BCRTCAB from TIME8. format and instead format it
BCRTCAB DATETIME21.2.
Note: Dec 18, after 11.09 built: used similar logic for
BCRTBLA and BCRTLAB datetime variables.
-Change input of DCRCLEN from &PIB.4. to &PIB.2.
Thanks to Norbert Korsche, OMV-AG, AUSTRIA.
Change 11.258 Variables ACTDLYTM,DSPDLYTM,RESDLYTM were added by Change
IMACPDB 10.031 to TYPE30_4, but were not carried into PDB.STEPS
Nov 30, 1993 nor PDB.JOBS. They have now been added to the _PDB30_4
and _SUMSTP macros defined in IMACPDB, so they will now
exist in PDB.STEPS and PDB.JOBS.
Thanks to Bob Eastlake, Alternative Marketing Systems, USA.
Thanks to Tom Elbert, John Alden Life Insurance, USA.
Change 11.257 ASMVTOC may produce no output under MVS/ESA 3.1.3, 4.1.0,
ASMVTOC or possibly even 4.2.0. APAR OY39355 points out that DFP
Nov 22, 1993 3.3 (which introduced the new UCBSCAN COPY service) does
not run with earlier levels of MVS/ESA. If you have this
problem (no error, but no output from ASMVTOC), you can
simply comment out (by adding an asterisk in column one)
these two lines in ASMVTOC:
TM FLAG,MVSESA42 MVS/ESA V4.2 OR BEYOND?
BO MVS42AAB YES, GO USE UCBSCAN SERVICE
ASMVTOC has also failed with 213-04 when it encounters a
TPF volume. That problem is still under investigation.
Thanks to Ron Willingham, Fina Oil, USA.
Change 11.256 RMF Reports from PDB data are further corrected and
ANALRMFR enhanced. CPU percentages could be wrong, and type 74
Nov 21, 1993 reports were corrected.
Change 11.255 Support for DB2 Release 3.1.0 incompatibly altered SMF
type 100, 101, and 102 SMF records.
== added 11Jan95=======
== Messages on the log "ID=100 SUBTYPE=2 QWHSIID=202"
== tell you that you are reading DB2 3.1 SMF records
== with an old Version of MXG (MXG 11.09 or later is
== required).
ADOCDB2 100, 101, and 102 SMF records. New Datasets created are:
DIFFDB2 Dataset SMF Record Description
EXDB2ACP DB2ACCTP 101 Subtype 1 Package/DBRM executions
EXDB2ST2 DB2STAT2 100 Subtype 2 Hiperpool interval statistics
IMACDB2 Many new variables were also added to existing datasets.
VMACDB2 New variables are listed in member DOCVER11, and ADOCDB2
VMAC102 was updated with which DSECT is in which record and which
Sep 6, 1993 MXG dataset is created from which records. Details:
Nov 30, 1993 Dataset DB2ACCT:
Now contains 312 variables (was 215). New variables in
existing sections QWAC,QXST,QBAC,QTXA,and QLAC, and
new section QIFA. Variables QBACBPX and QBACSWU are
now reserved.
Dataset DB2ACCTP:
New dataset for Package/DBRM executions is built from
QPAC section(s) added to type 101 subtype 0 record (up
to ten sections will create ten observations), or from
new type 101 subtype 1 record (up to 10 per record, for
overflow if sections do not fit in existing subtype 0).
Dataset DB2STAT0:
Now contains 319 variables (was 277). New variables in
existing sections Q9ST,QWSD,QLST,QJST and QDST.
Variable QJSTWTL is now reserved.
Dataset DB2STAT1:
Now contains 447 variables (was 297). New variables in
existing sections QXST,QTST,QBST,QIST, and QTXA.
Variables QTCURPB,QTOPNOK,QTOPNNO,QTTTBRN,QTEXDRN,
QTSTDRN,QTPUBDD,QBSTBPX,QBSTSWU,and QBSTPUW are now
reserved.
Dataset DB2STAT2:
New dataset from new type 100 subtype 2 record.
Dataset T102S148:
New variables: QBnCDPF,QBnCHPG,QBnCHRE,QBnCHRF,QBnCHWF,
QBnCHWR,QBnCNGT,QBnCSIO n=1,2,3,4
Dropped vars: QBnCBPX,QBnCSWU n=1,2,3,4
Change 11.254 Support for AS/400 Version 2.3 Performance Data adds four
EXQAPDDI new datasets:
EXQAPFRL Dataset Description
EXQAPSTD QAPMDDI Distributed Data Interface (DDI) data
EXQAPSTY QAPMFRLY Frame Relay Data
IMACQAPM QAPMSTND DDI Station Counter Data
VMACQAPM QAPMSTNY Frame Relay Station
Nov 20, 1993 Changes were compatibly made, so prior versions of MXG
will not fail with the version's data records.
Change 11.253 Support for Memorex Telex LMS Version 2.17 SMF record now
EXLMSCUP creates these two new datasets:
EXLMSDAL Dataset Subtype Description
IMACLMS LMSCUP 06 Cart Update (inhibit SCR indicator)
VMACLMS LMSDALC 29 Device Allocation
Nov 20, 1993 Also, VMACLMS was restructured for consistent colimation.
Thanks to Dan Kaberon, Hewitt Associates, USA
Change 11.252 Support for Mobius INFOPAC-RDS user SMF record is added
ADOCIPAC by this comprehensive user contribution. Datasets are
ANALIPAC documented in ADOCIPAC, and sample analysis reports are
EXIPAC01 in ANALIPAC! Five new datasets are created:
EXIPAC02 Dataset Subtype Description
EXIPAC03 IPAC01 01 Batch Printing Usage Statistics
EXIPAC04 IPAC02 02 Online Printing Usage Statistics
EXIPAC05 IPAC03 03 Online Viewing Usage Statistics
IMACIPAC IPAC04 04 Archive Recall Usage Statistics
TYPEIPAC IPAC05 05 Archive I/O Subsystem Tuning & Perf
VMACIPAC And the analysis example, ANALIPAC, is comprehensive: it
Nov 19, 1993 combines the VERSIONS and DISTRIBUTION databases from
the INFOPAC-RDS product, with MXG's PDB.HSMFSRST (from
HSM), and PDB.PRINT (from JES2 printing), Vanguard's
RACF database, with three of the five SMF subtypes.
Thanks to Jeff Burnett, Anixter, USA.
Change 11.251 The ASM program to break down MVS/ESA 4.3 RMF Monitor III
ASMRMF3 segments into actual records was missing code (lost in
Nov 19, 1993 fax transmission and transcription!). The code has been
corrected, and renamed to ASMRMF3 instead of ASMMON3.
This is preliminary for MXG support of the compressed ESA
4.3 data - the SAS code to process the output of the ASM
utility is still in development. See Change 11.238.
Change 11.250 Xerox SFS records from 9700 INVALID ARGUMENT TO INPUT
VMACSFS FUNCTION occurs if CUSTJNR contains hex nulls instead of
Nov 18, 1993 blanks. Insert this line:
VAR(10)=TRANSLATE(VARS(10),'40'x,'00'x);
immediately preceding the existing line:
CUSTJNR=INPUT(VARS(10),8.);
Thanks to Doug Medland, Confederation Life Insurance, CANADA.
Change 11.249 Support for Integris' UniKix product, used to downsize
EXTYUNIA CICS VSAM and DB2 applications to the Unix environment.
EXTYUNIK The product creates a binary file of performance records
IMACUNIA and provides a conversion program to create a portable
IMACUNIK ASCII file. MXG can process either the binary or ASCII
TYPEUNIA file under UNIX, Windows, or OS/2 SAS, or the ASCII data
TYPEUNIK can be uploaded for processing under MVS SAS. This is
VMACUNIA the beta release of the UniKix measurements, and Integris
VMACUNIK will restructure the data records in their next release
Nov 17, 1993 (at my suggestion) so they will be true variable-length,
self-defining records so that future enhancements can be
made to the data records compatibly, so the MXG support
will be revised when those changes are available.
The current implementation members ....UNIA are for the
ASCII file (infile name UNIKIXAS), and members ....UNIK
are for the Binary file (infile name UNIKIXBI).
Change 11.248 Support for BatchPipes/MVS type 91 SMF record creates 11
EXTY9101 new datasets:
EXTY9102 Dataset Subtype Description
EXTY9103 TYPE9101 01 Subsystem Initialization
EXTY9104 TYPE9102 02 Subsystem Interval
EXTY9111 TYPE9103 03 Subsystem Termination
EXTY9112 TYPE9104 04 Subsystem Parms Changed
EXTY9113 TYPE9111 11 Pipe Connection Open
EXTY9114 TYPE9112 12 Pipe Connection Interval
EXTY9115 TYPE9113 13 Pipe Connection Close
EXTY91IC TYPE9114 14 Pipe Create
EXTY91OC TYPE9115 15 Pipe Delete
IMAC91 TYPE91IC 11-13,15 Input Connection Details
TYPE91 TYPE91OC 11-13,15 Output Connection Details
VMAC91 Subtypes 1 and 3 are Pipes Subsystem event records.
Nov 17, 1993 Subtypes 2 and 4 are interval or termination records with
statistics on each Pipes Subsystem (pipes/connections
created/deleted/active, input/output bytes, etc.).
Subtype 11-15 are Pipe Connection records, which identify
the pipename being accessed, and (for subtype 12 and 15)
contain pipe activity counts. In addition, subtypes 11,
12, 13, and 15 can contain one or more Connection Detail
sections (either Input or Output connection), so MXG
creates one observation in TYPE91IC or TYPE91OC for each
Connection Detail segment (which contains JOB,READTIME,
DDNAME, six timestamps, reads/writes, bytes in/out, etc.)
for each user of a pipe. This structure lets you analyze
overall pipe statistics with the subtype datasets, or the
pipe statistics by user with the IC/OC detail datasets.
MVS Pipes looks to be a very powerful new MVS facility!
Change 11.247 Support for Novell Network Navigator user SMF record now
EXTYNNAV creates one dataset:
IMACNNAV Dataset Description
TYPENNAV TYPENNAV Network Navigator Session Resources
VMACNNAV with session logon and logoff datetimes, JESNR, bytes
Nov 16, 1993 sent/received, and TGETS/TPUTS for the session.
Thanks to Elena Beryozkin, United Parcel Service, USA.
Change 11.246 Support for NetView Performance Monitor NPM Version 2.1.0
EX028NWC added major enhancements, especially in the area of VTAM
EX028NWD monitoring, with CPU and storage used by VTAM. Thirteen
EX028RMA new datasets are created:
EX028RMD Dataset Subtype Description
EX028VAP NPMRMSTR BA RTM ACTIVATE
EX028VAD NPMRMSTP BB RTM DEACTIVATE
EX028VBF NPMVTSTR D0,D1,D2 VTAM START/STOP/MD
EX028VEN NPMVTEXC D3,D4 VTAM EXCEPTION
EX028VDV NPMVSVEN D5 VTAM ENVIRONMENTAL
EX028VGB NPMVSVGB D6 VTAM GLOBAL
EX028VTE NPMVSVBF D7 VTAM BUFFER POOL
EX028VTS NPMVSVDV D8 VTAM DEVICE DATA
EX028VVR NPMVSVVR D9 VTAM VIRTUAL ROUTE
FORMATS NPMVSVAP DA VTAM APPLICATION
IMAC28 NPMVSVAD DB VTAM ASID DATA
VMAC28 NPMNWCWC FC WRKSTN-NPM CONNECT
Nov 13, 1993 NPMNWDWD FD WRKSTN-NPM DISCON
Change 11.245 The original change described in this text in MXG 11.07
VMXGSUM thru MXG 11.09 were never actually implemented. The text
Nov 12, 1993 of the change was written, but the VMXGSUM member was not
moved into the MXG library, because the KEEPIN= logic did
not produce identical output datasets, and it had to be
backed out of the changes. See Change 11.281 & 11.309.
Change 11.244 A new utility, UCICSCNT counts how many SMF type 110 CICS
UCICSCNT records come from each CICS Region, by CICS version, and
Nov 10, 1993 by record subtype, so you can prove to your CICS guru
which APPLIDs have monitoring and/or statistics records.
Thanks to Richard S. Ralston, Whirlpool Corporation, USA.
Change 11.243 Support for NETWISE's RPC EXEC product type 33 SMF record
VMAC33 adds these "accounting" fields to dataset TYPE33_1:
Nov 9, 1993 NETWCAPN,NETWCOMP,NETWCORR,NETWMDNM,NETWRPCM,NETWRPCN,
NETWRPCN,NETWRPCT and NETWSAPN. MXG now creates one obs
in TYPE33_1 for each TPUSE section; previously only the
first TPUSE section's data was output. With NETWISE's
data, there are two sections in each record, one for the
inbound and one for the outbound connections, so there
two observations for each NETWISE SMF record.
Thanks to Linda Marzik, EDS Performance and Evaluation Group, USA.
Change 11.242 DB2 variable NETSNAME still can have blanks, after Change
VMACDB2H 11.050, preventing DB2ACCT matching with CICSTRAN. This
Nov 8, 1993 happens if the last half of NETSNAME contains blanks; the
correction is to translate all blanks in DB2 NETSNAME to
nulls. After the NETSNAME algorithm, and just before
"/* CREATE UOWTIME FROM QWHCTOKN */", insert the line:
NETSNAME=TRANSLATE(NETSNAME,'00'X,'40'X);
Thanks to Edward McCarthy, Health Insurance Commission, AUSTRALIA.
Change 11.241 TRNDRMFI will fail with VARIABLE PLATCPUS NOT FOUND when
TRNDRMFI ASUM70PR is not executed. Add in the INCODE= section:
Nov 8, 1993 IF PLATCPUS=. THEN PLATCPUS=.; just like PARTNCPU.
There is no requirement to run ASUM70PR before TRNDRMFI,
but without it, PLATCPUS did not exist, until the change.
Thanks to Tom Elbert, John Alden Life Insurance, USA.
Change 11.240 Variables READY12 READY13 READY14 READY15 were left out
TRND70 of the NORM2= list in this trending member, causing their
Nov 8, 1993 summary values to be erroneously large.
Thanks to Tom Elbert, John Alden Life Insurance, USA.
Change 11.239 MXG Early PreRelease 11.08 only. IF ID=80 SOURCE='RACF';
ANALSMF should have been IF ID=80 THEN SOURCE='RACF';
Nov 8, 1993
Thanks to Freddie Arie, Lone Star Gas, TEXAS.
==Changes thru 11.238 were included MXG Early PreRelease 11.08 01Nov93=
Change 11.238 This new Assembler program reads the RMF Monitor III VSAM
ASMMON3 files from MVS/ESA 4.3 (which are compressed, and are not
Oct 30, 1993 standard records). It was typed from a fax, and has not
been tested, but I wanted to make it available for tests
because there are reported problems in the ZRB processing
that are still unresolved. See Change 11.251.
Thanks to Don Friesen, B.C. Systems, CANADA.
Change 11.237 ANALDB2R could not use a PDB on tape for reports, because
ANALDB2R multiple datasets were opened simultaneously, but with a
Oct 30, 1993 new TREND= parameter, either the Accounting or Statistics
reports can be run from your PDB= on tape. Only if you
want to include your TREND data base and your PDB data
bases together for a report will you need to point TREND=
to the DDname for your TRNDDB2A, TRNDDB20, and TRNDDB21
datasets.
Change 11.236 Internal logic was improved for performance. If the first
VMXGSUM data step or the SORT is not needed, they are bypassed.
Oct 30, 1993 This can reduce CPU and DASD requirements significantly.
If no INCODE=, no INTERVAL=, no SHIFT=, and no NORMX= are
used and there is only one input dataset, the first data
step is bypassed. If there is no SUMBY=, then no SORT.
Unfortunately, most of the ASUMxxxx and TRNDxxxx members
that invoke VMXGSUM do not meet the criteria and see no
benefit, but ANALDB2R gets some help, and it is the
righteous thing to do anyhow. See Change 11.309.
Change 11.235 Trending of VM/XA and VM/ESA MONWRITE dataset VMXAINTV
TRNDVMXA had logic errors, that causes several variables to be
Oct 30, 1993 incorrect.
Thanks to Sean Chaffee, Amadeus Data Processing GmbH & Co., GERMANY.
Change 11.234 Support for SMF type 42 subtype 14 (IBM ADSM Distributed
VMAC42 Storage Management Product) provides good statistics in
Oct 30, 1993 the new TYPE42AD dataset, with counts of byte traffic
and objects, for backup and archived files moved between
client and server, as well as CPU time plus waiting time
for Communications or Media, and session idle time.
The only identifiers, however, are the client name and
the client owner name. Unrelatedly, but because VMAC42
was "open", DFSMS Data Set, Storage Class, and Total
datasets were enhanced with read and write hit percents.
Thanks to Peggy Schulte, Cincinatti Gas and Electric Company, USA.
Change 11.233 SAS option SORTDEV=3380 was removed from MXG's CONFIG
CONFIG members - it is not needed, and caused errors at sites
Oct 30, 1993 that have no 3380s.
Thanks to Freddie Arie, Lone Star Gas, TEXAS.
Change 11.232 Variable AVGMTPTM was retained across device records that
VMAC74 had no Mount Pending. After its calculation, insert
Oct 30, 1993 ELSE AVGMTPTM=.;
Change 11.231 Additional enhancements and corrections to RMF reports.
ANALRMFR MXGCPU - Added OMVSMAX,OMVSAVG statistics.
Oct 30, 1993 MXGPAGE - Added OMVS00-OMVS11 statistics
MXGDEVC - DEVMTPTM to DEVACTTM, changed summary BY LCU
for calculation of AVGMTPTM.
MXGSMRY - BY SYSTEM DATE TIME changed to BY SYSTEM DATE