COPYRIGHT (C) 1984-2007 MERRILL CONSULTANTS DALLAS TEXAS USA
CHANGE 13.13
==========MXG 13.13 dated Jan 20, 1996, thru Change 13.332============
=========================member=CHANGE13================================
/* COPYRIGHT (C) 1984-1996 MERRILL CONSULTANTS DALLAS TEXAS USA */
This is MXG Version 13.13, dated Jan 20, 1996, thru Change 13.332.
MXG Version 13.13 is dated Jan 20, 1996, thru Change 13.332
Newsletter TWENTY-NINE, dtd Jan 20, 1995, thru Change 13.323
MXG Version 13.09 was dated Jan 10, 1996, thru Change 13.313
MXG Version 13.08 was dated Dec 15, 1995, thru Change 13.290
MXG Version 13.07 was dated Oct 30, 1995, thru Change 13.253
MXG Version 13.06 was dated Oct 10, 1995, thru Change 13.225
MXG Version 13.05 was dated Aug 21, 1995, thru Change 13.172
Early MXG Version 13.05 was dated Aug 11, 1995, thru Change 13.162
Newsletter TWENTY-EIGHT, dtd Aug 21, 1995, thru Change 13.162
MXG Version 13.04 was dated Jul 31, 1995, thru Change 13.149
MXG Version 13.03 was dated Jul 19, 1995, thru Change 13.120
MXG Version 13.02B was dated Jul 6, 1995, thru Change 13.111
MXG Version 13.02A was dated Jun 28, 1995, thru Change 13.101
Initl MXG Version 13.02 was dated Jun 19, 1995, thru Change 13.095
Real MXG Version 13.01 was dated May 3, 1995, thru Change 13.055
PreRe MXG Version 13.01 was dated Apr 26, 1995, thru Change 13.046
Early MXG Version 13.01 was dated Apr 1, 1995, thru Change 13.011
MXG Version 12.12A was dated Mar 20, 1995, thru Change 12.328
MXG Version 12.12 was dated Mar 1, 1995, thru Change 12.314
MXG Newsletter TWENTY-SEVEN, Mar 1, 1995, thru Change 12.306
Contents of member CHANGES:
I. MXG Software Version Status.
II. MXG Technical Notes
III. MVS Technical Notes
IV. DB2 Technical Notes
V. IMS Technical Notes
VI. SAS Technical Notes
VII. CICS Technical Notes
VIII. Incompatibilities and Installation of MXG 13.13.
IX. Online Documentation of MXG Software.
X. Changes Log
I. MXG Software Version Status.
1. MXG Software Version 13.13, dated January 20, 1996, was shipped
with newsletter, NEWSLETTER TWENTY-NINE.
Major enhancements added in MXG 13.13 dated Jan 20, 1996:
Added after Newsletter 29 was sent to the printer:
Support for 4-digit UCBs in DCOLLECT, ASMVTOC and ASMVVDS.
Support for DOS/VSE POWER 5.2 Accounting Records
Support for MVS Catalog records (Exported with IDCAMS)
Included in Newsletter 29 list of enhancements in MXG 13.13:
Support for BETA 93 Release 1.06.50 (INCOMPATIBLE)
MXGVERSN variable added to TYPE70 and RMFINTRV.
Support for Frye Systems measurement of Netware LANS
Support for Blue Line Software 4.03 and 4.04 (INCOMPAT) and 4.10.
Sample conversion of DBaseIII files into SAS datasets.
Workaround for SAP and IBM CICS 2.1 interleaved records.
ASCII execution of BUILDPDB and PROC FORMATS now transparent.
TESTMWX for improved CPU capture in User records.
Major enhancements added in MXG 13.09 dated Jan 10, 1996:
Support for DFSMS/MVS 1.3 DCOLLECT records (compatible).
Support for DFSMS/MVS 1.3 VSAM RLS fields in type 64 (compatible).
Support for DFSMS/MVS 1.3 VSAM RLS fields in type 42 (compatible).
Support for MVS/ESA 5.2.2 Open Edition OMVS type 92 (INCOMPATIBLE).
Support for MVS/ESA 5.2.2 Open Edition OMVS type 30 (compatible).
Sample HSM reports and analysis suggestions
TYPE6 INPUT STATEMENT EXCEEDED for PSF type 6 with OW10067.
CICS/ESA 4.1 corrections (TRANTYPE, ELAPSTM, ENDTIME, IRESPTM)
CICS/ESA 3.3 UNEXPECTED STATISTICS with STILEN=0 protection.
MEASUREWARE (old HP-PCS) CPU time error in HPxxGLOB,HPxxAPPL.
Landmark TMON for UNIX enhancements, corrections and errors.
Major enhancements added in MXG 13.08 dated Dec 15, 1995:
Support for MVS Solution's MVS Thruput Manager SMF record.
Support for VM/ESA SQL/DS Remote User Accounting Record (INCOMPAT)
Support for Landmark's TMON for UNIX.
Support for TANDEM D20 and D30 and D40 releases.
Support for DB2 4.1 IFCIDs 221, 222, and 231.
Support for IDMS 12.01 (INCOMPATIBLE) was not correct until 13.08.
Support for TOPSECRET 4.4 and 5.0 (INCOMPATIBLE) added.
Support for HSM ABARS ABACKUP/ARECOVER FSR segment validated.
Support for SAP 5.0 INCOMPATIBLE changes to type 110 journal data.
MAINTLEV 7 of MXG Tape Mount and Allocation Monitor.
Replacement for CICINTRV available for testing.
"XMXGSUM" architecture now replaces VMXGSUM.
SYSNAME and SYSPLEX added to PDB.JOBS/STEPS/PRINT.
Default ASUMCICS summarization now includes USER.
JESNR may show only four digits in TYPE26; IBM lied in ESA 5.2
DEVPLX (duplex volume) address wrong, IBM worrying.
Major enhancements added in MXG 13.07 dated Oct 30, 1995:
Support for DB2 4.1.0 type 100 and 101 SMF records.
Support for STK SILO HSC VIEW Command Subtype 8 SMF record.
Support for MODEL204 Release 3.0
CICS/ESA 4.1 CICSTRAN variables STRTTIME/ENDTIME now GMT-corrected.
New IMACSPCK exit for SPIN decision override.
New IMACZDAT localizes creation of ZDATE, for ease in reruns.
Corrections for Landmark Version 2 TMDB support.
Major enhancements added in MXG 13.06 dated Oct 10, 1995:
ASMTAPES revision MAINTLEV 6 is now included, resolves errors.
TYPETMON (TMON CICS 1.3) must now use RECFM=VB instead of RECFM=U.
Support for Landmark TMON for DB2 Version 2.
Support for Tandem D20 MEASURE CPU, Disk, and Process data records.
Support for COM-PLETE Version 4.6 SMF record.
Support for ISOGON Soft Audit Version 4.1.
Support for HSM ABARS ABACKUP/ARECOVER FSR segment.
Support for APAR OW14717 and APAR OW16039 for SMF type 42.
Support for Omegamon for MVS/ESA V400 adds variables.
Support for 3590 tape drives now complete.
Support for APAR OW11142 adds new fields to TYPE64.
Support for Software Engineering of America's TRMS SMF record.
MXG 13.01-MXG 13.05, IMACJBCK caused deletion of RACF, ACF2 and DB2
observations with job name of nulls. See Change 13.183.
ANALDB2R may still get FORMAT NOT FOUND, assorted minor DB2 fixes.
Major enhancements added in MXG 13.05 dated Aug 21, 1995:
Added after Newsletter TWENTY-EIGHT was printed:
Support for MVS/ESA 5.2.2.
Support for Candle Omegamon 300 SMF record (incompatible).
Support for Landmark's TMON/MVS 1.2/1.3 additional subtypes.
Preliminary support for 3590 tape drives.
Correction for VM/ESA INVALID CONTROL RECORD error.
Announced in Newsletter TWENTY-EIGHT:
Support for the year 2000 (see MXG Technical note in NEWSLTRS, NL28)
Support for OpenMVS File System I/O type 92 SMF record.
Support for MVS/ESA 5.2 System Logger Data type 88 SMF record
Support for EREP (SYS1.LOGREC) records.
Deaccumulation of HMF records.
Final (?) Correction to ANALDB2R Statistics and Audit Reports.
If you use either the DB2 Statistics reports or DB2 Audit Reports,
you must request MXG 13.05 for the ANALDB2R corrections to errors
introduced in MXG 12.12 (Statistics) or MXG 13.01 (Audit) that were
not fixed until now (I apologize for the careless coding and lack
of validation of report output that took seven iterations to fix).
The Audit errors were actually corrected in 13.03, but Statistics
still had four values that were not corrected until MXG 13.05.
The more-commonly-used DB2 Accounting Reports had no errors.
MAINTLEV 6 of ASMTAPES was listed in Newsletter 28, but is not on
the MXG 13.05 tape; see text of Change 13.163.
Major enhancements added in MXG 13.04 dated Jul 31, 1995:
Support for NetCompress SMF records.
Support for Packet/Main SMF records.
Support for Kodak AXCIS Optical Disk SMF records.
Major enhancements added in MXG 13.03 dated Jul 19, 1995:
More fixes for DB2 Statistics Reports, a fix for DB2 Audit Reports.
TYPE116 (MQM) validation and correction.
Major enhancements added in MXG 13.02B dated Jul 6, 1995:
Correction to DB2 Statistics Summary and Audit Reports
MXG Position Paper on Support for Year2000 in member YEAR2000.
Major enhancements added in MXG 13.02A dated Jun 28, 1995:
Correction to DB2 PMSSTA01/02 Statistics Summary Reports.
Final (?) revisions to XMXGSUM.
Major enhancements added in MXG 13.02 dated Jun 19, 1995:
Support for MVS/ESA 5.2 (compatible) changes 24, 30, and 42 records.
Support for OPC Release 3.0 (INCOMPATIBLE).
Support for DFSORT Release 13.0 (INCOMPATIBLE).
Support for TMS (CA-1) Release 5.1 (compatible).
Support for Antares' HURON ObjectStar SMF record.
Support for TYPE32 APARS OW10393 (causes error) and OW12856 (none).
Support for SAP Release 5.0 CICS accounting in type 110.
Support for ACS Wylbur Accounting SMF record
Support for Sterling SAMS Storage Automation SMF record.
Support for LEGENT's AUTOMATE SMF record.
DB2 Audit SQL text corrections.
Support for APAR OW08641 for NPM Version 2.2
Major enhancements added in MXG 13.01 dated May 3, 1995:
Support for NETSPY Release 4.6 (compatible), divide by zero fixes.
Support for HP PCS current version on HPUX, AIX, and SUN unix.
Support for OS/400 Version 3.1.0 (was wrong in MXG 12.12/12.12A).
Support for TCP/IP APAR PN69321-PN69322.
Support for Sterling SOLVE NCL CPU-time accounting user SMF.
Support for HMF SMF record subtypes 4 and 5.
Support for APAR OW04653 added variables to TYPE74ST dataset.
Support for IBM's IRRDBU00 RACF Database Unload.
ASMRMFV 0C4 correction and enhancements for RMF VSAM processing.
ANALCNCR enhancements and validation.
XMXGSUM enhancements and validation.
TYPE116 (MQM) validation and correction.
Major enhancements added in MXG 12.12A dated Mar 20, 1995:
Twelve MXG 12.12 members had errors that are now fixed:
ANALCNCR ANALDB2C ANALDB2R ANALPATH ANALTALO IMACICSA
TRNDTALO VMAC80A VMAC110 VMACILKA TYPEMON8 TYPETMON
Support for Memorex/Telex LMS Version 3.1 (INCOMPATIBLE).
All of these 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
MVS/ESA 4.1 Oct 26, 1990. 8.8
MVS/ESA 4.2 Mar 29, 1991. 9.9
MVS/ESA 4.2.2 Aug 1991. 9.9
MVS/ESA 4.3 Mar 23 1993. 10.10
MVS/ESA 5.1.0 - compatibility Jun 24, 1994 12.02
MVS/ESA 5.1.0 - Goal Mode May 3, 1995 13.01
MVS/ESA 5.2.0 Jun 15, 1995 13.05
MVS/ESA 5.2.2 Oct 19, 1995 13.09
CICS/ESA 3.2 Jun 28, 1991. 9.9
CICS/ESA 3.3 Mar 28, 1992. 10.01
CICS/ESA 4.1 Oct 27, 1994. 13.09
CICS/ESA 4.2 when G.A. ??.??
CRR 1.6 Jun 24, 1994. 12.02
DB2 2.2.0 1990 8.8
DB2 2.3.0 Oct 28, 1991. 10.01
DB2 3.1.0 Dec 17, 1993. 13.02A
DB2 4.1.0 Nov 7, 1995 13.07
DFSMS/MVS 1.1 Mar 13, 1993. 11.11
DFSMS/MVS 1.2 Jun 24, 1994. 12.02
DFSMS/MVS 1.3 Dec 29, 1995. 13.09
NPM 2.0 Dec 17, 1993. 12.03
NPM 2.2 Aug 29, 1994. 12.05
VM/ESA 1.1.1 Dec 27, 1991. 10.01
VM/ESA 2.0 Dec 23, 1992. 10.04
VM/ESA 2.1 Jun 27, 1993. 12.02
VM/ESA 2.2 Nov 22, 1994. 12.06
Table MXG support for non-IBM products:
Availability MXG Version
Product Name Date Required
Landmark
The Monitor for DB2 Version 2 13.06
The Monitor for CICS/ESA 1.2 - 12.12
The Monitor for CICS/ESA 1.3 - 12.12A
The Monitor for MVS/ESA 1.3 - 12.05
Candle
Omegamon for CICS V300 User SMF 12.05
Omegamon for CICS V400 User SMF 13.06
Omegamon for IMS V110 (ITRF) 12.12
Omegamon for MVS - last MXG change 1992 12.12
Omegamon for DB2 Version 2.1/2.2 13.05
Omegamon for VTAM V160 12.04A
Omegamon for SMS V100/V110 12.03
Boole & Babbage
IMF 3.1 (for IMS 5.1) 12.12
Memorex/Telex
LMS 3.1 12.12A
II. MXG Technical Notes.
III. MVS Technical Notes after Newsletter TWENTY-NINE.
IV. DB2 Technical Notes.
V. IMS Technical Notes.
VI. SAS Technical Notes.
VII. CICS Technical Notes.
VIII. Incompatibilities and Installation of MXG 13.13.
1. Incompatibilities introduced in MXG 13.13 (since MXG 12.12):
a- IMACs that were changed (if they exist in your USERID.SOURCLIB, you
must refit your tailoring, starting with the new IMAC member):
IMACPDB (Change 13.198)
IMACJBCK (Change 13.183)
b- Other incompatibility changes:
Member FORMATS cannot be executed as-is under SAS Version 5.18,
but can be tailored if you are still running that archaic version.
See Change 13.127
User-written invocations of VMXGSUM with OUTCODE= to recalculate
the DATETIME= variable may be wrong. See Change 13.152.
c- These products were incompatibly changed by their vendor, and they
require MXG 13.xx as indicated:
Memorex/Telex LMS 3.1 (Change 12.326, MXG 12.12A)
OPC Release 3.0 (Change 13.092, MXG 13.02)
DFSORT Release 13 (Change 13.092, MXG 13.02)
Hipercache 4.1.x (Change 13.120, MXG 13.03)
BETA 93 Release 1.06.50 (Change 13.304, MXG 13.09)
OMEGAMON/MVS Version 300 (Change 13.170, MXG 13.05)
IDMS/R 12.01 Maint 9506 (Change 13.223, MXG 13.06)
TMON/CICS 1.3 (Change 13.204, MXG 13.06)
SAP 5.0 type 110 journal (Change 13.261, MXG 13.08)
TOPSECRET 4.4/5.0 (Change 13.254, MXG 13.08)
OPEN EDITION MVS 5.2.2 (Change 13.313, MXG 13.13)
VM/ESA SQL/DS Accounting (Change 13.xxx, MXG 13.yy)
IMS 5.1 (Change 13.265, MXG 13.xx)
Model204 Release 3.0 (Change 13.249, MXG 13.xx)
TMON/DB2 Version 2 (Change 13.224, MXG 13.xx)
TYPE42 APAR OW14717 (Change 13.217, MXG 13.xx)
2. Installation and re-installation procedures are described in detail;
in member INSTALL (which also lists common Error/Warning messages a
new user might encounter), and sample JCL is in member JCLINSTL:
Summary:
a. Install member MXGSAS as JCL Procedure MXGSAS in your PROCLIB.
b. Allocate a 105-cyl PDS: MXG.V1313.MXG.SOURCLIB, and use IEBUPDTE
to read the MXG tape to create the 2937+ member Source Library.
c. Allocate a 1-cyl PDS: MXG.V1313.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 V1313.USERID.SOURCLIB.
d. Allocate a 1-cyl SAS Data Library: MXG.V1313.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.V1313.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.V1313.USERID.SOURCLIB. Then, compare the
members in your USERID.SOURCLIB with the list of members that
were incompatibly changed (above, in this section) in this MXG.
If any of the incompatibly changed members exist in your dataset
MXG.V1313.USERID.SOURCLIB, then you must reinstall your site's
tailoring for that IMAC, starting with the IMAC member from the
MXG 13.13 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 13.13 in its own set of libraries. When
parallel testing is complete and are ready to implement MXG 13.13
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.V1313.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:", "ERROR :", " NOT "
"UNINITIALIZED", "TRUNCATED", "NEVER BEEN", "NOT FOUND", "CONVERT",
"APPARENT", and "NOT CATLGD", as they usually 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. Online Documentation of MXG Software.
Since 1994, the contents of the two MXG Books, (the 1984 MXG Guide, and
the 1987 MXG Supplement) are contained in the MXG Source Library, as are
all MXG Technical Newsletters and all MXG Changes, so all MXG
documentation is actually online in the software itself; even the
Installation Instructions are online, in members INSTALL/JCLINSTL!
ACHAPxxx members are the text of the 42 chapters from the two MXG books,
to which the text from newsletters and changes has been added. Some of
these chapters are still rough; while some of the chapters have actually
been completely revised, many of these ACHAPxxx are little more than a
concatenation of the two original chapters, often without the figures
or tables. The revision is work still in progress!
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 data, references to MXG reports that use these data,
and the MXG member names that you use to process that product. While
this too is work in progress, the most heavily used data sources,
especially the common SMF records, have been revised and are up to date.
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, because of MXG naming conventions:
IMACxxxx - Defines record IDs, and the _Lyyyzzz and _Kyyyzzz macros
that name the dataset(s) created from product xxxx.
ADOCxxxx - "Chapter FORTY" style dataset and variable documentation of
all datasets created from product xxxx, with sample output.
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 tailoring of each MXG dataset, not used by
most MXG sites, but powerful if needed. There can be more
than one dataset created from one product. The yyyzzz
suffix of the EXyyyzzz member name is the same as the
suffix of "_L" and "_K" macros defined in the IMACxxxx for
its product. See 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.
Member CHANGES identifies this Version and Release of MXG Software, and
describes all changes made in this Release, plus new technical notes.
Member CHANGESS contains each of the CHANGES members from each version
of MXG, so this member contains ALL changes ever made to MXG Software.
Since each MXG change lists the names of the members that were added or
altered, names the new product/version supported by a change, or lists
error messages corrected by a change, this member is designed to be read
online (with SPF BROWSE); you can search for specific product acronyms
(CICS, MVS/ESA, etc.), or the MXG member name or anything else. Many of
the changes are actually mini-tutorials, especially for new products.
Member NEWSLTRS contains the text of all newsletters. You can search
NEWSLTRS for product name or acronym to find all of Dr. Merrill's
published and unpublished technical papers, technical notes announcing
enhancements in new operating systems or subsystems, new datasets and
products, important APARs and PTFs, and other technical information of
importance to MXG users. (Since the Change Log that is printed in each
newsletter is in member CHANGESS, it is not repeated in NEWSLTRS.) MXG
Technical Newsletters are typically published twice a year, with one
printed copy sent to each licensed site's technical addressee.
Member DOCVER lists alphabetically ALL datasets and variables that are
built by this MXG Software Version, abbreviated to a line per variable.
Members DOCVERnn are the "delta-documentation" between MXG versions, and
list only those datasets and variables that were added/deleted/changed
by version "nn", so you can identify when a variable/dataset was added.
Finally, remember that MXG is source code, and you can often find your
answer by BROWSING the source members, especially the VMACxxxx members.
The MXG Variable name is frequently the vendor's field name, or the
vendor's field name is often in a comment adjacent to the variable's
INPUT, so you can cross reference MXG to the vendor's documentation.
The migration from print to online is clearly work in progress, but at
least the two books are now machine readable! When all 42 chapters
are completely revised and updated in the source library, I will decide
which, if any, will also be made available in printed form, but the
primary media for all future MXG documentation will be these members of
the MXG source library, which can be immediately updated in each new
version of MXG as changes occur.
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 than 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 after MXG 12.12:
Dataset/
Member Change Description
Many 13.190 Format of UOWTIME changed to DATETIME25.6 everywhere.
Many 13.198 Support for 3590 tape drives.
ADOCFRYE 13.317 Sample conversion of DBaseIII files into SAS datasets
ANALALL 13.076 Print of All SMF records from a job was enhanced.
ANALAPAF 13.014 Semicolon missing in report program.
ANALCISH 13.046 Report enhancements for CICS Shutdown reports.
ANALCISH 13.113 CICS Shutdown may cause NOTSORTED error.
ANALCISH 13.274 Lots of page ejects corrected.
ANALCNCR 13.036 Validation closed several exposures.
ANALCNCR 13.047 ANALCNCR failed when invoked by ANALTAPE or ANALMTP.
ANALCNCR 13.280 Correction of Dataset Not Found condition.
ANALDB2C 12.318 NO MATCHING IF error because colon vice semicolon.
ANALDB2R 12.328 Syntax errors with PMACC01 or PMACC02 report.
ANALDB2R 13.042 DBID/OBID mapping enhanced to include timestamp.
ANALDB2R 13.058 BY VARIABLE STRTTIME IS NOT ON INPUT DATA error.
ANALDB2R 13.079 DB2 Statistics Summary PMSTA01, Audit report fixes.
ANALDB2R 13.106 Statistics Report correction, FORMAT NOT FOUND.
ANALDB2R 13.118 Final (?) corrections to Statistics and Audit Reports
ANALDB2R 13.159 More Statistics Report errors, but at field level.
ANALDB2R 13.191 $DB2DBID FORMAT NOT FOUND may still occur in 13.05.
ANALDB2R 13.278 Enhancements only! No errors reported!
ANALHSM 13.307 Analysis of HSM SMF record HSMFSRST data.
ANALPATH 12.325 Cross-System DASD Reports cols ran together.
ANALPATH 13.207 INVALID ARGUMENT error in report program.
ANALPGNS 13.003 Failed if you changed RMFINTRV duration in IMACRMFI.
ANALRMFR 13.134 Data/time selection crossing midnight failed.
ANALTALO 12.327 VARIABLE NOT FOUND error.
ANALTALO 13.006 Variable SYSTEM NOT FOUND in MXG 12.12A.
ANALTAPE 13.037 All-systems report was missing.
ANALTAPE 13.286 ERROR:KEYWORD PARAMETER in MXG 13.06-13.07 only.
ASMIMSLG 13.265 IMS 5.1 changes, untested.
ASMRMFV 13.027 0C4 ABEND if no enqueue table, additional records.
ASMTAPES 13.135 MAINTLEV 4 of MXG Tape Mount and Allocation Monitor
ASMTAPES 13.163 MAINTLEV 5 of MXG Tape Mount and Allocation Monitor
ASMTAPES 13.187 MAINTLEV 6 of MXG Tape Mount and Allocation Monitor
ASMTAPES 13.282 MAINTLEV 7 of MXG Tape Mount and Allocation Monitor.
ASMVTOC 13.331 Support for 4-digit UCBs.
ASMVVDS 13.330 Support for 4-digit UCBs.
ASUMCICS 13.268 Default summarization now includes USER.
BUILDPDB 13.320 CODEPASS=2 now set only for MVS execution.
CICINTRZ 13.281 Replacement for CICINTRV available for testing.
DIFFDB2 13.212 Removed DB2STAT2 from DIFFDB2 create of DB2STATS.
DIFFDB2 13.269 Variables QBSTHPL/QBSTVPL removed from DIF().
FORMATS 13.061 All MXG formats for hex values use OTHER= syntax.
FORMATS 13.127 MXG FORMATS member incompatible with SAS Version 5.
FORMATS 13.319 OTHER= syntax now works under MVS or ASCII.
GRAFLPAR 13.060 MXG 13.01 only. NAME uninitialized error.
IMACFILE 13.109 Select CICS records by APPLID/SUBTYPE example.
IMACICSA 12.324 SAP Journal data times formatted correctly.
IMACICSA 13.077 CICS SAP variable STCTIMTR may be wrong.
IMACICSA 13.199 SAP variable STICODE changed from Numeric to Char.
IMACPDB 13.271 SYSNAME and SYSPLEX added to PDB.JOBS/STEPS/PRINT.
IMACSPCK 13.241 New BUILDPDB/BUILDPD3 exit for SPIN override.
IMACZDAT 13.237 ZDATE creation now localized, for ease in reruns.
JCLDAYDS 12.316 DCOLLECT output LRECL=644 instead of LRECL=264.
JCLPDB6 13.018 Member ASUMDB2S does not exist error.
MONTHBLD 13.015 SORT error building monthly TYPE72, wrong BY list.
REXXDB2 13.284 REXX program to convert DB2 GTF records corrected.
RMFINTRV 13.213 TSOxxxxx response variables FORMAT now 7.3.
SASAFIX1 13.239 S370FRBn informat replacement .DLL for ASCII SAS.
TRNDDB2S 13.031 Variables QTPUBD and QTXAIRL incorrect spellings.
TRNDTALO 12.327 Syntax error due to missing comma.
TYPEACF2 13.112 ACF2 subtype "L" logic (ACF2JR dataset) redesigned.
TYPEACHE 13.005 CRR 1.6 with 3990-6 in Basic Move, values wrong.
TYPEAUTO 13.091 Support for LEGENT's AUTOMATE SMF record.
TYPEAUTO 13.102 Corrections to initial support for AUTOMATE.
TYPEAXC 13.149 Support for Kodak AXCIS Optical Disk SMF records.
TYPEBETA 13.322 Support for BETA 93 Release 1.06.50 INCOMPATIBLE.
TYPECACH 13.103 Support for 4-digit UCB in Cache RMF Reporter data.
TYPECACH 13.262 DEVPLX (duplex volume) address wrong, IBM worrying.
TYPECOMP 13.222 Support for COM-PLETE Version 4.6 SMF record.
TYPECTLG 13.325 Support for MVS Catalog Records exported by IDCAMS.
TYPEDB2 13.212 Dataset DB2STAT2 was incomplete.
TYPEDB2 13.244 Support for DB2 4.1.0 type 100 and 101 records.
TYPEDCOL 13.105 INPUT STATEMENT EXCEEDED with SMS 1.2 DCOLLECT.
TYPEDCOL 13.295 Support for DFSMS/MVS 1.3 DCOLLECT records (COMPAT).
TYPEDCOL 13.332 Support for 4-digit UCBs.
TYPEDOS 13.328 Support for DOS/VSE POWER 5.2 Accounting Records.
TYPEEDGS 13.124 IBM RMM SMF record INVALID DATA FOR MDUCDATE.
TYPEEPMV 13.170 Support for OMEGAMON/MVS Version 300 (INCOMPAT).
TYPEEPMV 13.201 Support for Omegamon for MVS/ESA V400 adds variables.
TYPEEREP 13.164 Support for EREP/SYS1.LOGREC records.
TYPEEREP 13.208 EREP gets INVALID DATA FOR DTL, additional support.
TYPEEREP 13.270 INPUT STATEMENT EXCEEDED error corrected.
TYPEFRYE 13.317 Support for Frye Systems LAN measures for Netware.
TYPEHIPR 13.120 Support for Boole & Babbage HiperCache V1.4.3.
TYPEHMF 13.038 Support for HMF subtypes 4 and 5.
TYPEHMF 13.165 Deaccumulation of HMF records.
TYPEHPAI 13.010 Support for HP-PCS data from AI UNIX.
TYPEHPSU 13.010 Support for HP-PCS data from SUN UNIX.
TYPEHPUX 13.010 Support for HP-PCS data from HPUX UNIX.
TYPEHSM 13.131 Corrections to HSM FSR segment in SMF record.
TYPEHSM 13.218 Support for HSM ABARS ABACKUP/ARECOVER FSR segment.
TYPEHSM 13.259 HSM ABARS record now validated.
TYPEHURN 13.085 Support for Antares' HURON ObjectStar SMF record.
TYPEHURN 13.243 Zero obs in HURN49 dataset.
TYPEICE 13.026 ICEBERG subtype 5 extents and TOIOTIME wrong.
TYPEIDMS 13.223 Support for IDMS/R 12.01 Maint 9506 (INCOMPATIBLE).
TYPEIDMS 13.267 Support for IDMS 12.01 INVALID DATA FOR PMHSDATE.
TYPEILKA 13.130 Internet addresses were not converted to num-point.
TYPEIMSA 13.013 IMS DEDB and MSDB counts from fastpath type 59.
TYPELMS 12.326 Support for Memorex/Telex LMS Version 3.1 (INCOMPAT).
TYPEMON8 12.315 NO MATCHING DO/SELECT error, 'TD' record support.
TYPENAF 13.094 NAFLOGOF dataset variables incorrect.
TYPENAF 13.133 Candle's Supersession Release 147 PTF QLV1372
TYPENDM 13.070 Variable NDMDSDSN (Source DSN) added to NDMCT.
TYPENDM 13.146 Connect Direct (formerly NDM) minor corrections.
TYPENSPY 13.021 NETSPY Type N subtype 06/07 support incorrect.
TYPENSPY 13.022 Support for NETSPY Release 4.6 (compatible).
TYPENSPY 13.059 INPUT STATEMENT EXCEEDED for NETSPY type X record.
TYPENTCP 13.144 Support for NetCompress SMF records.
TYPEOMCI 13.173 INPUT STATEMENT EXCEEDED RECORD Subtype 200.4.
TYPEOPC 13.092 Support for OPC Release 3.0 (INCOMPATIBLE).
TYPEPKMN 13.145 Support for Packet/Main SMF records.
TYPEQAPM 13.051 Support for OS/400 Version 3.1.0 wrong in MXG 12.12.
TYPEQAPM 13.071 OS/400 Version 3.1, DSARM/DSTYPE reversed.
TYPERACF 13.030 Support for IBM's IRRDBU00 RACF Database Unload.
TYPERMDS 13.260 INVALID ARGUMENT TO MDY in RMDS 1.4 records.
TYPESAMS 13.080 Support for Sterling SAMS Storage Automation SMF.
TYPESAVR 13.252 New fields added, ZAP required to populate.
TYPESFTA 13.219 Support for ISOGON Soft Audit Version 4.1.
TYPESOLV 13.028 Support for Sterling SOLVE NCL CPU-time accounting.
TYPETAND 13.221 Support for TANDEM D20 MEASURE CPU, DISK and PROCESS.
TYPETAND 13.283 Support for TANDEM D20 D30 and D40 releases.
TYPETCP 13.008 Support for TCP/IP APAR PN69321-PN69322.
TYPETMDB 13.223 Support for Landmark TMON for DB2 Version 2.
TYPETMNT 13.135 PROGRAM=IEFIIC records are again deleted by TYPETMNT.
TYPETMON 12.320 Landmark Version 1.3 variables were not INPUT.
TYPETMON 13.204 TYPETMON (TMON CICS 1.3) INCOMPATIBLY CHANGED BY MXG.
TYPETMS5 13.083 Support for TMS (CA-1) Release 5.1 (compatible).
TYPETMS5 13.123 New variables from 5.1 added to final datasets.
TYPETMS5 13.308 BUFNO=220 on //TMC DD reduces 15 minute run to 4!
TYPETMVS 13.170 Support for new TMON/MVS subtypes.
TYPETSOM 13.143 TSO/MON 6.1 only, TRIVTM,NTRIVTM,LONGTM too small.
TYPETUX 13.288 Support for Landmark TMON for UNIX.
TYPETUX 13.302 Corrections and Enhancements for Landmark TMON/UNIX.
TYPEVM 13.287 Support for VM/ESA SQL/DS Remote User Account Record.
TYPEVMXA 13.126 Sterling's VM/Monitor MONWRITE records cause error.
TYPEVMXA 13.137 Support for MICS VM Data Transmission Program output.
TYPEVMXA 13.168 Correction to Change 13.126, applies to IBM too.
TYPEVMXA 13.318 Alternative VXBYUSER using VXUSELOF vice VXUSEINT.
TYPEWYLA 13.075 Support for ACS Wylbur Accounting SMF record.
TYPE102 13.009 T102S145 QWn145OB values wrong.
TYPE102 13.192 IFCID 21 or 44 INVALID SECOND ARGUMENT error message.
TYPE110 12.321 CICS Statistics CICDS and CICEODRV datasets wrong.
TYPE110 13.057 CICSLSRR variables A08BKCTD/A08BKDTD incorrect.
TYPE110 13.261 Support for SAP 5.0 INCOMPATIBLE type 110 journal.
TYPE110 13.291 CICSTRAN (MXG 13.07-13.08 only) ENDTIME/ELAPSTM bad.
TYPE110 13.292 CICS/ESA 3.3 UNEXPECTED STATISTICS with STILEN=0.
TYPE110 13.296 CICS/ESA 4.1 TRANTYPE was moved by IBM, now correct.
TYPE116 13.049 Zero observations in dataset TYPE116.
TYPE1415 13.002 DSNAME='UNKNOWN...' set incorrectly for multi-vol.
TYPE1415 13.064 Multi-UCB type 1415 SMS fields wrong.
TYPE16 13.093 Support for DFSORT Release 13 (INCOMPATIBLE).
TYPE24 13.066 Fields added by MVS/ESA 5.2
TYPE26J2 13.263 JESNR may show only four digits; IBM lied in ESA 5.2
TYPE28 13.072 Support for NPM Version 2.2 APAR OW08641.
TYPE30 13.065 Negative value for EXECTM due to IBM leapseconds.
TYPE30 13.066 Fields added by MVS/ESA 5.2
TYPE30 13.073 ABEND value may be wrong in TYPE30_5.
TYPE32 13.084 Support for APARs OW10393 and OW12856.
TYPE42 13.066 Fields added by MVS/ESA 5.2
TYPE42 13.217 Support for APAR OW14717 and OW16039 SMF type 42.
TYPE42 13.311 Support for DFSMS/MVS 1.3 VSAM RLS new subtypes.
TYPE50 13.188 Variable WRBUFUSE added to dataset TYPE50.
TYPE6 13.056 4-Digit remote support incomplete.
TYPE6 13.309 INPUT STATEMENT EXCEEDED for PSF type 6 with BINS.
TYPE64 13.312 Support for DFSMS/MVS 1.3 VSAM RLS new variables.
TYPE72GO 13.236 Delay percentages calculation was incorrect.
TYPE74 13.004 MVS/ESAs 5.1 TYPE74ST dataset had duplicate/missing.
TYPE74 13.035 Support for APAR OW04653 added to TYPE74ST dataset.
TYPE80A 12.323 Invalid SUBSTR function, STOPOVER error corrected.
TYPE80A 13.254 Support for TOPSECRET 4.4/5.0 (INCOMPATIBLE) records.
TYPE91 13.189 INVALID DATA FOR AFSTTIME in SMF type 91 fixed.
TYPE92 13.155 Support for OpenMVS File System I/O SMF type 92.
TYPE92 13.313 Support for MVS/ESA 5.2.2 Open Edition INCOMPATIBLE.
VMACEXC2 13.329 Supression of excess INVALID DEVICE messages
VMAC102 13.273 Support for DB2 4.1 IFCIDs 221, 222, and 231.
VMAC110S 13.323 CICS 2.1 and SAP journal segments intermixed fix.
VMXGDUR 13.305 Rename internal variables DATE HOUR DAY DAYM etc.
VMXGHSM 13.108 Dataset DGN corrected for multiple dump copies.
VMXGINIT 13.033 New macro variable, &MXGDEBUG is now GLOBALed.
VMXGSUM 13.152 VMXGSUM incompatible for user-written invocations.
VMXGSUM 13.276 "XMXGSUM" architecture now replaces VMXGSUM.
XMXGSUM 13.097 Final validation enhancements.
YEAR2000 13.110 MXG Position Paper on support for the Year2000.
YEAR2000 13.158 Phase one support for the Year2000.
Inverse chronological list of all Changes:
NEXTCHANGE: Version 13
==========MXG 13.13 dated Jan 20, 1996, thru Change 13.332============
Change 13.332 Support for 4-digit UCB's in DCOLLECT required only that
VMACDCOL the format for variable DCVDVNUM be changed from HEX3 to
Jan 19, 1996 HEX4.
Thanks to Astrid Fridtun, Statens datasentral, NORWAY.
Change 13.331 Although DCOLLECT should be used instead of this old MXG
ASMVTOC Assembly routine, the program has been enhanced to handle
VMXGVTOC 4-digit UCB addresses, and VMXGVTOC has been modified to
Jan 18, 1996 look for the 4-digit address at the end of the record
created by ASMVTOC.
Thanks to Astrid Fridtun, Statens datasentral, NORWAY.
Change 13.330 Although DCOLLECT should be used instead of this old MXG
ASMVVDS Assembly routine, the program has been enhanced to handle
Jan 18, 1996 4-digit UCB addresses. The TYPEVVDS program was already
written to support 4-digit addresses, so it was okay!
Thanks to Astrid Fridtun, Statens datasentral, NORWAY.
Change 13.329 ERROR VMACEXC2.2 INVALID DEVICE DATA is printed for each
VMACEXC2 DD segment with non-zero EXCPCNT that has DEVCLASS=00,
Jan 18, 1996 DEVTYPE=00, and DEVNR=00, because MXG does not know what
to do with EXCPCNT in a DD segment which has no device!
However, the message is printed for EACH DD, filling the
SAS log with these messages from an MVS 3.1.3 system. No
other site has encountered the problem, and the site is
investigating to determine what is unique there, but to
prevent filling the log, the PUT statement is now limited
to the first ten occurrences. The existing EXC2ERR1=1;
statement was changed to EXC2ERR1+1; to make it a counter
and a new line inserted between that statement and the
PUT statement reading IF EXC2ERR1 LE 10 THEN so that
the message is supressed after ten occurrences.
Thanks to Warick Smith, Sun Alliance & Royal Insurance, AUSTRALIA.
Change 13.328 Support for DOS/VSE POWER 5.2 Accounting Records. IBM
IMACDOS again changed the records INCOMPATIBLY, so you must EDIT
TYPEDOS member IMACDOS to specify OFFSET=0 and INPUT @43 RECID.
Jan 17, 1996 to process POWER 5.2 records.
-Additionally, the choice between "American" MMDDYY dates
and "European" DDMMYY dates was externalized into member
IMACDOS (previously, you had to actually change the code
in member TYPEDOS for European formats.). If you have a
member IMACDOS in your USERID.SOURCLIB, you must replace
your existing IMACDOS with IMACDOS from MXG 13.13, or
you will get a VARIABLE _MMDDYY IS UNINITIALIZED message.
Fortunately, even with that message, if your dates are in
American format, MXG 13.13 will still work correctly with
your old IMACDOS. If your dates are in European format
and you use the old IMACDOS, you will also get messages
INVALID ARGUMENT TO FUNCTION MDY and your date values
will be missing until you replace your old IMACDOS with
the IMACDOS from MXG 13.13 (and tailor it for European).
-Finally, MXG code was corrected for the Reader record and
variable FROUSRID $EBCDIC8. is now INPUT after LOCLNODE
is read in. Without this correction, an INPUT STATEMENT
EXCEEDED RECORD LENGTH error occurred if a reader record
did not contain a Network Account Number.
Thanks to ???, Alenia, ITALY.
Change 13.327 The statement %INCLUDE SOURCLIB(IMACZDAT); must be
TYPEMON8 %%INCLUDE SOURCLIB(IMACZDAT); because it is
TESTUSER inside an old-style macro definition (and TYPEMON8 was
Jan 17, 1996 inadvertently removed from TESTUSER, so I missed this!)
MXG 13.07 thru MXG 13.09 only.
Thanks to Andrew Scales, Nissan UK, ENGLAND.
Change 13.326 IDMS Severity Code, TASMSSEV no longer exists in IDMS 12,
VMACIDMS and variable TASABMSG was miscalculated. The statement
Jan 16, 1996 TASMSSEV=MOD(TASABMSG,10); was replaced with TASMSSEV=0;
and the statement TASABMSG=INT(TASABMSG/10); was deleted.
Also, variables DBKKYFMT and DBKLTYPE are now formatted
as HEX8 and DBKOWNER as $HEX2 so as to be recognized by
IDMS-literate database administrators in their tongue!
Thanks to Martin Wieland, Neckermann B.V., THE NETHERLANDS.
Change 13.325 Support for Catalog Records (Exported with IDCAMS). A
EXCTLGC1 separate dataset for each of the 13 Catalog Segments is
EXCTLGC2 created for complete decoding of all possible segments
EXCTLGC3 (and variable CATRECNR can be used to collect all of the
EXCTLGC4 segments from a specific catalog record). In addition,
EXCTLGC7 two datasets are created from specific records:
EXCTLGC8 CTLGDSN - Non-VSAM Data Set record (sequence of catalog
EXCTLGC9 segments C1/01/04/04/...). The first five
EXCTLGDS VOLSERs are kept in CTLGDSN.
EXCTLGD9 CTLGVSAM - VSAM Cluster record record (sequence of
EXCTLGE3 C3/01/C4/01/04/.../C9/01/04/04...). The
EXCTLGVS first Data VOLSER and the first Index VOLSER
EXCTLG01 are kept in CTLGVSAM.
EXCTLG02 This preliminary support code detects and deletes a few
EXCTLG03 "strange" records (always at the beginning of the Export
EXCTLG04 file), printing messages on the log. After MXG 13.13 is
EXCTLG05 built and early users have played with this new support,
EXCTLG06 I intend to examine the strange records further. I also
IMACCTLG need feedback as to intended use of the catalog records
TYPECTLG to enhance contents of the record-level datasets CTLGDSN
VMACCTLG and CTLGVSAM (and may need to add a CTLGGDG dataset!).
Jan 16, 1996 See documentation in the member on usage.
Thanks to Dale Houg, Kraft Foods, USA.
=======NEWSLETTER TWENTY-NINE Printed Changes THRU Change 13.324=======
Change 13.324 If PDBOUT=WORK was specified for READDB2, the datasets
READDB2 were written to //WORK, but then inadvertently deleted!
Jan 13, 1996 Now, they will remain in the //WORK file as requested.
Change 13.323 For CICS 2.1 and SAP, SAP journal segments (which should
VMAC110S be in a subtype=0 type 110 record) are intermixed with
Jan 13, 1996 IBM performance records in records with subtype=1, and no
one at SAP AG can tell why! (See text of Change 13.261).
This problem has only been seen with CICS 2.1 (which is
already off IBM support) at one site, and they were smart
enough to create logic to deal with that aberration and
share it with me, so I have created new member VMAC110S
by adding their workaround to the MXG 13.13 VMAC110 code.
I do not have test data records but have a hex dump of an
example bad record and have validated their logic in that
manner. If you still have CICS 2.1 and have SAP writing
data to the type 110, you should test this new member
and compare the number of observations output in all of
the CICxxxxx datasets; if they are the same, you need not
use VMAC110S, but if you have the defective records, the
normal VMAC110 will throwaway records and you will have
fewer observations output (or SAS may loop!).
To use the VMAC110S member instead of the normal VMAC110,
copy member VMAC110S into your USERID.SOURCLIB library
and rename it to VMAC110.
Thanks to Paolo Carloni, Agip petroli SPA, ITALY.
Change 13.322 Hex dumps of BETA93 release 01.06.50 records have now
VMACBETA been reviewed (See Change 13.304) and they show new time
Jan 13, 1996 values are misdocumented by the vendor. Some binary are
actually HH MM SS in PK1. fields, some HHMMSS are
SMFSTAMP8, and one SMFSTAMP8. field is reversed (date
first, time 2nd!). This change should complete support
for the new release.
Change 13.321 Duplicate LABELs were removed from members ASUM70PR,
many ZMACTMVS, and VMAC members 110, 110M, 30, 33, 42, 60, 74,
Jan 13, 1996 80A, 84, BETA, CMF, DCOL, HPAI, HPCS, LMS, MEMO, NDM,
NSPY, RRTM, SAMS, and TPX.
Thanks to Freddie Arie, Lone Star Gas, TEXAS.
Change 13.320 The SAS option CODEPASS=2 is now set only for execution
BUILDPDB under MVS, because CODEPASS is an MVS-only option, but
BUILD001 it causes an ERROR 2-12 INVALID OPTION NAME under ASCII
Jan 13, 1996 SAS. (In actuality, CODEPASS=2 is an MVS compiler option
that has no measurable effect on BUILDPDB, but if the
default CODEPASS=1 is in effect, SAS prints a note on
the log suggesting that CODEPASS=2 might reduce run time
so I specify CODEPASS=2 mostly to suppress the message,
rather than for any performance improvement.)
Change 13.319 The syntax OTHER="left bracket" $HEX2. "right bracket"
FORMATS or OTHER=("vertical bar" $HEX2. "vertical bar") cannot
Jan 12, 1996 be used on both EBCDIC and ASCII platforms. The left
and right brackets do not exist on MVS, and the vertical
bar ('4F on MVS) becomes '5D'x on ASCII, which must be
changed to '7C'x to work under ASCII. Fortunately, the
CHARCODE system option allows a pair of characters to
replace right and left brackets, so the syntax of
OTHER= ?< $HEX2. ?> can be used, as long as the
code is preceded by OPTIONS CHARCODE;, which has now
been added in the FORMATS member to allow this part of
MXG to execute transparently under either ASCII or MVS.
Thanks to Terry Poole, SAS Institute Cary, USA.
Change 13.318 Comparing the CPU times in VM/ESA MONWRITE data, PFXUTIME
VMACVMXA was significantly higher than VMDTTIME, because the data
Jan 11, 1996 for the time from end of last interval to logoff was not
captured. Initially, Ian's rework of the VXBYUSR code
was to use the USEINT data, but he is now convinced that
that data is not complete, and he has suggested to IBM to
include that CPU time (the time from logon to the first
interval) in the USELOF data. Now, however, his rework
produces more VMDTTIME from the combined USEACT & USEINT
datasets than the sum of PFXUTIME and PFXTMSYS derived
from the SYTPRP records! I have implemented Ian's design
in new macro _TESTMWX, which you can use in place of the
normal TESTMW macro, to see how the CPU times captured in
the user records (VMDTTIME) compares at your site. Please
let me know your results; this note will be updated based
on your feedback of his algorithm.
Thanks to Ian Davis, Worker's Compensation Board of Alberta, CANADA.
Change 13.317 Support for FRYE Systems LAN monitor for NETWARE.
ADOCFRYE Their monitor stores data into five DbaseIII files. This
ASUMFRYE support uses PROC DBF (a part of PROC ACCESS) to convert
GRAFFRYA DbaseIII into SAS files, and produces some very nice SAS
GRAFFRYT plots from the resultant file. This code can only be
IMACFRYE executed on a SAS ASCII platform, as the DBase files can
TRNDFRYE not be uploaded to a mainframe, and PROC DBF only exists
TYPEFRYE on ASCII systems. The member ADOCTYPE provides early
VMACFRYE documentation of the Netware data captured, and also has
Jan 11, 1996 three examples of converting DbaseIII into SAS (PROC DBF,
PROC ACCESS, and a DATA step).
Thanks to Chuck Hopf, MBNA, USA.
Change 13.316 Variables WRHITPCT, RDHITPCT, CHITPCT, CACHRATE, DASDRATE
FORMATS HITPCT and CIOPCT in datasets TYPE42SR and TYPE42DS and
VMAC42 the twelve S42AMxxx variables in TYPE42DS were not set to
Jan 11, 1996 a missing value when they could not be calculated or when
the fields did not exist, so values from a prior segment
in the same record were carried forward incorrectly. An
ELSE clause now sets these variables missing when needed.
The TYPE42DS records variable INTVCLOS indicates whether
the record is for an Interval or Close event, and I had
thought the Close record contained total counts for the
entire open; however, the Close event actually contains
only the counts between the end of the last interval and
the Close, so I have changed the INTVCLOS format values
from 0:CLOSE TO 0:FINAL INTERVAL.
Thanks to Peter Lauper, Bank of America, USA.
Change 13.315 Blue Line Software's Release 4.03 and 4.04 cause INPUT
VMAC28 STATEMENT EXCEEDED RECORD LENGTH with type 28 subtype D6x
Jan 10, 1996 D7x or D9x SMF records. Their fixes are 4030030/4030031
for 4.03 and 4040035 for 4.04. All are reported fixed in
their release 4.10, currently in beta testing. I have
added traps in MXG to recognize their short records and
prevent the ABEND.
Thanks to Kevin Batten, Roses Stores, Inc., USA.
Change 13.314 Variables MVCRTIME,MVLCTIME and MVUCTIME in EDGSVREC
VMACEDGS dataset should have been LENGTH 8 with DATETIME21.2
TYPETMS5 format, and variable DSAUTIME in dataset DSNBRECD should
Jan 10, 1996 have been LENGTH 8 with DATETIME18.; now all are!
Thanks to Freddie Arie, Lone Star Gas, TEXAS
==========MXG 13.09 dated Jan 10, 1996, thru Change 13.313============
Change 13.313 Support for MVS/ESA 5.2.2 Open Edition MVS (OMVS) adds
VMAC92 new flag variable SMF92MFG to TYPE9201 and SMF92UFG to
Jan 9, 1996 TYPE9205 to identify the mounter/unmounter of the file
system, and new subtype 6 (for File System Remount) will
now be output in TYPE9205 dataset (and variable SMF92STP
was added to identify Unmount or Remount).
Unfortunately, the new flag fields were inserted in the
subtype 1 and 5 records, incompatibly altering format.
Change 13.312 Support for DFSMS/MVS 1.3 (compatibly) added several new
VMAC64 variables for VSAM Record Level Sharing (RLS), including
Jan 9, 1996 separate counts of I/O requests satisfied from LSR, DASD,
or the CF (Coupling Facility) Cache Structure (variables
SMF64BMH,SMF64RIO, and SMF64CFH, respectively), and flag
variables to identify if RLS is in effect, if RLS is in
effect but measurement has been turned off, or if this is
an extended addressable dataset. When VSAM RLS is in use
existing Hiperbatch fields and buffer counts are zeroed,
and EXCP count variables ACCEXCPS and EXCPs count buffer
manager request rather than SSCHs.
Change 13.311 Support for DFSMS/MVS 1.3 (compatibly) added four new
EXTY42D1 subtypes for VSAM Record Level Sharing (RLS) activity,
EXTY42D2 with excellent measurement of RLS's usage of CF structure
EXTY42L1 (counts and durations and response). MXG creates eight
EXTY42L2 new datasets from these four new subtypes:
EXTY42P1 From new Subtype 15:
EXTY42P2 TYPE42S1 - Storage Class Sysplex-wide statistics
EXTY42S1 TYPE42S2 - Storage Class By-System statistics
EXTY42S2 These two datasets provide six sets of 17 variables:
IMAC42 DASD Summary (variables SMF42FCx and SMF42FIx)
VMAC42 DASD REDO (variables SMF42FDx and SMF42FJx)
Jan 9, 1996 SEQ Summary (variables SMF42FEx and SMF42FKx)
SEQ REDO (variables SMF42FFx and SMF42FLx)
SEQ READAHEAD (variables SMF42FGx and SMF42FMx)
SEQ PREFORMAT (variables SMF42FHx and SMF42FNx)
From new Subtype 16:
TYPE42D1 - Data Set Sysplex-wide statistics
TYPE42D2 - Data Set By-System statistics
These two datasets provide six sets of 17 variables:
DASD Summary (variables SMF42GCx and SMF42GIx)
DASD REDO (variables SMF42GDx and SMF42GJx)
SEQ Summary (variables SMF42GEx and SMF42GKx)
SEQ REDO (variables SMF42GFx and SMF42GLx)
SEQ READAHEAD (variables SMF42GGx and SMF42GMx)
SEQ PREFORMAT (variables SMF42GHx and SMF42GNx)
From new Subtype 17:
TYPE42L1 - Lock Structure Sysplex-wide statistics
TYPE42L2 - Lock Structure By-System statistics
These two datasets provide 9/10 variables.
From new Subtype 18:
TYPE42P1 - CF Cache Partition Sysplex-wide statistics
TYPE42P2 - CF Cache Partition By-System statistics
These two datasets provide 33/34 variables.
Change 13.310 Support for MVS/ESA 5.2.2 (compatibly) added new fields:
VMAC30 -TYPE30OM dataset has new variables SMF30OMS,SMF30OMR, and
Jan 9, 1996 SMF30OSY for message queue bytes and sync() functions for
Open Edition/MVS.
Change 13.309 INPUT STATEMENT EXCEEDED INPUT for PSF type 6 SMF record,
VMAC6 because IBM added 32 undocumented bytes to the APA
Jan 8, 1996 section. The change was made by APAR OW10067 and PTF
UW18264, but the description and location of the change
to the type 6 record was not contained in the APAR text!
(nor is the change documented in the 5.2.2 SMF manual).
Change VMAC6 to read:
SMF6PTDV $EBCDIC8. /* ... */ existing
@; existing
IF SMF6LN4 GT 84 THEN DO; insert
INPUT insert
SMF6OCNM $EBCDIC20. /*OUTPUT*COM*NAME*/ insert
+12 /*RESERVED*/ insert
@; insert
SKIP=SMFLN4-116; insert
IF SKIP GT 0 THEN INPUT +SKIP @; insert
END; insert
IF SMF6BNOF GT 0 THEN DO; existing
This error only occurs if the Multi-Bins header and
counter sections exist in the type 6 record.
Thanks to Veronique Planes, SAS Institute, FRANCE.
Change 13.308 Setting BUFNO=220 on the //TMC DD statement can make a
TYPETMS5 dramatic reduction in elapsed time. A fifteen-minute run
Jan 8, 1996 ran in under 4 minutes with increased buffers.
Thanks to Freddie Arie, Lone Star Gas, TEXAS.
Change 13.307 Some very simple HSM reports and a preliminary technical
ANALHSM note on how to measure HSM, and what's important in the
ADOCHSM HSM SMF records has been added in these members.
Jan 7, 1996
Thanks to Chuck Hopf, MBNA, USA.
Change 13.306 Cosmetic changes in MXG 13.08 only. The invoked message
VMXGSUM still had "XMXGSUM" and "13.01" hardcoded, now corrected,
Jan 7, 1996 and the output dataset label was double quotes instead of
blank if no dataset label was provided in the outcode.
Thanks to Freddie Arie, Lone Star Gas, TEXAS.
Change 13.305 Internal, temporary variables named DATE, HOUR, DAY, DAYM
VMXGDUR QTRHOUR HALFHOUR and MINUTE were created and dropped
Jan 7, 1996 inside VMXGDUR macro, which is called by VMXGSUM when
INTERVAL= is specified. If you wanted to keep one of
those variable names, the internal DROP statement
prevented you from doing so (and it was most definitely
not obvious why your VMXGSUM did not work!). Now, the
temporary variables names start with DUR to prevent the
inadvertent loss.
Thanks to Neil Ervin, Huntington Services Company, USA.
Change 13.304 Support for BETA93 Release 1.06.50 (INCOMPATIBLE) inserts
VMACBETA fields in existing records, and adds five new subtypes
Jan 7, 1996 which create five new datasets:
BETA20 - Browse or Print of List or Report
BETA21 - Browse Selection Action
BETA40 - Archive of a List
BETA41 - Reload of a List
BETA42 - Deletion of an Archive Generation Record
Existing variable names were based on the DSECT names,
but this caused the same entity (eg., pages or lines) to
have a different variable name in each of the existing
seven datasets; for consistency and ease in reporting I
have renamed some of these variables, knowing full well
that my changes may cause your existing reports to fail
with VARIABLE NOT FOUND errors, for which I apologize!
Labels were also made consistent and more descriptive.
The changes have been tested with prior release data,
but not yet with records from 1.06.50. See Change 13.322.
Change 13.303 New variable MXGVERSN is kept in TYPE70 and PDB.RMFINTRV
RMFINTRV datasets so you can tell which version of MXG created the
VMAC7072 dataset from SMF. I did not think it necessary to add
Jan 6, 1996 the 6-byte version name ('13.13 ') in each MXG dataset.
Should you need to create MXGVERSN in other datasets,
you can use this logic (as macro variable MXGVERS is a
Global macro, set at SAS initialization by VMXGINIT):
MXGVERSN=SYMGET('MXGVERS');
and then add MXGVERSN to the _K macro defined in the
IMACxxxx member for the product - See Change 10.175.
Thanks to Don Deese, Computer Management Sciences, USA.
Change 13.302 Landmark's TMON for UNIX dataset TUXCPU is now created,
EXTUXCPU all datasets have now been tested with data, and formats
VMACTUX for rates and percentages are now consistent. However,
Jan 6, 1996 there are still unfixed problems that won't be fixed at
least until their ML 3.3 release:
-Datasets TUXCONEC (connections), TUXPROG (program) and
TUXPROC (process) have occasional short records (i.e, one
or more fields and their delimiters do not exist in the
data record!), causing INPUT STATEMENT EXCEEDED LENGTH
errors. Landmark Activity 49861 still open.
-Two undefined fields are in the data record that are not
in the header in TUXNFSCL (nfsclient), TUXSOCK (sockets)
and TUXUSERI (userio), causing variables WRITBLOK,
READPART, WRITPART, READFAIL, and WRITFAIL to be trashed
in those three datasets. Ref. 47164.
-Of more concern, monitor intervals are not synchronized
and timestamp values are very suspect.
I expected one minute interval data to be written each
minute, but the one set of TUXINFO (info) records had
event timestamps starting at 17 seconds after the minute,
drifting to 55 seconds after the minute in only a few
minutes: 17,15,26,28,26,26,...26,36,37,39,44,49,55
New test data for the cpu table (TUXCPU) permits better
analysis, because both EVENTIME (log_time) and the true
HRDWTIME (BOOTTIME plus UPTIME) can be compared.
Both clock shows that interval durations are not only not
synchronized but also are quite erratic, and each record
shows a different interval depending on which clock value
you examine! Comparing durations in the same record:
from hardware clock: 59,99,151,41,60,126,146,113
from log_time clock: 60,97,116,61,60,122,142,118
Comparing the hardware timestamp with the log_time in the
same record shows that the logtime sometimes is only 1-2
seconds later than the hardware timestamp (with a 5-hour
difference between GMT in hardware and EST in local), but
other intervals have a log_time several minutes later
than the hardware time, and a few records are really bad,
with the hour-part difference only two instead of five!
This is clearly a serious problem, and Landmark is now
aware of these discrepancies in their monitor. This text
will be updated when Landmark responds.
Thanks to Dan Sidorick, SmithKline Beecham, USA.
Change 13.301 Decoding DEVCLASS and DEVTYPE in VMACUCB still tested the
VMACUCB first bit of DEVNR and set DEVICE='MSS' if on, but this
Jan 5, 1996 is incorrect now, as four-digit device numbers exist, and
MSS devices do not, so that test is now disabled!
Change 13.300 New variable HIGHRBA is now created in TYPE64 with the
ANAL4GB allocated size (in bytes) of the VSAM file (using logic
VMAC64 from GC26-4574-2 to calculate CI's per track for 3380s
Jan 5, 1996 and 3390s). Member ANAL4GB then identifies those VSAM
files that are over 80% of the IBM hard limit maximum of
4GB for VSAM files, so you can forewarn their owners!
Thanks to Chuck Hopf, MBNA, USA.
Change 13.299 H-P's MEASUREWARE (formerly HP-PCS) does not record true
IMACHPAI CPU seconds in the HPxxGLOB and HPxxAPPL datasets, but
IMACHPSU instead records only the Average CPU time per CPU Engine,
IMACHPUX and then does NOT record how many Engines there are, so
VMACHPAI so you get correct total CPU time from the data records.
VMACHPSU While I regard this as an ERROR, HP considered it only an
VMACHPUX enhancement request! The NRCPUS field is in the CONFIG
Jan 6, 1996 records, but unfortunatly the HP Extract program is hard-
Jan 18, 1996 coded to put the CONFIG records at the end of its output
file. HP was persuaded to provide a workaround Script
that was to sort the Extract output and interleave the
CONFIG records to appear first (and simultaneously, that
interleave would have supported dynamic changes in the
number of engines, if "VARY CPU OFFLINE" ever becomes a
UNIX option!), so MXG logic was reordered to look for the
CONFIG records first, and retain NRCPUS into the needed
datasets. Unfortunately, the first Script did not work
as expected, so HP is back working on the problem as this
Newsletter goes to press. As an interim MXG workaround,
I have added a user-specified macro in IMACHPAI, IMACHPSU
and IMACHPUX which defaults to one CPU, but allows you to
tell MXG if you have more than one Engine. That logic
will be revised when HP provides a solution to the basic
problem, and this text will be revised to point to a
later change when there is a solution.
MEASUREWARE records are NOT supported in MXG 13.13; as I
stated in this text in Newsletter TWENTY-NINE, I had just
received test data as that newsletter went to print, and
now my fears are confirmed: HP made INCOMPATIBLE changes
between PCS records and MEASUREWARE records that will
require significant changes in MXG support. If you are
replacing HP-PCS with MEASUREWARE, please fax me for the
status of those changes (and identify the system, HP, AIX
or SUN, that you need supported, as each is different!).
Thanks to Thierry Van Moer, Procter & Gamble, BELGIUM.
Change 13.298 Format MGTANDS now decodes device type =38 (38:2GB) disk
FORMATS device, and variables LDEV and CTRL are now input as
VMACTAND $CHAR2. with a $OCTAL6. format, so device and control
Jan 4, 1996 unit are printed as TANDEM sysprogs expect.
This was my first use of the $OCTAL format, and Steve
Smith discovered what happens when I underspecified
the output width. Forgetting that a two-byte field
requires six print positions for its value in octal, I
initially assigned $OCTAL4 to a two-byte character
variable, but when a two-byte field containing '0056'o
(octal), or '002E'x (hex) was input, the value 0000
was printed, because SAS truncates character variables
on the right. Steve changed $CHAR2 to PIB2 and
$OCTAL4 to OCTAL4, and the correct value 0056 was
printed, because SAS truncates numeric variables on
the left! Of course, specifying the correct width of
$OCTAL6 or OCTAL6 prints 000056 and eliminates the
exposure to truncation differences!
Thanks to Steve Smith, BGS Systems, USA.
Change 13.297 Spelling corrections in labels, consistent comments after
EXVMxxx output statements, and removal of duplicate names in KEEP
VMACIDMS lists were made in members VMACAXC, VMACDB2, VMACDCOL,
Jan 2, 1996 VMAC28, VMACAIM7, EXDB2PAT, EXTY72GO, VMACTPM, JCLUXRE6.
VMACIDMS now includes IMACZDAT (needed only if TYPEIDMS
was executed standalone).
EXVMxxx members now have their "_LVMxxxx" macro names
instead of hard-coded dataset names for VM Accounting.
All of these changes were precipitated by Freddie's
excellent "MXG SOURCE CODE ANALYZER" program.
Thanks to Freddie Arie, Lone Star Gas, TEXAS.
Change 13.296 Variable TRANTYPE in dataset CICSTRAN with CICS/ESA 4.1
FORMATS was changed by IBM. Previously IBM used the fourth byte
VMAC110 of a four-byte field; now they use the first two bytes of
Dec 29, 1995 a four-byte field, so the length of TRANTYPE is increased
to two bytes, the INPUT for 4.1 records was reordered and
the MG110TT format was changed to decode both the old
one-byte value and the new one-and-two-byte values!
Thanks to ????, Banco Santander, SPAIN.
Change 13.295 Support for DFSMS/MVS 1.3 DCOLLECT records COMPATIBLY
EXDCODAI added a number of new variables to these datasets:
EXDCODCN DCOLDSET,DCOLCLUS,DCOLMIGS,DCOLBKUP,DCOLDC,DCOLSC,DCOLBC
IMACDCOL DCOLSC,DCOLVL,DCOLAG,DCOLDR,DCOLLB
VMACDCOL and two new datasets are now created:
Dec 29, 1995 DCOLCN - Cache Names (Cache Set name and 8-SES Caches)
DCOLAI - Accounting Information (audit of definitions
of data class, management class, storage class
and storage group - who/when updated, which
dsname/member)
In addition, enhancements to the existing DCOLLECT code
for the construct datasets were made. Variables with hex
flag values are now INPUT as $CHAR instead of $EBCDIC and
are formatted HEX or $HEX, new MGDCOxx formats now decode
variables, especially in DCOLMC and DCOLSG datasets, and
new multi-valued flag variables were created and decoded.
Thanks to Mike Moos, British Rail, ENGLAND, for construct changes.
Change 13.294 Variable DEVICE in TYPE64 was truncated to two bytes, if
VMAC64 TYPE64 member was executed by itself. The statement
TRNDCICS DEVICE=' '; must be changed to DEVICE=' '; to get
Dec 28, 1995 all seven positions of DEVICE type name.
Thanks to Chuck Hopf, MBNA, USA.
Change 13.293 Change 13.268 (adding USER to the SUMBY list for building
ASUMCICS PDB.CICS from CICSTRAN) was not applied to ASUMCICS nor
TRNDCICS to TRNDCICS, but now both members have been changed.
Dec 18, 1995
Thanks to Richard S. Ralston, Whirlpool, USA.
Change 13.292 IBM creates invalid CICS Statistics records with CICS 3.3
VMAC110 that cause UNEXPECTED STATISTICS RECORDS with STILEN=0,
Dec 18, 1995 which caused MXG to fill the //WORK file. While IBM is
trying to find their error, MXG has added logic to detect
the STILEN=0 condition and prevent the error.
To circumvent the error, in member VMAC110, find the
INPUT statement that inputs STILEN, STID, and STIVERS,
and after the @; that ends that INPUT statement, insert
IF STILEN=0 THEN DELETE;
which will cause MXG to stop processing that 110 record.
Thanks to David Callahan, Caterpiller Inc., USA.
Change 13.291 CICS/ESA 4.1 only, MXG 13.07-MXG 13.08 only. The CICSTRAN
VMAC110 variables ENDTIME, ELAPSTM and IRESPTM are wrong. Change
Dec 18, 1995 13.247 (GMT support) was incorrectly typed in VMAC110.
The two lines reading: ENDTIME =ENDTIME =MCTMNTAD;
must both be changed to: ENDTIME =ENDTIME +MCTMNTAD;
(Since ASUMCICS and TRNDCICS use STRTTIME rather than
ENDTIME to classify a transaction, the ENDTIME error is
noticed only if you look at a specific transaction, but
because IRESPTM is used for the response time buckets,
those data for your CICS/ESA 4.1 systems is wrong.)
ENDTIME is also wrong in dataset CICSEXCE.
Thanks to Neil Ervin, Huntington Service Company, USA.
==========MXG 13.08 dated Dec 15, 1995, thru Change 13.290============
Change 13.290 Cleanup of dead members and dead references; Freddie has
IMACNPM built a SAS program that reads my SAS programs to find
VMACZRB0 members-not-referenced, comments-misspelled, etc. This
Dec 12, 1995 sweep removed references to VMAC43PC,VMAC47PC,VMAC48PC,
and VMAC49PC in member VMACTEST (a private test program),
and deleted members IMACNPM and VMACZRB0 (both archaic
and no longer needed nor referenced)
Thanks to Freddie Arie, Lone Star Gas, TEXAS.
Change 13.289 Support for MVS Solutions's Thruput Manager SMF record
EXTYTPMF creates two data sets from the single SMF record:
EXTYTPMV TYPETPMF - Thruput Manager Job Analysis
IMACTPM TYPETPMV - Thruput Mangager Variable Fields
TYPETPM
VMACTPM
Dec 12, 1995
Thanks to Dan Kaberon, Hewitt Associates, USA.
Change 13.288 Support for Landmark's TMON for UNIX creates 34 datasets:
EXTUXBLO
EXTUXCLI MXG Data INFILE Landmark
EXTUXCON Set Name name Table name status
EXTUXCUR
EXTUXDIS TUXBLOCK TUXBLO blockdevice TESTED
EXTUXDSK TUXCLIEN TUXCLI clientdetail TESTED
EXTUXFIB TUXCONEC TUXCON connections See Note 1, below
EXTUXFIH TUXCURDI TUXCUR currentdir TESTED
EXTUXFRE TUXDISK TUXDIS disk TESTED
EXTUXINF TUXDSKPR TUXDSK diskprocess TESTED
EXTUXINT TUXFILEB TUXFIB filebalance TESTED
EXTUXLIM TUXFILEH TUXFIH filehistory TESTED
EXTUXMEM TUXFREE TUXFRE freespace TESTED
EXTUXNFS TUXINFO TUXINF info TESTED
EXTUXNFR TUXINTER TUXINT interface TESTED
EXTUXOPN TUXLIMIT TUXLIM limits TESTED
EXTUXPRD TUXMEMRY TUXMEM memorymgmt TESTED
EXTUXPRC TUXNFSCL TUXNFS nfsclient See Note 2, below
EXTUXPRO TUXNFSRV TUXNFR nfsservice TESTED
EXTUXPRF TUXOPENF TUXOPN openfiles TESTED
EXTUXPRS TUXPRODI TUXPRD processdisk TESTED
EXTUXPGM TUXPROC TUXPRC process TESTED
EXTUXPCL TUXPROCO TUXPRO processor TESTED
EXTUXQUO TUXPROFI TUXPRF processfiles TESTED
EXTUXRSP TUXPRODS TUXPRS processdisposition TESTED
EXTUXSRV TUXPROG TUXPGM program TESTED
EXTUXSOC TUXPROTO TUXPCL protocol TESTED
EXTUXSTO TUXQUOTA TUXQUO quotas no test data yet
EXTUXSYS TUXRESP TUXRSP response TESTED
EXTUXTAB TUXSOCK TUXSRV server See Note 2, below
EXTUXTRM TUXSTOR TUXSOC sockets TESTED
EXTUXUSR TUXSYSTM TUXSTO storage TESTED
EXTUXUSI TUXTABLE TUXSYS system TESTED
EXTUXWAI TUXTERM TUXTAB tables TESTED
IMACTUX TUXUSER TUXTRM terminal TESTED
TYPETUX TUXUSER TUXUSR user TESTED
VMACTUX TUXUSERI TUXUSI userio See Note 2, below
Dec 12, 1995 TUXWAITS TUXWAI waits TESTED
The Landmark EXPORT command that is used to create the
data files that are read by MXG has these known errors
December. Landmark expects to have a revised EXPORT
command module by January to correct these errors:
1) The connections table, MXG data set TUXCONEC, has some
data records with fields missing, causing an INPUT
STATEMENT EXCEEDED RECORD LENGTH error with that file.
2) The TUXNFSCL (nfsclient) TUXSOCK (server) and TUXUSERI
(userio) tables have numbers instead of names for some
fields in the header, so those data sets are not yet
completely valid until Landmark corrects their data.
Member JCLTUX gives an example of the JCL required that
will read all 34 files created by TMON for UNIX's export
command.
Change 13.287 Support for the VM/ESA SQL/DS Remote User Record in the
EXVMSQLR VM Account file. The new record INCOMPATIBLY alters the
TYPEVM VMSQLUSR record (SQLCPUTM in hundreds of hours), because
Dec 12, 1995 it the MXG logic unknowingly output the new record there!
This change recognizes the new record and outputs it into
new dataset VMSQLRMT instead.
Thanks to Norbert Korsche, OMV AG, AUSTRIA.
Change 13.286 MXG 13.06-13.07. ERROR: THE KEYWORD PARAMETER ALOC3590
ANALTAPE WAS NOT DEFINED. Two line reading ALOC3490=TAPE3490;,
Dec 12, 1995 must have the comma at the end of the line removed, and
twos line reading ALOC3490='3490 ALLOCATIONS WAITING';,
must have both the semi-colon and the comma at the end
of the line removed. Four lines needed correction.
Thanks to Jon Caldwell, U.S. Department of Veterans Affairs, USA.
Thanks to Mike Hampton, First Nationwide Bank, USA.
Change 13.285 Cosmetic documentation change. References to ANALDB2 were
ADOCDB2 changed to DIFFDB2, the "four datasets" note was changed
DIFFDB2 to "three datasets", and change 12.033 is referenced
Dec 12, 1995 instead of change 12.034.
Thanks to Nico Lenaerts, SAS BELGIUM, BELGIUM.
Change 13.284 REXX program to convert GTF trace records from DB2 into a
REXXDB2 legitimate (un-segmented) records had typographic errors.
Dec 12, 1995 -All C2K should have been C2X instead.
-The NE should have been <> instead.
-The statement I=REC must be changed to F=REC.
-The concatenation symbol '6A'x needs to be '4F'x for MVS.
That character is mis-translated between EBCDIC/ASCII by
many upload/download packages, so the actual change was
to replace F=F||G with F=(F)(G)so that the
REXX program is impervious to upload/download.
Thanks to Eric Thornton, D&B, USA.
Thanks to Chuck Hopf, MBNA, USA.
======= Attended CMG 95 Conference in Nashville, Tennessee ============
Change 13.283 Support for TANDEM D20, D30, and D40 releases is added
VMACTAND compatibly. However, I found I cannot trust the TANDEM
Dec 2, 1995 MEASURE documentation; its DLLs show changes where there
Dec 12, 1995 were none! (Fortunately, CMG came to the rescue as there
Jan 3, 1996 I met a TANDEM employee who put me in touch with the real
programmer who wrote the code!). Two variables were added
compatibly by D30 (BEGTRANS,ABRTRANS) by using reserved
space in the PROCESS record. Several measurement fields
(lock-pages-qtime/count and UCL-lock-qtime/count in the
PROCESS record, and the four pairs of START/END variables
for UDS-LOCK, SDS-LOCK,UCL- LOCK, and SCL-LOCK in the
DISC record) were made reserved fields in D40 (because
they were too expensive to capture!). The DDL for D40 are
wrong, as they show BEGTRANS/ABRTRANS in the wrong place,
and the now-reserved fields were deleted from the DDL,
but they were not deleted from the physical record.
Thanks to Joe Fleischmann, US Bancorp, USA.
Thanks to Todd Tomita, US Bancorp, USA.
Thanks to Steve Smith, BGS Systems, USA.
Change 13.282 MAINTLEV 7 of the MXG Tape Mount and Allocation Monitor
ASMTAPES corrects the JSCB access problem, the CA-11 restart case,
Nov 30, 1995 and supresses the SRB dump messages (unless we ask you to
enable DEBUGGING!). This iteration has been running in
two sites for several weeks with no failure. The previous
monitor code was copied into ZSMTAPES for backup.
Change 13.281 This replacement for member CICINTRV is temporarily put
CICINTRZ in this member for extensive testing, but it will become
Nov 30, 1995 CICINTRV in the near future. The present CICINTRV logic
is incorrect, and this new logic correctly creates the
CICS interval datasets from the statistics datasets.
This version first summarizes the individual datasets at
the lowest level, and performs deaccumulation with DIF()
function for the REQ and USS records so that all four
types of CICS stat records are correctly summarized into
the CICINTRV dataset. Note that this can be resource
intensive if you have lots of CICS activity, but you can
construct the CICS activity from these statistics records
even if you have turned off CICSTRAN creation!
Revised Jun 13, 1996: Resources are not a problem; see
resource measurements in text of Change 14.132, which
implemented these enhancements starting with MXG 14.04.
Thanks to Chuck Hopf, MBNA, USA.
Change 13.280 Correction. If no summary dataset was created, but
ANALCNCR summary reports were requested, the summary reports were
Nov 30, 1995 not produced.
Change 13.279 New parameters SMFBEGIN and SMFEND were added to allow
READDB2 selection while the raw SMF records are read. These new
Nov 30, 1995 parameters are now used by ANALDB2R (Change 13.278).
Change 13.278 Several enhancements to DB2 reporting.
ANALDB2R -Reports can now be produced from MNTHxxxx datasets, if
Nov 30, 1995 you have used the MNTHxxxx members to trend monthly.
-When reading SMF, the BEGTIME and ENDTIME values are now
passed to READDB2 (as SMFBEGIN/SMFEND) so that selection
applies to the raw data as it is read, which will reduce
DASD space and run time, especially with big traces.
Change 13.277 This utility (used only in JCLTEST6, to select ten SMF
VMXGGETM records of each type) has new INCODE= operand added to
Nov 30, 1995 enhance selection criteria, for those of you who have
found this utility useful! You could now code
INCODE=IF (ID=30 AND 4 LE SUBTYPE LE 5) OR ID=72; ,
to select only those records and subtypes.
Thanks to Chuck Hopf, MBNA, USA.
Change 13.276 The revised VMXGSUM logic has been moved from XMXGSUM to
VMXGSUM VMXGSUM, and member XMXGSUM has been deleted. (Just in
XMXGSUM case, the old VMXGSUM was copied into ZMXGSUM for backup,
ZMXGSUM but that member too will go away in time). The new logic
Nov 30, 1995 in VMXGSUM will significantly reduce the DASD space, CPU
time and run time, as it keeps only the variables that
are actually needed by the summarization, and (unlike the
old VMXGSUM), it does not create dummy variables in
the output dataset. It also supports variable lists with
hyphenated syntax. Many sites with large data volumes
have been using the XMXGSUM logic, so I believe it is now
safe to make the MXG default to be the new logic.
Change 13.275 New parameters INTERVAL and MYTIME are defined for report
ANALRMFR summarization, but they are only implemented in MXGCHAN
Nov 30, 1995 report at this time.
Change 13.274 CICS shutdown reports CICCONSR or CICCONMR can cause many
ANALCISH blank pages with only the heading and no content; several
Nov 30, 1995 line changes were required, too complicated to show here.
Also, END; statement was missing after IF INOBS EQ CXMC.
Thanks to Rick Ralston, Whirlpool. USA.
Change 13.273 Support for DB2 4.1 type 102 trace records has tested the
VMAC102 new IFCIDs 221, 222, and 231 for parallel group tracing,
Nov 30, 1995 and adds new fields in existing trace datasets for IFCIDs
8, 10, 20, 21, 22, and 28. There are still other fields
added to other IFCIDs by 4.1 that are not yet decoded by
MXG due to absence of test data records; those will be
added when user demand and test data arrive together.
Thanks to Ted Blank, IBM, USA.
Change 13.272 Corrections to several variables in HP PCS records:
VMACHPAI -VMACHPUX, comment now has HPUX as correct INFILE name.
VMACHPSU -VMACHPUX, PIN variable removed from LENGTH statement so
VMACHPUX that it will be numeric rather than character (as it was
Nov 29, 1995 in HPAI and HPSU members, like all other PINs).
-INTEREST now input as INTEREST $CHAR12. (instead of with
no INFORMAT) as the file may contain leading blanks.
First test for INTEREST that sets IMPWTHI was deleted.
Last four tests for INTEREST must test for lower case
letters c,d,m,i rather than upper case values.
Thanks to Thierry Van Moer, Procter & Gamble Europe, Belgium.
Change 13.271 Variables SYSNAME and SYSPLEX were not kept in BUILDPDB
IMACPDB datasets PDB.JOBS, PDB.STEPS, and PDB.PRINT, but they are
Nov 29, 1995 now added to _PDB30_1, _PDB30_4, and _PDB30_5 macros in
member IMACPDB so they will be kept in the PDB datasets.
Thanks to Dr. Alexander Raeder, Karstadt AG, GERMANY.
Thanks to Hartmut Beckmann, Karstadt, AG, Germany
Change 13.270 IBM writes truncated EREP records, but MXG did not catch
VMACEREP the truncation, causing INPUT STATEMENT EXCEEDED RECORD
Nov 29, 1995 for a hardware detected VLF software record. Protection
was added for dataset EREPSDW. Additionally, the ERRORID
field at the end of the SDW record was not input from the
correct location, and variable CLASRC is now kept in the
EREPSDW, EREPEOD, EREPMDR, and EREPOBL datasets.
Thanks to Solomon Baker, The Prudential Service Company, USA.
Change 13.269 Variables QBSTHPL and QBSTVPL were removed from DIF()'ing
DIFFDB2 because they are not accumulated values, but rather are
Nov 28, 1995 the number of hiperspace and virtual pool buffers.
Thanks to Alan Fendler, Pershing Info Management Services, USA.
Change 13.268 Variable USER was added to the default summarization of
ASUMCICS CICSTRAN dataset into PDB.CICS, because OPERATOR is now
Nov 28, 1995 usually blank, while USER contains the wanted user-id.
Dec 18, 1995 The summarization default is now by
APPLID OPERATOR USER TERMINAL TRANSACT (for each hour).
Thanks to Clark Jennings, Reynolds Metal, USA.
Change 13.267 Another IDMS 12.01 error, INVALID DATA FOR PMHSDATE for
VMACIDMS the PMHRTYPE=6 (Journal Wait) subtype. The statement
Nov 20, 1995 SKIP=SKIP-108; that is two lines prior to the statement
%%INCLUDE SOURCLIB(EXIDMJRL); should been
SKIP=SKIP-104;. (My test data stream did not have any
journal wait data, but this was an MXG coding error.)
Thanks to Dan Gilbert, Bergen Brunswig Corporation, USA.
Change 13.266 Variable STARTIME was missing TSOMCMND if the TSO/MON
VMACTSOM SMF record was written in segments (because there were
Nov 20, 1995 more logged on users that would fit in one SMF record).
STARTIME was added by Change 13.089 for consistency, but
the pre-existing, same value variable STRTTIME was never
wrong! Immediately following STRTTIME=TSOMSTAR; insert
STARTIME=STRTTIME;
Thanks to Neil Ervin, Huntington Services Co, USA.
Change 13.265 Support for IMS 5.1 records (INCOMPATIBLE) was reported
ASMIMSLG with these changes.
VMACIMS -ASMIMSLG - Replace these three non-contiguous lines
Nov 17, 1995 TM MSGCFLG1,MSGC1RAC TM MSGCFLG1,MSG3RACF
---17 lines ----
USING MSGRACF,R4 USING MSGSEC,R4
--- 8 lines ----
MVC ORGENT(8),MSGRACGP MVC ORGENT(8),MSGSAFNM
(with this change to ASMIMSLG, it can ONLY process 5.1
records, so you will need to maintain two separate load
libraries and separate job streams).
VMACIMS
18 new 4-byte fields were inserted in the 07 log record
between MSGGCMD and PDATE.
This is a documentation only change at this time, as I am
still awaiting data and documentation so that I can
validate this report and then change the MXG coding.
Now, see Change 14.030.
Thanks to Mr. Hellmann, Sudwestdeutsch Landesbank, GERMANY.
Change 13.264 TANDEM disk type format MGTANDS values are decimal, not
VMACTAND hex, so the "X"'s were removed, and the 35:3GB value has
Nov 16, 1995 replaced the 35:MGB spelling.
Thanks to Steve Smith, BGS Systems, USA.
Change 13.263 IBM lied, and JESNR may show only four digits in TYPE26J2
VMAC26J2 dataset (and if BUILDPDB finds only a purge record for a
Nov 13, 1995 job, its PDB.JOBS observation will have JESNR=1179 where
Feb 26, 1996 it should be JESNR=11179. IBM documentation of SMF26JNM
(the old, 4-position EBCDIC JESNR) says it will be zero
if the job number is 10,000 or greater, causing MXG to
get JESNR from SMF26JID, and this was true until now, but
it appears MVS/ESA 5.2 with JES x.y are now putting the
truncated JESNR back into SMF26JNM! While I chase after
the IBM INCOMPATIBLE change to type 26 record, I can fix
the MXG logic to work no matter what IBM does. Change:
ELSE DO;
IF JESNR GT 0 THEN
INPUT @57+OFFSMF TYPETASK $EBCDIC3.
+5
@;
ELSE
INPUT @57+OFFSMF TYPETASK $EBCDIC3.
@60+OFFSMF JESNR &NUM.5.
to read:
ELSE DO;
INPUT @57+OFFSMF TYPETASK $EBCDIC3.
@60+OFFSMF JESNR &NUM.5.
Feb 26, 1996 update: IBM APAR OW18822 acknowledges the
error and should correct the non-zero value back to zero,
but the MXG correction in MXG 13.13 fixes it anyhow!
Thanks to Tim Terbieten, Newell Company, USA.
Change 13.262 Variable DEVPLX, the device address of the duplex volume,
VMACACHE is an offset from the first device instead of the real
Nov 8, 1995 device number; now, DEVPLX will contain the true device
Dec 2, 1995 number by inserting these lines:
IF NDVCNT=1 THEN BASDEVN=DEVN;
IF DEVS1='....1...'B THEN DEVPLX=BASDEVN+MOD(DEVS2,64);
before the %%INCLUDE SOURCLIB(EXCAC90); statement.
I note that the Cache record does not contain a segment
for the duplex device; DEVPLX=05x, BASDEVN=2C0x, so the
duplex device address is now DEVPLX=2C5x, but there will
be no observation in CACHE90 with DEVN=2C5x.
The above correction worked until MVS/ESA 5.2, which has
caused an unexpected (at least by the CRR-folks) change
in the CRR record. The BASE device number used to be the
first device segment returned by the 3990 controller, and
that address is copied into the statistics segment. But
in 5.2, the order in which devices are varied online at
IPL is different, and the 3990 returns devices in order
they came online, so the base device is no longer going
to be in the first segment. IBM CRR Level II has this;
when they decide what they are going to do, so will I!
Thanks to Kurt Koch, West Publishing Corporation, USA.
Change 13.261 SAP Journal segments in type 110 records caused error
VMAC110 INPUT STATEMENT EXCEEDED, or INVALID DATA FOR HH, or did
Nov 8, 1995 not read in all segments in the SMF record, because MXG
Jan 13, 1996 did not anticipate that SAP would create journal segments
with only a header,
(found for the YISA APPC host-to-host connection
application, with JCSPTRAN='YISA', JCRLL=30, so there
is no data - these segments may be output into a new
dataset if there is usefulness, and this fix still
leaves them available in the EXCICJRN exit),
or with JCRUTRID not containing 'SA',
(found for a most strange segment between other 'SA's,
containing a Global Performance Interval segment with
MCTSSDID=2 which belongs in a subtype =1 record and
is normally output into CICSYSTM from that subtype!;
UPDATED Jan 13. SAP Technical Support has not responded,
but the second problem is circumvented in Change 13.323.
Header only segments are skipped over with these changes:
-Delete the line ... INPUT +6 SAPTEST $EBCDIC2 @LOC @;
-Change IF SUBTYPE=0 OR SAPTEST='SA' THEN DO UNTIL ...
to IF SUBTYPE=0 THEN DO UNTIL ...
-Change IF JCRUTRID='SA' THEN DO;
to IF JCRUTRID='SA' AND JCRLL GE 250 THEN DO;
Unrelated to the above errors, variable APPLID was added
to the KEEP= list for the CICSSAP dataset so CICSSAP can
be analyzed for each CICS region.
Thanks to Jens Schlatter, EDP Consulting Schlatter, GERMANY.
Thanks to Norbert Korsche, OMV, AUSTRIA.
Thanks to Paolo Carloni, Agip petroli SPA, ITALY.
Thanks to ????, Deutsche Post AG, GERMANY.
Change 13.260 RMDS 1.4 records may cause INVALID ARGUMENT TO MDY AT ...
VMACRMDS because only some MDY() functions were protected for the
Nov 8, 1995 'strange' values MO=99 and DD=99.
Feb 26, 1996 -Now, all uses of MDY() are protected with logic of the
form:
IF YY GT 0 AND (YY NE 99 AND MO NE 99 AND DD NE 99)
THEN xxxxDATE=MDY(MO,DD,YY);
-In addition, INVALID DATA FOR MM can occur, because only
some INPUTs of HH MM and SS were protected with the ??
modifier. Now, all fields input with &NUM are preceded
by the double-question-mark modifier.
-Finally, all HMS() functions are now protected with
IF 0 LE HH LE 24 and 0 LE MM LE 60 and 0 LE SS LE 60
logic to prevent invalid arguments to HMS() function.
-The error does not occur with current RMDS 2.1 or later.
Note added Feb 26, 1996: The support for RMDS 1.3/1.4
also deleted the two tests:
IF RMDSACT='D' and RMDSORG NE 'A' THEN RMDSACT='T';
IF RMDSACT='U' AND RMDSORG EQ 'V' THEN RMDSACT='S';
because the activity codes of 'T' and 'S' do not exist
in RMDS version 2.1.
Thanks to Ambat Ravi Nair, Trident Infotech Pte Ltd, SINGAPORE.
Change 13.259 MXG 13.06-13.07 only. ABARS enhancement validation:
EXHSMWWV -UNEXPECTED IDHMSMDS RECORD FOUND because the line now
IMACHSM reading ELSE IF DSRVSR='VRS' THEN ... should have been
VMACHSM ELSE IF DSRVSR='VSR' THEN ....
Nov 8, 1995 -INPUT STATEMENT EXCEEDED RECORD LENGTH on ABARS subtype
Nov 15, 1995 because the four fields WFSRML0U,WFSRML1U,WFSRML2U, and
WFSRTOTU at the end of both ABARS segments are now INPUT
as $EBCDIC1. instead of &PIB.4. MXG now decodes the unit
of space value (blank, K, M, etc.) and converts the space
used during ABACKUP variables WFSRML0S,L1S,L2S,TOTS into
bytes, and are formatted with MGBYTES to print pretty.
-Variable WFSRABCC is now input as $EBCDIC4. vice &PIB.4.
-IBM clarified several issues. Space units of K,M,G,T are
1024 (as expected, but since IBM used 1000 for hardware
"K", and since the ABARs documentation did not say, we
had to ask!). Also, ABACKUP VERIFY does cut a shorter
record that does not contain the space information fields
while ARECOVER creates a longer record, but zeroes out
the space information fields.
-New HSM dataset HSMWWVOL is created, but with zero obs
until you remove the comment block in member EXHSMWWV.
(This dataset will contain one obs for each volser that
was used by ABARS for backup, and I perceive little need
for that information; the useful ABARS information is in
the HSMWWFSR dataset, one obs per ABARS event.)
Thanks to Michael E. Friske, Fidelity Savings, USA.
Change 13.258 Very obscure, and only for the early users of XMXGSUM.
XMXGSUM Change the second occurrence of NUMPOS= from &HYPHEN1 to
Nov 6, 1995 &HYPHEN2. Would have caused an OUT OF MEMORY error.
Change 13.257 Variable AVGQUETM should not have been in the keep list
VMAC7072 for dataset TYPE72GO, as that field is from the subtype 2
Nov 6, 1995 (RMF Monitor III) record, and is output only in TYPE72MN.
Thanks to Don Deese, Computer Management Sciences, USA.
Change 13.256 Variable QBGAGN should be kept only in DB2ACCTG, and not
VMACDB2 in DB2ACCT, and it should not have been summed during the
Nov 6, 1995 creation of DB2ACCTG. It is the pool ID, not a counter!
Thanks to Chuck Hopf, MBNA, USA.
Change 13.255 Tandem variables CnMISSES was repeated in INPUT; the two
FORMATS instances are now named CnRMISS and CnWMISS for Read or
VMACTAND Write misses. C1BLKS is no longer divided by DURATM, as
Nov 6, 1995 it is blocks allocated, not blocks moved in interval.
Format MGTANDS was updated with device 1Fx and will now
print un-coded values in hex rather than decimal.
Thanks to Steve Smith, BGS Systems, USA.
Change 13.254 Support for TOPSECRET Release 4.4 and 5.0, INCOMPATIBLE,
VMAC80 CAUSES INPUT STATEMENT EXCEEDED RECORD error, because the
VMAC80A new release sets a value of 44X or 50X for RACFVRSN, but
Oct 31, 1995 MXG does not know in advance what value TOPSECRET will
use! Add OR RACFVRSN=44X OR RACFVRSN=50X to the test
for TOPSECRET in both members. (44X exists in 4.4 data;
5.0 is not out yet, so I am gambling in advance that they
will use 50X for that version when it's released!).
Thanks to Mark Paulson, Maurices Incorporated, USA.
Thanks to Sarah Gartner, Hudson's Bay Company, CANADA.
==========MXG Version 13.07, dated Oct 30, 1995, thru 13.253==========
Change 13.253 SAP 5.0.E creates invalid journal segments, which caused
VMAC110 INVALID DATA FOR HH and a hex dump of the record, but MXG
Oct 27, 1995 successfully skipped over the invalid segments and output
the valid ones. SAP had no one in tech support on Friday
to discuss their error before MXG 13.07 was built, but I
will pursue this with them later and update this note.
To eliminate the hex dump and message, insert ?? after
HH and MM following the INPUT of JCSPTASK.
Update: See Change 13.323.
Thanks to Paolo Carloni, Agip petroli SPA, ITALY.
Change 13.252 $AVERS SMF record variables SAVPAGES,SAVBLKS,SAVTBLKS are
VMACSAVR now created; these fields existed at the end of the SMF
Oct 27, 1995 record, but were not populated until this user went to
use them! The vendor, Software Engineering of America,
will fix the error in SAVRS V4.0A.33, and interim fix
number S40AF166 (a ZAP) is available from them now that
will populate these fields.
Thanks to Bill Hamilton, Scottish Widows, SCOTLAND.
Change 13.251 Support for STK's SILO SMF HSC View Subtype 8 record now
EXSTCHSV creates dataset STCHSV for every successful VIEW command
IMACSTC initiated by HSC.
VMACSTC
Oct 26, 1995
Thanks to Cheryl Howard, Wachovia Corporation, USA.
Thanks to Rodney L. Reisch, Wachovia Corporation, USA.
Change 13.250 DURATM was added to TSO/MON datasets by Change 13.089,
VMACTSOM but it was often missing! After the second statement
Oct 26, 1995 INTRVTM=TSOMDUR; insert DURATM=INTRVTM;
Thanks to Dan Squillace, SAS Institute Cary, USA.
Change 13.249 Support for MODEL204 Release 3.0 INCOMPATIBLY added five
IMACM204 fields to the SINCE record. Since there is no release
VMACM204 number in their record, you MUST update member IMACM204
Oct 25, 1995 in your USERID.SOURCLIB to use this new IMACM204, as it
now also defines macro _M204VER which tells MXG to read
Release 2 or Release 3 records (default is for Rel 3).
Thanks to Mark Wessel, Population Census & Surveys Office, ENGLAND.
Change 13.248 Summarization of IDMSTAS dataset from IDMS/R Perfmon into
ASUMIDMS PDB.ASUMIDS is provided by this user contribution, which
Oct 25, 1995 mimic's ASUMCICS algorithms to create response time and
resources by CV_NUM DC_USER DC_LTERM TASKCODE ADSODLGN.
Thanks to Richard S. Ralston, Whirlpool, USA.
Change 13.247 CICS/ESA 4.1 or later now contains the GMT offset, so MXG
VMAC110 can finally convert the STRTTIME/ENDTIME in CICSTRAN to
Oct 25, 1995 your local time of day. The INPUT of MCTMNTAD is changed
from &PIB.4. to &IB.4., and this line inserted:
MCTMNTAD=1.0485582324*MCTMNTAD;
to convert from CICS timer units to seconds. Then, in
the CICS/ESA 4.1 section for CICSTRAN and CICSEXCE, the
logic IF MCTMNTAD GT . THEN DO;
STRTTIME=STRTTIME+MCTMNTAD;
ENDTIME =ENDTIME +MCTMNTAD; END;
was inserted to add the (negative in USA) GMT offset.
NOTE: IF YOU HAVE TAILORED member EXCICTRN to convert the
CICSTRAN timestamps (as was described in Newsletter 27),
YOU MUST REMOVE OR REVISE YOUR conversion logic so that
it only converts non-4.1 records. For example, you could
use this logic for USA East Cost time zone in EXCICTRN:
IF MCTMNTAD=. THEN MCTMNTAD=.;
IF MCTMNTAD=. THEN DO;
STRTTIME=STRTTIME-HMS(5,0,0);
ENDTIME =ENDTIME -HMS(5,0,0);
END;
to force the 5-hour conversion for non-4.1 regions. The
first statement setting MCTMNTAD missing if it is missing
if the "compiler faker" statement which eliminates the
"uninitialized variable" message, so you could install
this logic in EXCICTRN even before you install MXG 13.07!
Variable MCTMNTAD was added to CICSTRAN by this change.
Thanks to Glenn Yee, Health & Welfare State of California, USA.
Change 13.246 Variable SETUP was added to _PDB26J2 macro so that that
IMACPDB variable will be kept in the PDB.JOBS dataset. It turns
Oct 25, 1995 out that the existence of a /*SETUP card causes JES2 to
put the job in logical hold until the operator releases
the job, but TYPRUN=HOLD is not set for these jobs. Now,
for observations with SETUP='Y' in PDB.JOBS, you can
identify these jobs that are delayed due to /*SETUP card.
Thanks to Andy Vick, Allied Dunbar Assurance, ENGLAND.
Change 13.245 In revision 4 of the type 6 SMF record, IBM truncated two
VMAC6 bytes of SMF6TU field, but in revision 5 data, the value
Oct 25, 1995 in SMF6TUL matches the length of SMF6TU, so the line that
was added by Change 13.162 is now changed to read:
IF REVISION EQ 04X THEN SMF6TUL=SMF6TUL-2;
I have not found IBM documentation of their change yet!
Thanks to Michael Moyer, Wyeth-Ayerst Labs, USA.
Change 13.244 Support for DB2 4.1.0 (COMPATIBLE) adds new fields to the
ANALDB2P statistics and accounting records, new subtypes and new
EXDB2ACG segments create three new datasets:
EXDB2PAT
EXDB2PST DB2ACCTG - Accounting - Group Buffer Pool usage
VMACDB2 DB2GBPAT - Global Buffer Pool Attributes
VMACDB2H DB2GBPST - Global Buffer Pool Interval Statistics
Oct 22, 1995
The major change is the support for DB2 Parallelism, with
multiple observations now created in DB2ACCT whenever
DB2 event (like a QUERY) is actually parallelized. The
degree of parallelism for a CPU bound task is constrained
by the number of CPU engines, while it is the structure
of your DB2 data (number of partitions, etc.) which
limits the degree of parallelism for an I/O bound task.
New member ASUMDB2P can be used to summarize these child
and parent pairs (and the sequential, or non-parallelized
DB2 events) so that there is only one observation for
each event, with variables PAIRNR (a created sequence
number token that was used to create ASUMDB2P from
DB2PARTY), NRCHILD (number of children records for this
event), and TOTELAPS (sum of elapsed time of all records
for this event, because ELAPSTM is the true elapsed wall
time of the parallel execution). Beware, sorting DB2ACCT
is required to create both the DB2PARTY detail dataset
and the output ASUMDB2P dataset, and DB2ACCT can be big!
The parent record has a non-zero QXMAXDEG, the maximum
number of parallel tasks, but there can be many more than
QXMAXDEG children records written, because tasks can be
parallelized in groups of different degrees. MXG creates
formatted variable DB2TSKTY to describe each observation
in DB2ACCT:
DB2TSKTY Description
C Child
P Parent
S Sequential (i.e., non-parallelized)
Complex queries in test data shows an event of three
groups, with 9, 10, and 8 children respectively, so 28
observations in DB2ACCT were created for that
parallelized query event. Almost all of the resources
(CPU, I/O) are recorded in the child record, but the
parent record contains important counts as well.
Extensive testing of DB2ACCT data was done in creation of
member ANALDB2P for parallel analysis, but the test data
thus far has not used Global Buffer Pools, so those new
datasets have not been data-tested. I have only casually
validated the DB2STATS with 4.1 data for reasonableness,
and VMAC102 has not yet been enhanced (I still await 4.1
trace test data). This note will be revised as testing
proceeds.
Change 13.243 MXG did not output observations to HURN49 if HU49XSNO is
VMACHURN zero (user logs on to Huron server, but did not access
Oct 20, 1995 another database before logging out). After the END;
after the DO I=1 TO HU49XSNO; insert:
IF HU49XSNO=0 THEN DO; %%INCLUDE SOURCLIB(EXHRN49); END;
Thanks to Colin Bowen, Old Mutual, SOUTH AFRICA.
Change 13.242 Correcting TYPE42DS STARTIME/ENDTIME from GMT to local in
VMAC42DS exit EXTY42DS using STARTIME=STARTIME-HMS(5,0,0) (to
EXTY42DS subtract 5 hours, for EST or CDT time zone) will not work
Oct 19, 1995 because the EXTY42DS member will be invoked once for each
dataset in a concatenation, causing STARTIME to be fine
in the 1st dataset, but then off by 5 hours in the 2nd,
off by 10 hours in the 3rd, etc. Instead, you must use
STARTIME=SMF42PTS-HMS(5,0,0); and
ENDTIME= SMF42PTE-HMS(5,0,0);
to force the correct GMT value. When you have installed
MXG 13.07 or later, you can revise your exit logic to use
IF S42JDGMO=. THEN DO;
STARTIME=SMF42PTS-HMS(5,0,0);
ENDTIME= SMF42PTE-HMS(5,0,0);
END:
because MXG 13.07 adds support for APAR OW16125 that adds
the actual GMT offset in S42JDGMO; with this revised code
your forcing code will only be executed prior to install
of that APAR. This is a documentation-only change; no
MXG code was actually changed.
Thanks to Diane Eppestine, Southwestern Bell, USA.
Change 13.241 New BUILDPDB exit IMACSPCK allows you to override the MXG
IMACSPCK decision "TO SPIN OR NOT TO SPIN" for specific cases.
BUILDPDB For example, VM Print Jobs, run on MVS, will create only
BUILDPD3 a type 6 print record. If you have tailored IMACSPIN so
BUILD000 that SPINCNT is greater than zero (as recommended), those
Oct 19, 1995 VM jobs will spin for SPINCNT days before finally being
output into the PDB. If you know that all VM Print jobs
have job names starting with RSCS, you can use this new
IMACSPCK member, by coding therein:
IF JOB=:'RSCS' THEN OKFLAG=1;
which will sent all RSCS jobs directly to the PDB instead
of waiting around in the SPIN library for SPINCNT days!
The default exit contains only comments.
Thanks to Norbert Korsche, OMV, AUSTRIA.
Change 13.240 Dataset ASUMDB2B was not created in the weekly PDB from
WEEKBLD the daily PDB's, but now it is.
WEEKBLDT
Oct 17, 1995
Thanks to Merlin Beeching, Generale de Banque SA, BELGIUM.
Change 13.239 S370FRBn informat fails under ASCII SAS if the floating
SASAFIX1 point value is unnormalized. See MXG Technical Note in
Oct 15, 1995 Newsletter TWENTY-NINE for discussion. This member is an
Nov 8, 1995 interim fix for MXG users executing under ASCII platforms
and currently contains two SAS programs that will create
the UWIS370F.DLL file for OS/2 SAS 6.10 or 6.11.
-Nov 8. The OCT 15 fix returned a large negative value if
the field was all hex zero, but that is now corrected,
and SASAFIX1 now provides fixes for SAS for OS/2 for both
6.10 and 6.11 and for SAS for Windows for 6.10.
Thanks to Ian Gibson, Queensland Transport, AUSTRALIA.
Change 13.238 MXG 13.06 only. Variable DELTATM is always missing. The
DIFFHMF semicolon is missing from each of the 6 LABEL statements,
Oct 14, 1995 also causing UNINITIALIZED warning message.
Change 13.237 Variable ZDATE is now created in one place, IMACZDAT, so
IMACZDAT that you can easily force ZDATE to a specific date for a
Many rerun of a build job. Previously, you had to change the
Oct 14, 1995 value of ZDATE in a separate place for each infile that
you had to rerun. All of the associated statements to
describe ZDATE (LENGTH, LABEL, FORMAT) were moved into
the IMACZDAT member, and each statement ZDATE=TODAY();
or IF ZDATE=. THEN DO; do group were replaced with the
%INCLUDE or %%INCLUDE syntax for member IMACZDAT. There
were 113 members changed in response to this suggestion,
which will surly make someone very happy some day!
Thanks to Bruce Hewson, Alcoa, AUSTRALIA.
Change 13.236 The execution delay percentage variables in TYPE72GO used
VMAC7072 the workload manager sample count (VALDSAMP=R723MTVN;) as
Oct 14, 1995 denominator, but that statement is now replaced with:
VALDSAMP=PCTUSCUS+PCTDLTOT+PCTDLUNK;
because the workload manager counts both address spaces
and dispatchable units in the numerator (eg., an ASID may
have an SRB executing and a TCB waiting). This discovery
by Don was non-trivial and has been IBM-confirmed!
Thanks to Don Deese, Computer Management Sciences, USA.
Change 13.235 Utility UDOCHECK (rarely needed, used to scan SAS source
UDOCHECK statements to locate DO ... END pairs when you have one
Oct 13, 1995 of those painful "MISSING END STATEMENT" syntax errors,
often caused in my experience because a comment swallowed
the END; statement) did not support DO WHILE / DO UNTILs.
Thanks to Wayne Bell, National General Insurance Company, USA.
Change 13.234 Variable NLDMSUBT should have been added to TYPE39_8 but
VMAC39 it wasn't until now.
Oct 13, 1995
Thanks to Wayne Bell, National General Insurance Company, USA.
Change 13.233 MXG 13.06. Support for Landmark for DB2 V 2 has now been
VMACTMDB tested with data which found undocumented alignment bytes
Oct 27, 1995 and changed header, causing STOPOVER. In addition, many
variables were not formatted that are now.
Thanks to Ken Updegraff, Hershey Chocolate, USA.
Change 13.232 The values of LPMINCnn, LPTARCnn, and LPMAXCnn variables
VMACAPAF are 10000 times too small. Change their informat from
Oct 17, 1995 &PIB.4.6 to &PIB.4.2 to correct. Additionally, variables
LPMINPnn, LPTARPnn, and LPMAXPnn are now created with the
Percentage allocation for each logical processor.
Thanks to John Suters, Telecom Australia, AUSTRALIA.
Change 13.231 The calculation of ARSPNET was sometimes incorrect. The
VMACNSPY statement IF NETRSPNO GE .5*TRANSNO AND TRANSNO GT 0
Oct 12, 1995 THEN ARSPNET=CRSPNET/TRANSNO;
should be ... THEN ARSPNET=CRSPNET/NETRSPNO;
Thanks to Alan Keebel, British Steel, ENGLAND.
Change 13.230 MXG 13.06 only. Change 13.181 caused INPUT STATEMENT
VMAC64 EXCEEDED RECORD error. The five lines at the end:
Oct 11, 1995 INPUT BEGCCHHX PIB4.
ENDCCHHX PIB4.
+18
@;
ALLOCCYL=ALOCCYL+ENDCCHHX-BEGCCHHX+65536;
must be replaced by this single corrected line:
ALLOCCYL=ALOCCYL+ENDCCHH-BEGCCHH+65536;
Thanks to Freddie Arie, Lone Star Gas, TEXAS.
Change 13.229 Change 12.195 was never made to WEEKBLDT, causing SORT
WEEKBLDT ORDER error. The correct _BYLIST for TAPEMNTS is:
Oct 11, 1995 MACRO _BYLIST SYSTEM SHIFT DEVICE TMNTTYPE TMNTTIME % .
Thanks to Neil Ervin, Huntington Services Company, USA.
Change 13.228 MVS/ESA V5 in Goal Mode only. Pre-Goal Mode, MXG only
EXTY72GO output TYPE72 when the PERFGRP had activity (to save DASD
FORMATS space, because IBM created segments for idle perfgroups),
VMAC7072 and so in Goal Mode, MXG only output TYPE72GO when the
Oct 10, 1995 SRVCLASS consumed resources (by testing, in EXTY72GO, for
non-zero CPUUNIT,SRBUNIT,IOUNIT,MSOUNIT or TRANS).
However, that test should only have been applied against
service classes for address spaces (as only ASIDs contain
resources). The result was that observations for trans
service classes that had no completions during the
interval were not output.
The test should have been qualified by R723TYPE, as it
describes which type of record we have. However, then I
discovered that R723TYPE was missing in some MVS/ESA 5.2
data, because the resource flag, R723CRCA, was not set,
and that had previously been a legitimate identifier that
an observation was an address space. As a result of this
discovery, I had to redefine the way R723TYPE is created:
IF RPRTCLAS EQ 'Y' THEN DO;
IF R723CRCA EQ 'Y' THEN R723TYPE='4';/*REPORT, ASID */
ELSE R723TYPE='5';/*REPORT, TRAN */
END;
ELSE IF R723CWMN GT 0 THEN R723TYPE='3';/*TRANSACTION*/
ELSE DO;
IF R723CRTX GT 0 THEN R723TYPE='1';/*ASID SC WITH RESP*/
ELSE R723TYPE='2';/*ASID SC NO RESP*/
END;
-Now, with the correct definition and setting R723TYPE
values, the logic in EXTY72GO could be changed so that
only observations that could contain resources are tested
to see if they should be output, using:
IF R723TYPE IN(1,2,4) THEN DO;
IF SUM(CPUUNITS,SRBUNITS,IOUNITS,MSOUNITS,TRAN)
GT 0 THEN OUTPUT _LTY72GO ;
END:
ELSE OUTPUT _LTY72GO;
With these changes, R723TYPE will be valid for all obs,
and only those resource-containing observations written
for Address Space Service Classes or Report Classes will
be output by the exit.
-Also discovered, the format names in member FORMATS for
$MGRMFTY and $MGRMFRT were reversed. $MGRMFTY describes
the type of record, while $MGRMFRT describes responses.
Thanks to Don Deese, Computer Management Sciences, USA.
Change 13.227 The VAX Accounting Support was designed for execution on
VAXPDS ASCII platforms, which caused errors when executed under
Oct 10, 1995 MVS. The RECFM=N for ASCII must be RECFM=VB for MVS, so
I now have added a macro %%VMXGLRF in place of RECFM=N on
each INFILE statement, and defined VMXGLRF to set the
correct RECFM depending on where MXG is being executed.
Also, the broken vertical bar character ('6A'x onMVS)
used for concatenation was replaced with the exclamation
points ('5A'x on MVS), because the '6A'x character is not
correctly translated between ASCII and MVS systems.
Thanks to Frank d'Hoine, Nationale Bank van Belgie, BELGIUM
Change 13.226 Support for APAR OW16125 which adds GMT offset to type 42
VMAC42 subtype 6 (TYPE42DS dataset) observations. If the APAR
Oct 10, 1995 has been installed, new variable S42JDGMO will be non
missing, and MXG will have converted STARTIME and ENDTIME
from GMT to local time of day. If S42JDGMO is still
missing, the APAR is not installed, and STARTIME/ENDTIME
will still be on the GMT clock.
==========MXG Version 13.06, dated Oct 10, 1995, thru 13.225==========
Change 13.225 Change 13.065 can cause variables INTBTIME,INTETIME to
VMAC30 be really far from the truth, because the line inserted:
Oct 9, 1995 by that change:
GMTOFF30=GMTOFF30+SMF30IST-INTBTIME; /*GET LEAP SEC*/
must be deleted. In attempting to correct IBM's error, I
made the problem worse, by adding that heuristic that
worked with my test data, but failed badly with different
data. Removal of this line may still cause the problems
that were discussed in 13.065, but it is the safest
approach for "normal" sites.
Thanks to Don Deese, Computer Management Sciences, USA.
Change 13.224 Support for Landmark TMON for DB2 Version 2 INCOMPATIBLY
EXTMDxxx changed their records, so MACRO _TMDVER is now defined in
IMACTMDB member IMACTMDB to tell MXG to process version 2 records.
VMACTMDB (The default in IMACTMDB expects Version 1 data records,
Oct 8, 1995 so you MUST tailor IMACTMDB to process Version 2.
The previous support created only TMDBDA,TMDBDB,TMDBDE,
and TMDBDR datasets. For version 2, datasets TMDBDA2,
TMDBDB2, and TMDBDE2 will have observations while their
un-suffixed counterparts will only have observations with
version 2, and TMDBDR no longer exists with version 2.
These new version 2 data sets are now created and will
have observations if their subtypes are found:
TMDBDBA, TMDBDAB, TMDBDAF, TMDBDBB, TMDBDDF, TMDBDBK
TMDBDBR, TMDBDW , TMDBDC.
In addition, these new datasets are defined and will have
observations, but only the record header is decoded for
these subtypes at this time:
TMDBBB , TMDBBC , TMDBBD , TMDBBE , TMDBBF , TMDBBG
TMDBBH , TMDBBI , TMDBBJ , TMDBBK , TMDBBL , TMDBBM
TMDBBT , TMDBDD
This combined support for both versions has not been
tested with data records, but the original code and the
Version 2 code contributed by Peter were separately
tested before I restructured and merged the code into
the single VMACTMDB member, and no error have surfaced.
Thanks to Peter Proppe, Bremer Lagerhaus Gesellschaft(BLG), GERMANY.
Thanks to Ken Updegraff, Jr., Hershey Chocolate, USA.
Change 13.223 Support for IDMS 12.01 Maintenance Level 9506 and later.
VMACIDMS CA INCOMPATIBLY changed their PERFMON SMF record. MXG
Oct 8, 1995 should have detected their change and deleted the changed
Nov 14, 1995 record and print a NOTE on the log, but their change
exposed an MXG logic error in detecting IDMS changes, and
MXG ABENDed with INPUT STATEMENT EXCEEDED RECORD LENGTH.
(In my defense, even CA IDMS Tech Support did not know
THAT there was a change, nor WHAT fields were changed
until I read this text to them!) Originally I thought
the change was introduced in IDMS 12.01, but it is their
maintenance level 9506 that contains the new data fields.
-Delete the final IF SKIP GT 0 THEN INPUT +SKIP (the one
after the END; /* END SUBTYPE 18 */ statement). This
will eliminate the STOPOVER condition with 12.01 data,
However, datasets IDMSARA, IDMSBUF, IDMSDBK and IDMSJRL
will still be wrong because field lengths were changed.
-To process ONLY 12.01 data, you could make these changes:
After PMHRTYPE=1, change INPUTs of
ARANAME $EBCDIC16. to ARANAME $EBCDIC27.
ARAFILE $EBCDIC16. to ARAFILE $EBCDIC27.
ARABUFR $EBCDIC16. to ARABUFR $EBCDIC18.
INPUT ARAFPERA &PIB.2. /* #FILES FOR AREA*/
and change SKIP=SKIP-184 to SKIP=SKIP-208;
After PMHRTYPE=2, change INPUTs of
BUFNAME $EBCDIC16. to BUFNAME $EBCDIC18.
and change SKIP=SKIP-120 to SKIP=SKIP-122;
After PMHRTYPE=6, change INPUTs of
JRLNAME $EBCDIC16. to JRLNAME $EBCDIC27.
and change SKIP=SKIP-120 to SKIP=SKIP-131;
After PMHRTYPE=18, change INPUTs of
DBKAREA $EBCDIC16. to DBKAREA $EBCDIC27.
DBKFILE $EBCDIC16. to DBKAREA $EBCDIC27.
and change SKIP=SKIP-120 to SKIP=SKIP-142;
-The actual change processes 12.01 and earlier data.
Thanks to Don Snively, E-Systems, USA.
Change 13.222 Support for COM-PLETE Version 4.6 has no change in their
VMACCOMP record format, but two errors in MXG were uncovered: if
Oct 7, 1995 you use the single SMF ID for your COM-PLETE record, MXG
failed to output the COMPULOF and COMPUCKP datasets. The
line with _IDCOMOF should test ULOGRTYP=3 (was 1), the
line with _IDCOMCK should test ULOGRTYP=2 (was also 1).
These two changes are required for either 4.5 or 4.6, but
only if you use a single SMF record type in the _IDCOMP
macro definition in IMACCOMP.
Thanks to Wayne Bell, National General Insurance, USA.
Change 13.221 Support for Tandem MEASURE processes their Process, CPU,
ADOCTAND and Disk data files. See member ADOCTAND for discussion
EXTANCPU of how to create, process, and use the three datasets:
EXTANDIS TANDCPU - Interval CPU activity statistics
EXTANPRO TANDDISK - Interval DISK activity statistics
IMACTAND TANDPROC - Interval PROCESS activity statistics
TYPETAND The Tandem data files contain ASCII character data with
VMACTAND standard mainframe binary values; this support has been
Oct 6, 1995 executed both under MVS and under OS/2 (and I discovered
Dec 2, 1995 that the FB data records must have RECFM=F on the INFILE
statement under ASCII versions of SAS, but must have
RECFM=FB under EBCDIC versions, necessitating creation of
the VMXGLRF macro to provide transparent support).
NOTE: MXG will process the "native" ASCII TANDEM data on
an ASCII platform (UNIX, OS/2, WINDOWS) as is. However,
if you want to process the TANDEM data on with an EBCDIC
platform (MVS, CMS, VSE), you must NOT translate the
TANDEM data from ASCII to EBCDIC - send the TANDEM data
to MVS as a BINARY file with no conversion and NOCRLF.
If your character variables are filled with @@@@@, you
are reading data that was converted from ASCII to EBCDIC,
and it is not just characters that are corrupted!
Thanks to Barry Pieper, Norwest, USA.
Change 13.220 Length of MXGCHAN variable CHTYPE increased to $4, and
ANALRMFR ELSE clauses removed, and a RETAIN statement deleted in
Oct 3, 1995 report enhancements.
Change 13.219 ISOGON Soft Audit Version 4.1 compatibly changed record
VMACSFTA format from FB to VB format (for better maintenance in
Oct 3, 1995 future versions), and added several new variables to
both the Program and the Module datasets, including the
Accounting Fields from the JOB card in the Program data.
Change 13.218 Support for the ABARS ABACKUP/ARECOVER FSR segment in the
EXHSMWWF HSM user SMF record creates new dataset HSMWWFSR with new
IMACHSM statistics (counts, timestamps/durations, space used).
VMACHSM The new segment is now put in the DFSMShsm smfid record
Oct 2, 1995 (which previously contained only the DSR and VSR
segments), but DFSMS 1.3 or APAR OW11391 will relocate
the new segment to the smfid+1 record (which contains
FSRs). MXG is coded to create it from either of the two
HSM records. The HSMWWFSR dataset is an event record,
written at the end of ABACKUP or ARECOVER, and thus there
should be no accumulated fields across SMF records, so
there is no reference to HSMWWFSR in member DIFFHSM.
Thanks to Michael E. Friske, Fidelity Savings, USA.
Change 13.217 APAR OW14717 for SMF type 42 subtype 2 INCOMPATIBLY
VMAC42 changes the value of SMF42CSS,SMF42SSA,SMF42SAP,SMF42SSU,
Oct 2, 1995 SMF42NSZ, and SMF42SPR (cache controller and non-volatile
storage sizes), but OW14717 should not be installed, as
IBM is replacing it with a better solution. A new APAR
number OW16039 will be issued to fix the same problem but
i