COPYRIGHT (C) 1984-2007 MERRILL CONSULTANTS DALLAS TEXAS USA
CHANGE 14.14
=========================member=CHANGE14================================
/* COPYRIGHT (C) 1984-1997 MERRILL CONSULTANTS DALLAS TEXAS USA */
This is MXG Version 14.14 is dated Feb 21, 1997, thru Change 14.352.
Newsletter THIRTY-ONE was dated Feb 21, 1997, thru Change 14.343
2nd MXG Version 14.11 was dated Feb 4, 1997, thru Change 14.324
1st MXG Version 14.11 was dated Feb 3, 1997, thru Change 14.323
MXG Version 14.10 was dated Jan 10, 1997, thru Change 14.299
MXG Version 14.09 was dated Dec 17, 1996, thru Change 14.295
MXG Version 14.08A was dated Nov 18, 1996, thru Change 14.275
MXG Version 14.08 was dated Nov 13, 1996, thru Change 14.271
MXG Version 14.07 was dated Sep 11, 1996, thru Change 14.221
Newsletter THIRTY was dated Sep 10, 1996, thru Change 14.209
early MXG Version 14.07 was dated Sep 10, 1996, thru Change 14.209
MXG Version 14.06 was dated Aug 20, 1996, thru Change 14.191
MXG Version 14.05 was dated Jul 15, 1996, thru Change 14.160
MXG Version 14.04 was dated Jun 13, 1996, thru Change 14.132
MXG Version 14.03 was dated May 27, 1996, thru Change 14.114
MXG Version 14.02 was dated Apr 25, 1996, thru Change 14.096
MXG Version 14.01 was dated Mar 7, 1996, thru Change 14.051
MXG Version 13.13 was dated Jan 20, 1996, thru Change 13.332
Newsletter TWENTY-NINE, dtd Jan 20, 1995, thru Change 13.323
Contents of member CHANGES:
0. Table of contents of NEWSLETTER THIRTY-ONE (see member NEWSLTRS).
I. MXG Software Version 14.14 Status.
1. Announcing email, WWW.MXG.COM home page, and MXG-L LISTSERV.
2. MXG Software Version 14.14, dated Feb 21, 1997, was shipped.
3. What products are not yet supported?
II.-X. Technical Notes are in Newsletter THIRTY-ONE.
IX. Incompatibilities and Installation of MXG 14.14.
X. Online Documentation of MXG Software.
XI. Changes Log
0. Table of contents of NEWSLETTER THIRTY-ONE:
MXG NEWSLETTER NUMBER THIRTY-ONE February 21, 1997
Technical Newsletter for Users of MXG : Merrill's Expanded Guide to CPE
TABLE OF CONTENTS Page
I. MXG Software Version 14.14 was shipped with this newsletter. 2
1. Announcing email, our www.MXG.com home page and the MXG-L LISTSERV 2
2. MXG Software Version 14.14, dated Feb 21, 1997, was shipped. 2
II. MXG Technical Notes 7
1. MXGTMNT's Tape Allocation Monitor logic at MAINTLEV 9. 7
2. If MONTHBLD fails due to NOTSORTED error due to skipped version. 7
III. MVS Technical Notes. 7
1. APAR OW15356 now writes type 21 SMF records 7
2. APAR OW10686 corrects errors in counting I/Os in type 30 records 7
3. MVS/XA type 30 subtype 2, 3, & 4 with hex zeros for JOB. 7
4. Increased Logical Swaps becoming Physical Swaps with Goal Mode. 7
5. Type 74 subtype 5 Cache record (TYPE74CA) has duplicates. 7
6. APAR OW23225 EXCP counts zero in TYPE30 for VSAM RLS datasets. 8
7. Boole & Babbage CMF 5.2 creates type 72 with STARTIME 1 sec off. 8
8. APAR OW23872 for 3590 Model A00 Control Unit serial number wrong. 8
9. APAR OW23814 documents errors in DCOLLECT type A DCAFLAG1. 8
10. Media Manager EXCP counting for DB2 VSAM in 30 and 72s. 8
11. TCP/IP SMF records with invalid data for FTPCLIENT. 8
12. Type 6 CA-DISPATCH non-matching READTIME values. 8
13. Slow TSO Logon duration due to massive STEPLIBs. 8
14. Type 42 records were enhanced by APAR OW20866 (DCME enhancements). 9
IV. DB2 Technical Notes. 9
1. Where have all the DB2 buffer pools data gone? 9
2. Number of observations in DB2ACCT no longer counts plans. 10
V. IMS Technical Notes. 10
1. Boole & Babbage IMF had negative values for RESPTM 10
2. Boole & Babbage IMF caused 10% increase in CPU time in MVS 5.2.2. 10
VI. SAS Technical Notes. 10
1. SAS USER ABEND 318 with SAS 6.08 at TS425 with 4-digit UCB. 10
2. SAS note 8243: SAS data libs cannot be hdw compress or striped. 10
3. IBM APAR OW14045 causes SYNCSORT to ABEND with 0C4 under SAS. 10
4. SAS Usage Note 5637 (from 1992) - how to ftp V VB VBS files. 10
5. If you use the FILE command from a Display Manager Session. 11
6. Algorithm to count the number of bits that are on in a bit flag. 11
VII. CICS Technical Notes. 11
1. APAR PN70228 has extensive discussion of Short on Storage. 11
VIII.Windows NT Technical Notes. 11
1. MXG Support for Windows NT with Demand Technology's NTSMF-WHY? 11
2. So what is NTSMF and what measures do you get from NT registry? 12
IX. Incompatibilities and Installation of MXG 14.14. 20
X. Online Documentation of MXG Software. 21
XI. Changes Log 23
Alphabetical list of important changes 23
Changes 14.343 thru 14.210 26-48
COPYRIGHT (C) 1997 MERRILL CONSULTANTS DALLAS TEXAS USA
I. MXG Software Version Status.
1. Announcing email, our WWW.MXG.COM home page, and the MXG-L LISTSERV.
My new email address is BARRY@MXG.COM (replacing mxg@e-mail.com), an
administrative matters can be sent to ADMIN@MXG.COM, or can be faxed
I have, to some extent, embraced email, especially for receiving SMF
data and for sending new members to beta sites for new support tests
and I do try to check my email once a day. I still find that fax is
often faster (I check it much more frequently as it is beside the
coffee pot!) but for hex dumps, the virtues of email over fax are
both its legibility, and its machine readability for searching.
If it is really critical, email the information, fax a reminder for
me to logon, and call me to remind me to look at the fax machine!
I still prefer to answer technical questions by phone whenever I can
Our home page has been operational since November 1996, and it has
the up-to-date status of the current MXG version. (MXG 14.14 is the
15th release since MXG 13.13, the last annual version). On the home
page you will find these members from the current version: CHANGES
(status of what MXG version you need for what), YEAR2000 (status of
other vendor's fixes), CHANGESS (all changes to all MXG versions),
and NEWSLTRS (text of all MXG newsletters). While the Annual Softwar
Version and Newsletter shipment sent in First Quarter, and the Summe
Newsletter sent in Third Quarter are still the primary MXG formal
communications, more current information is always on the home page.
Instructions on how to subscribe to the MXG-L LISTSERV, an e-mailing
list, are also on our home page. When you subscribe, any e-mail
sent to MXG-L will be rebroadcast to all subscribers. All MXG-L
notes are viewable in the MXG-L Archive, and you do not need to be
a subscriber to view the archive. MXG-L is intended as a forum for
technical questions among MXG users. It is not moderated, but is
monitored. It also provides me with an easy way to let you know
there is something worthwhile that has changed; for example, I email
to the MXG-L list when there is a new MXG version available.
2. MXG Software Version 14.14, dated Feb 21, 1997, was shipped to your
site with this Newsletter.
Major enhancements added in MXG 14.14 dated Feb 21, 1997:
MXG is now distributed as an unnumbered dataset.
MXG now converts DB2 GMT times to Local (Check you Exit Tailoring)
Support for OS/390 Version 1 Release 3 (Compatible)
Support for APAF Version 3.
Support for NPM APAR OW17875 type 28 new subtype 2Ax.
Support for Landmark's The Monitor for CICS/ESA 1.5 (easy - no change
New ASUMUOW to combine CICSTRAN and DB2ACCT by unit of work.
PROCSRCE member is "Proc Source" for ASCII SAS.
DB2GBPST dataset is now deaccumulated and usable.
Major enhancements added in MXG 14.11 dated Feb 3, 1997:
NTSMF support for 3.51, more data sets verified, record protects.
Support for new Type 42 subtype 19 and changed subtypes 15-18.
MXG Tape Mount and Tape Allocation Monitor ML11 in ASMTAPES
Coupling Facility Structure Data TYPE74ST enhancements.
DB2 GMT times now converted to local - see INCOMPATIBILTY SECTION.
MXGSAS JCL Procedure finally corrected!
Major enhancements added in MXG 14.10 dated Jan 10, 1997:
Windows NT support using NTSMF significantly enhanced and documented.
See "Windows NT Technical Notes" or member ADOCNTSM.
Major enhancements added in MXG 14.09 dated Dec 17, 1996:
Support for Demand Technology's NTSMF "SMF for Windows NT" product.
Support for Demand Technology's Stress Test product's SMF record.
Support for IBM VTAM Session Management Exit's SMF record
Major enhancements added in MXG 14.08A dated Nov 18, 1996:
Correction to VMAC74 INVALID DATA message for R744FCTM,FCSQ.
Major enhancements added in MXG 14.08 dated Nov 13, 1996:
Support for OS/400,AS/400 Release 3.7.0 and Release 3.6.0.
Support for CA's ENDEAVOR SMF record.
Support for APAR OW22209,OW25262 bytes read/written.
Support for HP's Measureware for AIX.
Support for Applied Software's SUPER IND$FILE SMF.
Support for Oracle Release 7.2.3 SMF record.
Support for RACF 2.1 IRRDBU00 unload utility.
Petabytes now formatted. (1024 Terabytes=1 Petabyte).
The TAILORNG= JCL parameter causes JCL error.
Support for RMF type 74 subtype 100 IRLM long locks.
Support for Interlink's Harbor 4.1 SMF record
Support for RSD's EOS SMF record (INCOMPATIBLE, not in 14.07).
Support for Boole and Babbage's PRO/SMS SMF Recovery Record.
Major enhancements added in MXG 14.07 dated Sep 11, 1996:
Support for Desktalk's TRENDSNMP IFENTRY SNMP data.
Support for Candle's Omegamon for SMS V150 (no change!).
CICS 4.1+ incorrect MCTMNTAD GMT offset circumvented.
CICINTRV variable A02TTS missing in CICEODRV
BUILDPDB now asserts SORTEDBY= for PDB.JOBS/STEPS/PRINT/SMFINTRV
Beta Test of MXG DASD Allocation Monitor in ASMDALO/TYPEDALO.
New utility UTILCONT (Contents of SAS library, sizes in Megabytes).
Major enhancements in early MXG 14.07 shown in MXG Newsletter THIRTY:
Support for CICS/ESA 5.1.0 aka Transaction Server (INCOMPATIBLE)
Support for TMON/DB2 Version 3 (INCOMPATIBLE).
Support for Boole and Babbage's PRO/SMS SMF Message Record.
Major enhancements added in MXG 14.06 dated Aug 20, 1996:
Support for CONTROL-T from New Dimension Software.
Support for Omegamon/VTAM V200 (INCOMPATIBLE).
Support for MODEL204 Release 3.2.1 (INCOMPATIBLE).
Support for SoftAudit Version 5.1 (INCOMPATIBLE).
Support for APAR OW15406 for RMF adds support for Year 2000.
Support for Tandem Controller and Line records added.
Sample code to read Network General's Sniffer Network Monitor data.
VM Print sent to JES2 is now merged in PDB.JOBS.
BUILDPD3 now sums JES3 type 25 MDS Tape Mounts/Fetches.
More RACF Reports for Command Events decoded by TYPE80A.
DB2 4.1 DB2STATS interval lost due to QWHSISEQ skipped values.
CICINTRV restored to pre-14.04 version, fixed for CICS 4.1.
Redesigned TRNDTALO to "SPIN" active allocations.
SMF Simulator (ANALSMF) now tests a CISIZE of 18432 for 3390s.
Major enhancements added in MXG 14.05 dated Jul 15, 1996:
Support for OS/390 Version 1 Release 2 (COMPATIBLE).
MXG 13.13 and later tolerate OS/390 Release 2, but to capture
the several new variables and new subtypes of type 74 and 89,
you must install MXG 14.05 or later.
Support for SMF type 89 subtype 2 (Measured Usage Product Summary).
Support for DB2 trace data written to GTF instead of SMF.
Support for HP MeasureWare for HP-UX platform
Support for RDS's EOS Enterprise Output Solution
Support for Landmark TMON/MVS spanned records.
Support for RMF type 74 subtype 5 Cache RMF Reporter.
Support for Anacomp, Inc's XSTAR product's SMF record
Support for DFSORT Release 13 APAR PN71337.
New JCLADHOC example of MXG ad hoc job to select specific data.
Revised MXGSAS JCL procedure adds TAILORNG= symbolic parameter.
New DB2 trace datasets to hold all SQL text are created.
MXG JCL examples now specify REGION=0M
VMXGTAPE utility macro to determine if lib/dsn is on tape.
UDEBLOCK utility to create valid RECFM=U on MVS from PC data.
ASMIMSLG/ASMIMSL5 SLOTS table was moved above the 16MB line.
Major enhancements added in MXG 14.04 dated Jun 15, 1996:
Support for ASTEX 2.1 (INCOMPATIBLE)
Support for NDM 1.4 (compatible) new variables
Support for IMS APAR PN76410 (INCOMPATIBLE) for ASMIMSLG processing.
Support for APAR PN78083 to SMF type 42 (ADSM) required no change.
Enhanced CICINTRV was installed as default (but removed in 14.06).
Major enhancements added in MXG 14.03 dated May 27, 1996:
Support for RACF 1.10 (compatible) - toleration of new records.
Support for NETSPY Release 4.7.
Support (partial) for AS/400,OS/400 Release 3.6 (INCOMPATIBLE).
Support for Thruput Manager #V041238 (INCOMPATIBLE).
All datetime constants '01JAN00:...' were changed to '01JAN1900:....'
Corrections to errors that were only in MXG 14.02:
DIFFDB2 14.108 BY VARIABLES ARE NOT PROPERLY SORTED DB2STATR
TYPE37 14.107 INPUT STATEMENT EXCEEDED ID=37
TYPE72 14.102 INPUT STATEMENT EXCEEDED ID=72
TYPENSPY 14.097 Zero obs in NSPYLU.
Major enhancements added in MXG 14.02 dated April 25, 1996:
ASMTAPES MAINTLEV 9, monitor no longer quits writing, TMNT013I msg.
Support for IBM's Cache RMF Reporter CRR Version 1.7.
Support for Netview FTP (File Transfer) SMF subtype 51x record.
Support for second length STK HSC Subtype 08 record.
Support for Shared Page Groups statistics in TYPE71.
Support for STK's NearOAM user SMF record.
Support for IBM's RMDS Version 2.2 (no change).
Support for NPM APARs OW08565/OW10584 for 3746/900.
Major enhancements added in MXG 14.01 dated March 7, 1996:
Support for OS/390 Release 1.1.0 (already in MXG 13.13).
Support for FACOM MSPE/EX PTF 93061 ID=127 SMF record.
Support for SMF type 6's ESS segment added and externalized.
MAINTLEV 8 of the MXG Tape Mount and Tape Allocation Monitor
INPUT EXCEEDED for NETSPY 4.6, type A record.
INPUT EXCEEDED for STK HSC subtype 8 record corrected.
INPUT EXCEEDED for DB2 4.1 type 101 subtype 2 (packages).
INPUT EXCEEDED for DFSMS/rmm type "O" record.
INPUT EXCEEDED for EREP type '40'X record.
INPUT EXCEEDED for PSF 6 SMF, PSF wrote truncated record.
INPUT EXCEEDED for VSAM 64 SMF, CF Cache Structure segment.
NOTSORTED error for PDB.CICS in WEEKBLD, WEEKBLDT, and MONTHBLD.
ASMVTOC failed to assemble.
INVALID DATA FOR HH,MM,SS with SAMS SMF record.
VARIABLE SYSTEM uninitialized in ASMIMSLG processing.
Hipercache SMF record values for VSAM segment wrong.
NDM/Connect Direct timestamps missing, data wrong.
TLMS dates were not decoded correctly.
NPM dataset NPMVSVVR variables were trashed.
All of these enhancements are described in the Change Log, below.
Availability dates for the IBM products and MXG version required:
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
OS/390 1.1.0 Feb 22, 1996 14.01
OS/390 1.2.0 Sep 30 1996 14.05
OS/390 1.3.0 Mar 28 1997 14.14
CICS/ESA 3.2 Jun 28, 1991. 9.9
CICS/ESA 3.3 Mar 28, 1992. 10.01
CICS/ESA 4.1 Oct 27, 1994. 13.09
CICS/ESA 5.1 Sep 10, 1996 14.07
CRR 1.6 Jun 24, 1994. 12.02
CRR 1.7 Apr 25, 1996. 14.02
DB2 2.3.0 Oct 28, 1991. 10.01
DB2 3.1.0 Dec 17, 1993. 13.02A
DB2 4.1.0 Tolerate Nov 7, 1995 13.07
DB2 4.1.0 Full support Nov 7, 1995 14.07
DB2 5.1.0 ??? ??, 1997 ??.??
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
MQM 1.2, 1.3, 1.4 Apr 25, 1996. 14.02
NETVIEW 3.1 type 37 ??? ??, 1996. 14.03
NPM 2.0 Dec 17, 1993. 12.03
NPM 2.2 Aug 29, 1994. 12.05
NPM 2.3, 2.4 ??? ??, 1996. 14.03
RMDS 2.1, 2.2 Dec 12, 1995. 12.12
TCP/IP 3.1 Jun 12, 1995. 12.12
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
IMS 4.1 Jul 4, 1994 12.02
IMS 5.1 Jun 9, 1996 14.05
Availability dates for non-IBM products and MXG version required:
Availability MXG Version
Product Name Date or Change Required
Demand Technology
NTSMF Version 1 Beta 14.11
Landmark
The Monitor for DB2 Version 3 14.07
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
The Monitor for MVS/ESA 1.5 - 12.05
The Monitor for MVS/ESA 2.0 - 15.??
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 IMS V300 (ITRF) 14.04
Omegamon for MVS V300 13.170 13.05
Omegamon for MVS V400 13.201 13.06
Omegamon for DB2 Version 2.1/2.2 13.05
Omegamon for VTAM V160 12.04A
Omegamon for SMS V100/V110 12.03
CA
ASTEX 2.1 14.04
Boole & Babbage
IMF 3.1 (for IMS 5.1) 12.12
Memorex/Telex
LMS 3.1 12.12A
3. What products are not yet supported?
a. Support for Landmark's Performance Works for Unix, a replacement
for their earlier The Monitor for Unix (that was supported by MXG
TYPETUX) is in development (although Landmark still has not been
able to provide documentaion, users have!) and may be partially
complete in the actual MXG 14.14 version.
b. Landmark's The Monitor for CICS/ESA Version 2 will be relased this
spring, but the documentation and test data had not yet arrived.
c. Enhancements to ASMRMFV (work on ASMTAPES ML 12 pre-empted) are
now hoped for second quarter.
4. What's planned for the near future?
a. Documentation revision. MXG 14.14 has support for just about ever
new product's version that anyone has asked for, so finally I can
return to updating the ACHAP and ADOC documentation members!
IX. Incompatibilities and Installation of MXG 14.14.
1. Incompatibilities introduced in MXG 14.14 (since MXG 13.13):
a- IMACs that were changed (if they exist in your USERID.SOURCLIB, you
must refit your tailoring, starting with the new IMAC member):
IMACCIMS - For Boole & Babbage IMF - See Change 14.152.
b- Other incompatibility changes:
- Dataset TYPE116 (MQM) variable QWHCATYP replaced by QWHCXTYP.
- With OS/390 R2, IBM CRR product (dataset CACHE90 from VMACACHE)
becomes dataset TYPE74CA from VMAC74. See TYPE74CA in MVS Tech
Notes.
- MXG now converts DB2 time stamps (like QWACBSC,QWACESC,QWHSSTCK)
from GMT to local, but if you did that already in EXDB2ACC for
DB2ACCT, you must remove your conversion code and let MXG do it.
c- These products were incompatibly changed by their vendor, and they
require MXG 14.xx as indicated:
See products listed as INCOMPATIBLE in Section I, Enhancements.
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.V1414.MXG.SOURCLIB, and use IEBUPDTE
to read the MXG tape to create the 2955+ member Source Library.
c. Allocate a 1-cyl PDS: MXG.V1414.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 V1414.USERID.SOURCLIB.
d. Allocate a 1-cyl SAS Data Library: MXG.V1414.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.V1414.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.V1414.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.V1414.USERID.SOURCLIB, then you must reinstall your site's
tailoring for that IMAC, starting with the IMAC member from the
MXG 14.14 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 14.14 in its own set of libraries. When
parallel testing is complete and are ready to implement MXG 14.14
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.V1414.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.
X. 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.
XI. 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 between MXG 13.13 and MXG 14.14:
Dataset/
Member Change Description
many 14.019 Support for OS/390 Release 1.0 already in MXG 13.13!
many 14.158 Support for OS/390 Release 2.0 tolerate by MXG 13.13!
many 14.318 Support for OS/390 Release 3 (Compatible).
many 14.320 MXG is now distributed as a unnumbered dataset.
ANALCNCR 14.162 FILE WORK.SPLIT DOES NOT EXIST corrected.
ANALCNCR 14.175 Specifying both output dataset and reports failed.
ANALDB2R 14.022 DB2 report PMAUD03, if PDB is on tape, will fail.
ANALDB2R 14.073 VARIABLE QWHSIID NOT FOUND corrected in DB2 reports.
ANALDB2R 14.286 DB2 Buffer statistics, Acct Detail, missed BP 1 & 2.
ANALDSET 14.064 Using Tape instead of DASD for ANALDSET fails.
ANALDB2R 14.340 DB2 4.1 Reporting for Buffer Pools and Packages.
ANALSMF 14.178 SMF Simulator now tests a CISIZE of 18432 for 3390s.
ASMDALO 14.222 Beta ASM failed due to careless changes.
ASMIMSL5 14.129 Support for IMS 5.1 APAR PN76410 (INCOMPATIBLE)
ASMIMSLG 14.148 SLOTS table moved above the 16MB line.
ASMTAPES 14.037 MAINTLEV 8 of MXG Tape Mount and Allocation Monitor.
ASMTAPES 14.086 MAINTLEV 9, monitor does not stop, new TMNT013I.
ASMTAPES 14.322 ML11 of the Tape Mount/Allocation monitor. No SRB!
ASMTAPES 14.351 ML 12 of MXGTMNT included in MXG 14.14.
ASMVTOC 14.003 Archaic assembly member was wrong on MXG 13.13
ASUM70PR 14.319 ASUM70PR LPAR data LPnCAP and LPnSHARE new variables.
ASUMAPAF 14.062 SORT ORDER error if you increase number of domains.
ASUMDB2R 14.287 NUMPLANS now counts only DB2PARTY='S', ='O'.
ASUMUOW 14.343 New ASUMUOW for CICS MRO and DB2 Unit of Work merge.
BUILDPD3 14.169 JES3 type 25 MDS Tape Mounts/Fetches in BUILDPD3.
BUILDPDB 14.185 VM Print sent to JES2 is now merged in PDB.JOBS.
BUILDPDB 14.210 SORTEDBY= asserted for PDB.JOBS/STEPS/PRINT/SMFINTRV
BUILDPDB 14.245 Duplicate data protection for additional datasets.
CICINTRV 14.188 Old CICINTRV replaced CICINTRZ, fixed for CICS 4.1.
CICINTRV 14.211 CICS 4.1+ variable A02TTA missing in CICEODRV.
CICINTRV 14.352 Revised "CICINTRZ" logic now replaced CICINTRV.
DIFFDB2 14.167 DB2 4.1 DB2STATS interval missing due to QWHSISEQ.
DIFFDB2 14.194 Extra obs in DB2STATB/DB2STATR, negative SEQCHECK.
DIFFDB2 14.231 SEQCHECK logic in Change 14.267 was incorrect.
FORMATS 14.255 Petabytes now formatted. (1000 Terabytes=1 Petabyte).
IHDRDCOL 14.027 First of new "IHDRyyyy" - "INFILE header" exits.
IMAC6ESS 14.036 Decoding of SMF type 6 ESS segment is added.
IMACEXCL 14.024 CICS Excluded Field support enhanced for multiples.
IMACICOC 14.123 Omegamon for CICS OMSUPRTM/OMDCOMTM incorrect.
IMACICOC 14.272 SAP Umbrella Trans Program/Tranname in OMUMBUSR/BPTC.
JCLADHOC 14.140 New example for ad hoc job to select specific data.
JCLTMON 14.012 Example JCL for Landmark's The Monitor for CICS.
JCLall 14.147 All MXG JCL examples now specify REGION=0M.
MONTHBLD 14.010 NOTSORTED error with ASUMCICS in monthly logic.
MXGSAS 14.140 Revised MXGSAS JCL procedure adds TAILORNG= parm.
MXGSAS 14.239 The TAILORNG= JCL parameter causes JCL error.
MXGSAS 14.304 TAILORNG symbolic finally corrected in MXGSAS JCL.
PROCSRCE 14.332 New member PROCSRCE is "Proc Source" for ASCII SAS.
TRNDTALO 14.130 INVALID DO LOOP error if ALOCSTRT=. or ALOCEND=.;
TRNDTALO 14.176 Redesign of TRNDTALO to "SPIN" active allocations.
TYPE102 14.047 DB2 Trace T102S096 vars QW0096SN,SC,SK corrected.
TYPE102 14.138 New datasets with all SQL text added for DB2 trace.
TYPE102 14.206 Dataset T102S231 corrected.
TYPE102 14.311 MXG now converts DB2 GMT time stamps to local.
TYPE110 14.089 Support for PN69653 (YYYY digit year in COLLTIME).
TYPE110 14.106 Variables MCTMNTAD/SMFPSRVR added to CICSEXCE.
TYPE110 14.184 CICSTRAN variable TRANTYPE increased to two bytes.
TYPE110 14.209 Support for CICS/ESA 5.1.0 (INCOMPATIBLE).
TYPE110 14.212 CICS 4.1+ incorrect MCTMNTAD GMT offset circumvented.
TYPE116 14.087 Variable QWHCATYP was INCOMPATIBLY renamed QWHCXTYP.
TYPE16 14.150 Support for DFSORT Release 13 APAR PN71337.
TYPE21 14.256 Support for APAR OW22209, bytes read/written.
TYPE26J2 14.303 INREASON wrong for LnnnnJRm syntax for JES2 INDEVICE.
TYPE28 14.023 Some NPM VVR (VTAM Virtual Route) variables trashed.
TYPE28 14.065 NPM APARs OW08565 and OW10584 for 3746/900 supported.
TYPE28 14.335 Support for NPM APAR OW17875 added new subtype 2Ax.
TYPE30 14.099 Auto Restart section INPUTs were incorrect.
TYPE30 14.172 Variable EXECTM in TYPE30_V wrong if only subtype 3.
TYPE37 14.213 Support for NETVIEW 3.1 type 37 changes.
TYPE42 14.063 DASDMPL 1000 times too large in TYPE42DS.
TYPE42 14.131 Support for APAR PN78083 required no change to MXG.
TYPE42 14.309 Support for type 42 new subtype 19 + enhancements.
TYPE6 14.009 Truncated PSF type 6 record INPUT STATEMENT EXCEEDED
TYPE6156 14.242 Truncated catalog cell=04 caused STOPOVER.
TYPE64 14.004 INPUT STATEMENT EXCEEDED, CF Cache Structure segment.
TYPE7072 14.051 ELAPSTM added to TYPE72GO, and RMFINTRV for WLM.
TYPE7072 14.059 TYPE72GO variable VALDSAMP and delay PCTs wrong.
TYPE7072 14.180 Variable PERFINDX now created in TYPE72GO.
TYPE71 14.058 Support for Shared Page Groups added.
TYPE71 14.302 New Shared Paging variables were still wrong.
TYPE72 14.085 MVS/ESA 5.2.2 variables overlooked in TYPE72GO.
TYPE72 14.254 TYPE72GO vars R723CSCR,CSPA,CSPE were still wrong.
TYPE73 14.164 APAR OW15406 for RMF adds support for Year 2000.
TYPE74 14.085 MVS/ESA 5.2.2 variables overlooked in TYPE74OM.
TYPE74 14.152 Support for type 74 subtype 5 Cache RMF Reporter.
TYPE74 14.236 Support for RMF type 74 subtype 100 IRLM long locks.
TYPE74 14.291 Coupling Facility Structure Data PTF UW90312.
TYPE74 14.328 R744SSIZ is in 4000, not 4096 units.
TYPE78 14.121 Variable PCTALLBY, LCUIORT added to TYPE78CU dataset.
TYPE78 14.166 ARRAY statement changed to _TEMPORARY_ to save CPU.
TYPE80 14.070 Support for IBM APAR OW19251 (RACF year 2000).
TYPE80 14.114 Support for RACF 1.10 (toleration).
TYPE80A 14.170 More RACF Reports for Command Events decoded.
TYPE80A 14.252 Invalid RACFTYPE=03 segment caused STOPOVER.
TYPE88 14.066 INPUT STATEMENT EXCEEDED corrected.
TYPE89 14.158 Support for Subtype 2 (Measured Usage Product Sumry).
TYPE89 14.233 TYPE89 variable MULCURD wrong for Batch Pipes.
TYPE99 14.069 TYPE99_2 now has obs for each period vice just first.
TYPEAPAF 14.307 Support for APAF Millennium subtypes 31 and 32.
TYPEAPAF 14.330 Amdahl APAF Version 3.0 records have been validated.
TYPEBETA 14.050 INVALID DATA FOR BETASTRT and BETAEND with 1.6.5.
TYPEBETA 14.084 INPUT STATEMENT EXCEEDED for SUBTYPE=41.
TYPECACH 14.093 Support for IBM's Cache RMF Reporter CRR 1.7
TYPECIMS 14.312 IMF flags in DBD section were not reset.
TYPECMF 14.033 MXG now recognizes 3990 model 6 in CMF user SMF.
TYPEDALO 14.215 Beta Version of MXG DASD Allocation Monitor
TYPEDB2 14.011 DB2 4.1 type 101 subtype 1 INPUT STATEMENT EXCEEDED.
TYPEDB2 14.044 Protection for truncated DB2 record.
TYPEDB2 14.071 Dataset DB2STATB now always has observations.
TYPEDB2 14.105 QWSDLR length 8, QWSCIID corruption corrected.
TYPEDB2 14.174 VMACDB2 ERROR ... QWHSIID=230 UNEXPECTED fixed.
TYPEDB2 14.195 DB2STATR, DB2 remote counts, corrected.
TYPEDB2 14.208 Datasets DB2GBPST and DB2GBPAT all BP now output.
TYPEDB2 14.217 DB2ACCT variables QTGA, QBGA trashed.
TYPEDB2 14.226 DB2 Group Buffer Pool DB2GBPST repeats first segment.
TYPEDB2 14.310 DB2GBPST dataset now deaccumulated and usable.
TYPEDB2 14.311 MXG now converts DB2 GMT time stamps to local.
TYPEDMON 14.125 Support for ASTEX 2.1 (INCOMPATIBLE).
TYPEEDGS 14.029 DFSMS/rmm type "O" INPUT STATEMENT EXCEEDED RECORD.
TYPEEDGS 14.289 DF/SMS Rmm records type V caused error.
TYPEEDGS 14.297 Variables MVxxxx now input from type "V" record.
TYPEEREP 14.021 INPUT STATEMENT EXCEEDED with EREP CLASRC='40'X.
TYPEF127 14.032 Support for FACOM MSPE/EX PTF 93061 for ID=127 SMF.
TYPEFTP 14.054 Support for FTP subtype 51x SMF record.
TYPEHARB 14.229 Support for Interlink's Harbor 4.1 SMF record
TYPEHIPR 14.015 Hipercache VSAM buffer field wrong in MXG 13.13.
TYPEHMF 14.316 HMF subtype 5 with 1 segment INPUT EXCEEDED error.
TYPEHSM 14.052 Short HSM ABARS FSRTYPE=15 INPUT STATEMENT EXCEEDED.
TYPEHSM 14.232 FRSTVOLS CAN CONTAIN ONLY 30 BYTES written in error.
TYPEHURN 14.230 No obs in HURN47 if no external segments.
TYPEIDMS 14.238 Archaic IDMS 10.2.1 caused STOPOVER.
TYPEIMS 14.030 Early testing IMS log records for IMS 5.1
TYPEIMSA 14.017 VARIABLE SYSTEM IS UNINITIALIZED with ASMIMSLG.
TYPEIMSA 14.244 SAP variables SAPTIMTR, SAPCPUT, SAPELTI wrong.
TYPEIPAC 14.240 INVALID ARGUMENT TO FUNCTION MDY, dates not MMDDYY.
TYPEM204 14.171 Support for MODEL204 Release 3.2.1 (INCOMPATIBLE).
TYPEMOVT 14.168 Support for Omegmaon/VTAM V200 (INCOMPATIBLE).
TYPEMWAI 14.249 Support for HP's Measureware for AIX.
TYPEMWUX 14.134 Support for HP MeasureWare for HP-UX platform.
TYPENDM 14.034 NDM or Connect Direct timestamps missing, data wrong.
TYPENDM 14.116 Support for NDM 1.4 (compatible) adds variables.
TYPENOAM 14.057 Support for STK's NearOAM user SMF record.
TYPENSPY 14.005 INPUT STATEMENT EXCEEDED, NSPY 4.6, type A, invalid.
TYPENSPY 14.053 LUNETID PCSESSID VILUNAME in dataset NSPYLU trashed.
TYPENSPY 14.111 Support for NETSPY Release 4.7 (compatible).
TYPENTSM 14.293 Support for Windows NT measurement with NTSMF.
TYPENTSM 14.299 Support for Windows NT measurement with NTSMF.
TYPEOMSM 14.219 Support for Candle's Omegamon for SMS V150 (no chg!).
TYPEOPC 14.077 INVALID MTD SUBTYPE, observations not output.
TYPEORAC 14.103 Accounting data input incorrectly for ORACLE.
TYPEORAC 14.247 Support for Oracle Release 7.2.3 SMF record.
TYPEQAPM 14.098 Support for AS/400,OS/400 Release 3.6 (INCOMPATIBLE)
TYPEQAPM 14.271 Support for AS/400,OS/400 Release 3.7 (INCOMPATIBLE)
TYPERACF 14.243 Support for RACF 2.1 IRRDBU00 unload utility.
TYPERMDS 14.092 Support for IBM's RMDS Version 2.2 (no change)
TYPERMDS 14.300 RMDSARN/ARI missing in RMDS 1.3/1.4.
TYPESAMS 14.013 INVALID DATA FOR HH,MM,SS with SAMS SMF record.
TYPESFTA 14.179 Support for SoftAudit Version 5.1 (INCOMPATIBLE).
TYPESNIF 14.186 Network General's Sniffer Network Monitor data.
TYPESTC 14.001 INPUT STATEMENT EXCEED for HSC subtype 8 record.
TYPESTC 14.055 STK's HSC Subtype 08 now in two lengths, 38 and 40!
TYPESTRS 14.349 Support for Demand Technology's Stress Test 3.3.6.
TYPESUIN 14.248 Support for Applied Software's SUPER IND$FILE SMF.
TYPESYNC 14.115 Syncsort variables SORTBEGN/END midnight spanning.
TYPETAND 14.223 INFILE statements for TANDCTLR/TANDLINE need LRECL.
TYPETCP 14.276 FTPLOCAL,FTPREMOT not decoded after Change 14.040.
TYPETLMS 14.014 TLMS year 2000 dates were not decoded correctly.
TYPETMDB 14.197 Support for TMON/DB2 Version 3 (INCOMPATIBLE).
TYPETMON 14.042 INVALID DATA for TIGETMCT or TIFREMCT corrected.
TYPETMON 14.336 Support for Landmark The Monitor for CICS 1.5, COMPAT
TYPETMS5 14.018 TMS datasets TMSRECS,DSNBRECS now deleted from WORK.
TYPETMVS 14.135 Support for Landmark TMON/MVS spanned records.
TYPETPM 14.113 Support for Thruput Manager #V041238 (INCOMPATIBLE).
TYPETRSN 14.218 Support for Desktalk's TRENDSNMP SNMP IFENTRY data.
TYPETSOM 14.334 Segmented TSO/MON records with only DRU STRTTIME=.;
TYPEVM 14.008 INVALID DATA FOR PWCOUNT in VMID=06 VM Accounting.
TYPEVSME 14.278 Support for VTAM Session Management Exit SMF record.
TYPEWSF 14.143 Support for RDS's EOS Enterprise Output Solution
TYPEWSF 14.228 Support for RSD's EOS Product SMF record.
TYPEX37 14.091 STOPX37 SMF records changed by Boole, useless now.
TYPEXSTR 14.144 Support for Anacomp, Inc's XSTAR product SMF record.
TYPPROS 14.207 Support for Boole & Babbage's PRO/SMS.
UCICSCNT 14.060 Enhanced CICS diagnostic tool for EXCLUDE/INCLUDE.
UDB2GTF 14.154 Support for DB2 records written to GTF.
UDEBLOCK 14.155 Utility to create valid RECFM=U on MVS from PC data.
UTILCONT 14.216 Utility contents of SAS library, sizes in Megabytes.
UTILGETM 14.018 Type 110 Subtype 2818 recognized and counted.
VMXGHSM 14.235 SMS-related Class fields in both MCC and MCD added.
VMXGSUM 14.177 If DESCENDING was used with KEEPALL=NO, it was lost.
VMXGTAPE 14.153 Utility macro to determine if lib/dsn is on tape.
WEEKBLDT 14.010 NOTSORTED error with ASUMCICS in weekly logic.
YEAR2000 14.100 Use of Date literal '01JAN00' changed to '01JAN1900'
YEAR2000 14.305 Format of year 2000 status revised with vendor fixes.
Inverse chronological list of all Changes:
NEXTCHANGE: Version 14
===Changes thru 14.352 were included in MXG 14.14 dated Feb 21, 1997===
Change 14.352 Member CICINTRV is now the enhanced logic that was first
CICINTRV tested as "CICINTRZ". The new logic creates only the
Feb 20, 1997 PDB.CICINTRV data set with CICS interval statistics.
The other four old datasets, CICEODRV,CICREQRV,CICRRTRV
and CICUSSRV should have been deleted, as they are now
meaningless, but they are still created (but now with no
observations) to prevent unnecessary failure if any of
your other jobs reference those datasets (in your weekly
or monthly, for example, if they were copied). Take the
time to remove any references to those now defunct data
sets to avoid future errors when they are deleted.
Change 14.351 ML 12 of the MXG Tape Mount and Tape Allocation Monitor
ASMTAPES MUST be installed for MVS/ESA 5.2.2 or OS/390 to avoid
ZSMTAPES possible UCB errors (due to relocated UCBE in MVS). Not
ZZMTAPES only does this revision solve that problem, it builds on
Feb 20, 1997 ML 11 (which replaced SRB with Cross Memory Services) and
Good News:
-Creates new TMNTTYPE=5 "Interval Allocation" record that
is written at the end of each (default=hour) interval for
each drive that was allocated. This will allow us in the
analysis programs to accurately count tape drives without
having to wait (days or weeks?) until the tape drive was
deallocated.
-Supports the workload manager, with new data elements
for Service class, workload name, resource group, and
resource class.
Bad News:
MXG 14.14 VMACTMNT processing code does not decode the
new fields, nor the subtype 5 record; that enhancement
should be available in early April.
Other News:
-Has new assembly time operating system parameter that you
must supply. The values are ESA or ESA5. ESA5 supports
MVS/ESA Version 5 and OS/390 and must be specified so the
correct IBM macros are used.
-Supports the new access to the UCB common extension.
-Changed SRB error fields to AR mode error fields.
-Corrected MODESET errors in AR mode.
-Changed initial tape UCBSCAN into subroutines.
-Support for above the line UCB's.
For archive, ML 9 is now in ZZMTAPES, and ML 11 is in
ZSMTAPES member.
Change 14.350 Dataset TYPE74CA was not created in the WEEKly PDB if
WEEKBLDT you used WEEKBLDT (but was with WEEKBLD). Now it is
Feb 20, 1997 created with either weekly job.
Thanks to Freddie Arie, Lone Star Gas, TEXAS.
Change 14.349 Support for Stress Test Release 3.3.6 Enhancements.
VMACSTRS Both the original and the enhanced SMF record is now
Feb 20, 1997 supported transparently. This release adds new data
to the SMF record that will soon allow control cards
for Stress Test parameters to be created to match your
existing DASD rates (by using TYPE74 and TYPE74CA SMF
data to measure your system). That analysis/generator
should be available in April.
Thanks to Chuck Hopf, MBNA, USA.
Change 14.348 Variable JOBCLASS was increased to LENGTH $8 (from $1)
VMAC30 in VMAC30 and VMAC26J3 because JES3 needs all eight
VMAC26J3 bytes for JES3 Main Class. Only one byte is input in
Feb 19, 1997 VMAC26J3, but by increasing the length in TYPE26J3 will
May 21, 1997 cause the kept size in BUILDPD3 to be eight bytes. What
is really slick is that the length of JOBCLASS in the
JES2 PDB.JOBS and PDB.STEPS datasets will still be only
one byte, so there is no increase in the size of the JES2
PDB as a result of this change to type 30. However, the
TYPE30_x datasets will have JOBCLASS with length 8 to
support either JES2 or JES3 job class names.
Thanks to Jack Mintz, Hudson Williams, USA.
Change 14.347 Continued enhancements to the RMF-like reporting.
ANALRMFR -ANALRMFR now detects and reads PDB on tape or disk.
Feb 19, 1997 -Workload Activity Report-Compatability Mode,
REPORT=WKLD, RPTOPT parameter is now the way
to make report selections. If none are selected
no reports are created.
RPTOUT=PERIOD Performance group period
within performance group.
GROUP Summarizes data for all performance
group periods within the
performance group.
DOMAIN Summarizes data by domain for the
entire system.
STM Summarizes data for the entire
system.
-Workload Activity Report-Goal Mode, REPORT=WLMGL
RPTOPT=WGPER:
Update Sevice Policy Page column Resource Groups
allowing for all service classes to be output.
-Workload Activity Report-Goal Mode, REPORT=WLMGL
RPTOPT=RCLASS, report classes defined in a service
policy, is added.
-Workload Activity Report-Goal Mode, REPORT=WLMGL
RPTOPT=SCLASS, summary of data for all service class
periods defined for a service class, is added.
There was no data to confirm values.
-Coupling Facility Activity, REPORT=CF
Reports created "Coupling Facility Usage Summary"/
"Structure Summary"/"Storage Summary"/"Processor
Summary" and "Coupling Facility Structure Activity"
Unconfirmed values a ouput on the report as "??".
-LCU summary does not include the first device.
Remove LCUIORAT=0 ....... from FIRST.DATE OR
FIRST.TIME OR FIRST.DEVCLASS.
Move LCUIORAT=SUM(LCUIORAT,IORATE)
.
To after FIRST.LCU THEN DO;
Thanks to David Childress, Lowe, USA.
Thanks to Alan M. Sherkow, Management Strategies LTD.
Change 14.346 Variables NRBINDS and NRLIMITS should have been spellec
VMACTPM NBINDS and NLIMITS, and variable JCTJOBID was added to
Feb 17, 1997 the KEEP= list for dataset TYPETPMF.
Thanks to Brian Sanga, Eagle Star Group Services Ltd, ENGLAND.
Change 14.345 The FMXGUCBL function (to allocate dynamically all DASD
FMXGUCBL devices for the archaic VMACVTOC) did not support four
Feb 17, 1997 digit UCBs, but now does, thanks to this contribution.
Thanks to Sue Yarker, Midland Bank, ENGLAND.
Change 14.344 "IHDR" exit for Boole and Babbage IMF records was added,
IHDRCIMS after newsletter text was sent to the printer. See text
VMACCIMS of Change 14.342.
Feb 17, 1997
===Changes thru 14.343 were printed in MXG Newsletter THIRTY-ONE=======
Change 14.343 New ASUMUOW summarizes CICSTRAN and DB2ACCT by "Unit of
IMACUOW Work UOW" to create PDB.ASUMUOW with total CICS and DB2
ASUMUOW resources in a single observation, keeping the original
Feb 19, 1997 TRANNAME and USERID of the real UOW. Member IMACUOW will
May 4, 1997 enable "SPINing" of incomplete CICS transactions (e.g.,
long running LU 6.2 events) to ensure completeness. This
member is a replacement/enhancement of ANALDB2C that is
renamed to an ASUMxxxx because it is now designed to be
executed as a data-set-builder (PDB.ASUMUOW) rather than
an ANALysis example (and UOW makes more sense than DB2C)!
The main assumption is that the earliest transaction for
any UOW must be the first transaction; during the merge,
if the TRANNAME of the first transaction is CSMI (i.e.,
an MRO mirror) or is blank (DB2), that transaction is
not complete, and the current records are SPUN (written
to the SPIN library to be held until the next run, if you
updated macro _SPINUOW in member IMACUOW to non-zero).
The ASUMUOW dataset contains the same CICS variables as
are needed to create the ASUMCICS interval summary from
detail CICS transactions (plus the DB2 variables for CICS
transactions calling DB2), so the ASUMUOW dataset could
be used as input to ASUMCICS (you would probably want to
make your own enhanced copy that also keeps the DB2
variables) so as to create interval UOW statistics. In a
test of 2.6 million tran obs in CICSTRAN, ASUMUOW had
only 1 million obs. ASUMUOW can be used even if only
CICSTRAN data exists, as it will combine all MRO events
into one observation per UOW.
Text revised May, and November, 1997.
Thanks to Chuck Hopf, MBNA, USA.
Change 14.342 "IHDR" exits (taken after the header of raw records have
IHDRTMON been read in) are added for Landmark's Monitor for
IHDRTMDB CICS/ESA and for Landmark's Monitor for DB2. These
IMACMONI "IHDR" exits are similar to the "IMACFILE" exit for SMF
IMACTMDB (which should be named IHDRSMF by my new naming
TYPETMON convention).
VMACTMDB
Feb 15, 1997
Change 14.341 Using EXTMSTMS and macro _KTMSTMS in IMACTMS5 to create
TYPETMS5 new variables did not work as expected. The new
Feb 15, 1997 variables were added to the initial TMSTMS dataset, but
post processing in TYPETMS5 did not include the _KTMSTMS
macro reference, so the new variable was lost. The
_KTMSTMS and _KTMSDSN references were added.
Thanks to Andy Chandler, Eagle Star, ENGLAND.
Change 14.340 DB2 Reporting Enhancements for DB2-PM like reports from
ANALDB2R DB2 4.1. Individual Buffer Pool and Individual Package
ASUMDB2A Execution data is now reported (See DB2 Technical Note in
ASUMDB2P Newsletter THIRTY-ONE). The Account Detail and Long
TRNDDB2A Trace reports now use the detail buffer and package data
TRNDDB2P (DB2ACCTB and DB2ACCTP) if they exeist. The default
Feb 15, 1997 assumption is that all of your DB2 datasets are in the
PDB libref, but if you have used IMACDB2 to send them
to different librefs, you can tell ANALDB2R where to find
them with the new DB2ACCT=, DB2ACCTB=, and DB2ACCTP=
arguments in your ANALDB2R invocation.
This change is incompatible with prior versions of the
ANALDB2R report in that only a single PDB will be used
to generate the report. (Previously, you could specify
PDB=PDB1 PDB2 PDB3, and the libraries would have been
"concatenated". This restructure lost that capability
but you can easily combine multiple PDB datasets first
and then invoke ANALDB2R.)
Most, but not all, of the DB2 4.1 fields have been
added; in particular, the individual buffer and package
sections are complete.
Thanks to Chuck Hopf, MBNA, USA.
Change 14.339 User enhancements to the ASMIMSLG/ASMIMSL5 programs for
ASMIMSLG IMS log processing protect for a short error message,
ASMIMSL5 and in case of MSC transactions, since the ARRVTIME may
Feb 14, 1997 be wrong (out of sync), now, the MSC timestamp is used
for ARRVTIME with good results.
Thanks to Harry Olschewski, dvg Hannover, GERMANY.
Change 14.338 Variable HIUICAV (TYPE71) was added to RMFINTRV dataset
RMFINTRV (the maximum of the individual values is kept) and it is
TRNDRMFI added to TRNDRMFI dataset (the average of the maximum is
Feb 15, 1997 kept).
Thanks to Manfred Thomas, BHF-Bank, GERMANY.
Change 14.337 Candle's EPILOG for MVS decoding was enhanced. The IO
ANALEPMV and ENQ data is now rolled into the EPMVEP dataset. The
VMACEPMV derivation of results to match Epilog screen reports that
Feb 14, 1997 doing straight-forward arithmetic with sample counts did
not resemble their (proprietary) calculations but
diligent work by Simon is now available in the ANALEPMV
member to do those calculations for reports. mon P.
Thanks to SiMundy, Telstra, AUSTRALIA.
Change 14.336 Support for Landmark's The Monitor for CICS/ESA 1.5 is
TYPETMON already in MXG, as the only change in the records is the
Feb 14, 1997 version (LMRKVREL) contains 0Fx rather than 0Ax. Their
Version 2 product is due out this year, but that will
require changes to MXG to support. Stay tuned.
Change 14.335 Support for NPM APAR OW17875 added new NPMSUBTY=2Ax that
VMAC28 is now decoded and output in the existing NPMSUMRY data
Feb 14, 1997 set. Subtype 2Ax allows the collection and reporting of
session data summarized by LU Group; the value of
SCDSPLUG (LU Group summarized) is stored in existing MXG
variable SCDSPNAM, rather than creating a new variable.
Change 14.334 Segmented TSO/MON records containing only DRU segments
VMACTSOM have missing STRTTIME in TSOMDRU dataset because MXG did
Feb 13, 1997 not protect for DRU-only TSO/MON records, but now does.
Thanks to Rick Ireland, Imperial Oil Limited, CANADA.
Change 14.333 NTSMF datasets ICMP, TCP, and UDP have been validated
ADOCNTSM with data records and the table in ADOCNTSM updated.
Feb 13, 1997
Thanks to Richard Clary, ENTERGY, USA.
Change 14.332 New member PROCSRCE is "Proc Source" for ASCII SAS. It
PROCSRCE creates a single IEBUPDTE-format file from individual
Feb 13, 1997 files, so that only a single file upload or download is
required to move MXG Source library between ASCII and
OS/390 platforms. See instructions in member PROCSRCE.
The basic technique is to pipe the DIR command's output
DIR *.SAS >> NAMEFILE.MXG /B /ON
to create a list of file names in NAMEFILE.MXG, then
start SAS and submit %INCLUDE SOURCLIB(PROCSRCE); which
reads NAMEFILE and copies each file into IEBUPDTE.MXG,
inserting the ./ ADD NAME=xxxxxxxx statements.
Ain't elegant, but it is how I build the IEBUPDTE.MXG
master file that is copied to 3480 distribution tapes.
The actual file on 3480 tape is about 75MB (because each
record is exactly 80 bytes long) but on ASCII takes only
about 40MB (variable length records with trailing blanks
removed), and it PKZIPs to less than 9MB. To upload MXG
for OS/390 validation, the 9MB IEBUPDTE.ZIP is sent via
IND$FILE across SDLC at 19.2KB, and on MVS is unzipped by
PKZIP for MVS (from ASI, 513-885-2031). With PKZIPing,
transmission takes 90 minutes. Unzipped, transmission
takes 7 hours!
The existing MXG member IEBUPDTE is the inverse of the
PROCSRCE program, as it reads PROCSRCE's output file to
create each member as a separate *.SAS file.
Change 14.331 NETSPY record 'N' might cause INPUT STATEMENT EXCEEDED;
VMACNSPY the +15 and +29 after the INPUT of NSPSTAFL should be
Feb 13, 1997 +16. No error was directly reported, but this might be
why one European site claimed they had to change the DO
interation's maximum value (reduced by one) to avoid an
ABEND (but I never got a record dump for diagnosis!).
Thanks to Carl Downing, BlueCross BlueShield of Minnesota, USA.
Change 14.330 Amdahl APAF Version 3.0 records have been validated with
VMACAPAF data records. Changed test for SUBTYPE=31 or =32 to be
Feb 13, 1997 =49 or =50 (Amdahl listed subtypes in hex not decimal!),
and corrected algorithm for counting bits on in a field
(see SAS Technical Note in Newsletter THIRTY-ONE).
Thanks to Bob Gauthier, American Stores Company, USA.
Change 14.329 SYNCSORT's product COBOL Advantage populates one byte in
VMACSYNC the SYNCSORT user SMF record. New variable SOOPCAT in
Feb 11, 1997 dataset TYPESYNC contains that byte, formatted in hex.
Thanks to Jim Ray, Branch Banking & Trust, USA.
Change 14.328 TYPE74CF (Coupling Facility) QSIZnn variables are the
VMAC74 structure size as specified in the CFRM in units of 4096
Feb 10, 1997 bytes per unit, while TYPE74ST (Structures) R744SSIZ
(and SMAS/SMIS) variables are actual allocated size of
the structure, in units of 4000 bytes per unit, but IBM
did not document the use of 4000 vice 4096. To properly
size the allocations, MXG now multiplies SSIZ/SMAS/SMIS
by 4000 instead of 4096 (and SSIZ will then be smaller
than QSIZ values).
Thanks to Don Deese, Computer Management Sciences, USA.
Change 14.327 Variable I was incorrectly used as the index variable
VMAC102 for two nested loops, which caused VMAC102 to loop.
Feb 7, 1997 There are two places, in the QWHSIID=21 and QWHSIID=44
processing that contain DO I= 1 TO 19 BY 3; In that
line, in the two following lines (...PUT(SUBSTR...
and in the line IF I=19 AND J=7 THEN J=20, change the
"I" to "L" to correct the error.
Thanks to Paul Hill, Midland Bank, ENGLAND.
Change 14.326 MXG 14.11 only. Data set TYPE42S2 had incorrect values
VMAC42 because "NEW" before SMF42FB2/SMF42FB3 was not removed.
Feb 6, 1997 Labels for variables SMFJOD01-SMFJOD16 were corrected.
Thanks to Freddie Arie, Lone Star Gas, TEXAS.
Change 14.325 MXG 14.11 only. Array CFNUM should only have sixteen
VMAC74 elements CFNUM01-CFNUM16 but was accidentally changed to
Feb 6, 1997 CFNUM01-CFNUM64. Had no actual impact.
Thanks to Bruce Widlund, Merrill Consultants, USA.
===Changes thru 14.324 were included in MXG 14.11 dated Feb 4, 1997===
Change 14.324 INVALID RECORD OBJECT=NETWORK INTERFACE error message
VMACNTSM because the test ... OFFDATA NE 20 ... should be NE 21
Feb 4, 1997 (this test is right after the test for
IF UPCASE(OBJECT)='NETWORK INTERFACE' THEN DO;
Thanks to Richard Clary, ENTERGY, USA.
Change 14.323 MXG 14.11 dated Feb 3, 1997 only. Type 102 subtype 100
VMAC102 ERROR: NO MATCHING IF-THEN CLAUSE because the two lines
Feb 4, 1997 QW0100SB=QW0100SB+GMTOFFDB;
QW0100SA=QW0100SA+GMTOFFDB;
were mis-located. They must be immediately before the
OUTPUT T102S100;
statement.
Fortunately, the 100 subtype is not used in ANALDB2R or
any other MXG program, so only specific use of T102S100
exposed the error (my QA caught it but I overlooked it).
Thanks to Freddie Arie, Lone Star Gas, TEXAS.
===Changes thru 14.322 were included in MXG 14.11 dated Feb 3, 1997===
Change 14.322 This is ML11 of the Tape Mount/Allocation monitor.
ASMTAPES This revision eliminates the use of an SRB to capture
ZSMTAPES job-related info, and instead does all of the cross
Feb 3, 1997 memory data collection in AR (access register) mode.
Running in AR mode will cause more recorded CPU time in
the TMNT address space, but what is really happening is
that all of our collection overhead is now captured in
the (calling) TMNT address space, whereas previously some
of the CPU time of the SRB's execution was recorded in
the SMF records of the allocating (monitored) address
space. The previous revision ML9 is in member ZSMTAPES.
ML12 will contain 3 improvements : workload manager
support, UCB common extension access changes, and
configuration change detection using ENF, and will be
available later this year.
Change 14.321 Don Deese's continued research into measurement of the CF
VMAC74 caused me to create new variables R744QSIZ and R744QFLG
Feb 3, 1997 from the QO segment into the SO per-structure segment
so QSIZ/QFLG are added to TYPE74ST (while we investigate
why QSIZ is often very difference thatn R744SSIZ!).
The structures names in QO and SO are not in the same
order, so MXG scans across the QO entries to find the
matching SO entry.
Thanks to Don Deese, Computer Management Sciences, USA.
Change 14.320 As will be discussed in the next newsletter, this is the
many first MXG Version (14.11) to be built at our office on
Jan 31, 1997 my new Overland 3480/3480IDRC/3490/3490E tape drive.
The EBCDIC to ASCII translation with IND$FILE is not the
same as the Overland default, and the Overland default is
also wrong (especially trashing the long-vertical-bar and
the not-sign), so I had to build my own translate table
to create EBCDIC tapes from my ASCII master file:
MXG IND$FILE MXG WRONG MXG OUTPUT
ON OUTPUT ON ON EBCDIC W/
MVS ON ASCII ASCII OVERLAND My Table
cent-sign 4A 5B same AD l. Sq. Bracket
not-sign 5F 5E AA caret
long vertial 4F 5D B3 BD r. sq. bracket
split vert 6A 7C same 4F split vert bar
(Note that in NEWSLETTER THIRTY-ONE 'A9'x was erroneously
typed for a not-sign on ASCII, but it is really 'AA'x).
I found I also had to change Overland's (DataTools for
Windows) default ASCII-to-EBCDIC table three errors
5D-->4F and not BD 5B-->4A and not AD
7C-->6A and not 4F
plus my two additions
AA-->5F B3-->4F
To correct symbols on your ASCII platform after you use
IND$FILE to download, change all '5D'x to 'B3'x and all
'5E'x to 'AA'x and your comments with vertical bars
and non-signs will look correct. Of course, before you
could upload that ASCII MXG to EBCDIC with IND$FILE, you
must reverse that change on ASCII before the upload.
I took this opportunity to rid "not-signs" from all MXG
code, using NE or NOT instead, and replaced all of the
remaining instances of double long-vertical-bars (for
concatenation) with double exclamation points, to
minimize any future exposure if MXG source is moved from
ASCII to EBCDIC, and removed all of the '4A'x extraneous
characters in text members.
However, there were some uses of single long vertical
bars that were inside comments and too pretty to lose,
and a few instances of "not sign" (suggesting not to use
it) that were left. These members were revised:
ACHAP08 ACHAP09 ACHAP12 ACHAP13 ACHAP16 ACHAP16
ACHAP17 ACHAP18 ACHAP19 ACHAP19 ACHAP21 ACHAP22
ACHAP23 ACHAP26 ACHAP30 ACHAP32 ACHAP33 ACHAP34
ACHAP37 ACHAP38 ACHAP39 ADOCEREP ADOCVMXA ADOC1415
ADOC7072 ANALCACH ANALCTLD ANALIPAC ANALRACF ANALRRTM
ANALSNAP ANALVARY ANALVMOS ANALVVDS IDMSBLT IDMSJANL
IDMSJRNL JCLCRAYC LOADINFO REXXCOPY REXXEMAC REXXPDB
REXXTEST SYSLOGJE TTXPDS TYPEIMS UTILFMTX UTILPRNL
UTILSPAC UTILXRF1 VMACIPAC VMACRRTM VMAC102 VMXGHSM
XIBMFDP XLOGREC XNALCACH XNPMSESS XTYPEVS1 ZNALDB2R
ZRBIPSJ
MXG is now distributed as an unnumbered data set; columns
73 thru 80 are blank in all records on the MXG tape.
I have not used line numbers for references for several
years, and eliminating line numbers makes the source
library much smaller on ASCII.
Change 14.319 LPAR data now contains flag variable LPnCAP to indicate
ASUM70PR which partitions are Capped, and variable LPnSHARE which
Jan 31, 1997 contains the partitions percentage of the sum of the LP
share values (i.e., if the partition is Capped, then
LPnSHARE is the capping percentage).
Thanks to Ian Porter, Nissan European Data Center, SCOTLAND.
Change 14.318 Support for OS/390 Release 3 (Compatible) adds major new
VMAC7072 measures to the TYPE72 and TYPE72GO datasets; the first
Jan 30, 1997 five variables were added to both (i.e., COMPATIBILITY
MODE in TYPE72 and WORKLOAD MANAGER in TYPE72GO):
R723CICT='NON-PAGING*DASD I/O/CONNECT*TIME'
R723CIDT='NON-PAGING*DASD*DISCONNECT*TIME'
R723CIWT='NON-PAGING*DASD I/O*WAIT*TIME'
R732CIRC='NON-PAGING*DASD I/O*SSCH COUNT'
R723VELI='EXECUTION*VELOCITY*INCLUDES*I/O DELAY?'
and only in WORKLOAD MANAGER do we find:
PCTDLIOD='DASD*DELAY*SAMPLES'
PCTDLNDI='NON-DASD*I/O USIN/DELAY*SAMPLES'
PCTDLQ ='QUEUE*DELAY*SAMPLES*WAIT FOR*SERVER'
PCTDLSHS='SERVER*HIPERSPACE*PAGING*DELAY'
PCTDLSMP='SERVER*MPL*DELAY*SAMPLES'
PCTDLSPV='SERVER*PRIVATE AREA*PAGING DELAY'
PCTDLSSW='SERVER*SWAP-IN*DELAY*SAMPLES'
PCTDLSVI='SERVER*SPACE VIO*PAGING*DELAY'
PCTUSIOU='TOTAL*USING I/O*SAMPLES'
PCTUSTOU='TOTAL*USING*SAMPLES'
The calculation of VELOCITY is also changed in Release 3,
as PCTUSTOU (R723CTOU) replaces PCTUSCUS (R723CCUS) in
the numerator and variable R723VELI='Y to indicate that
the exection velocity now includes I/O delays.
Change 14.317 Dataset DB2ACCTP (Package Accounting) has new variables
VMACDB2 QWACBSC and QWACESC (start/stop of plan) added to KEEP=
Jan 30, 1997 list because they appear on DB2PM reports, and because
Oct 13, 2003 variable QPACSCB (start of package) cannot be used, as
it is null in the 2nd and subsequent segments of the
type 101 subtype 0 (accounting record, holds first ten
package statistics), and QPACSCB is nulls in ALL of the
type 101 subtype 1 (package only) records, and finally
because the subtype 1 record is written first (so I can
not retain from the subtype 0!).
Update: October 13, 2003: QPACSCB and QPACSCE appear
to always exist, now, in DB2ACCTP observations, both
from Subtype=0 (first 10 packages), and from Subtype=1
(more than 10 packages).
However, QWACBSC and QWACESC will always have missing
value in DB2ACCTP observations from subtype=1 because
that record does not contain the QWAC segment!
This 2003 note is only for documentation.
Thanks to Chuck Hopf, MBNA, USA.
Change 14.316 Subtype 5 HMF record with only 1 segment caused INPUT
VMACHMF STATEMENT EXCEEDED error. Although undocumented, this
Jan 29, 1997 record had only the bus segment; there was no memory
segment present. To correct, insert after the @; that
is after the INPUT of HMF5BUS:
IF HMF5SEGS EQ 2 THEN DO;
and after the following IF SKIP GT 0 THEN INPUT +SKIP @;
insert END;
(so that only the bus stats are read when HMFSEGS=1).
Thanks to Ann Knapik, ISSC Akron, USA.
Change 14.315 DB2 utility programs set QWHCATYP=41 as their attachment
FORMATS type value, an undocumented value that IBM does not set.
Jan 28, 1997 The site is pursuing IBM for a better answer.
Thanks to Roman Jost, Gjensidigo, NORWAY.
Change 14.314 Dataset MEMOACCT new variables ENTRCALE/ENTRFORM are now
EXTYMEMO INPUT from previously reserved fields. In addition, the
VMACMEMO MEMOACCT dataset contains variable CURRMODE with values
Jan 28, 1997 of T - terminate session or C - continuation, the latter
having accumulated values, so in most cases you only want
the type T, so in member EXTYMEMO I have added an example
of the code IF CURRMODE='T' THEN OUTPUT _LTYMEMO; that
would cause only type T obs to be output, but that sample
code in EXTYMEMO is commented out by default, so MXG will
create both C and T observations until you change it.
Thanks to Roman Jost, Gjensidigo, NORWAY.
Change 14.313 Invalid type 80 RACF record caused INPUT STATEMENT EXCEED
VMAC80A error. The record, an RACFEVNT=21:RDEFINE has pairs of
Jan 28, 1997 (SMF80DTP,SMF80DLN) (data type, data length, in decimal)
of (6,151),(12,12),(81,08),(0,21),(6,8), then 543 (24,12)
segments, a (49,20) and a (53,80). The first DTP=6 is
the expected 151 bytes, but there is a later DTP=6 with
unexpected length of 8. The DTP=12 is 12 bytes instead of
the documented multiple of 9. There are no DTP= 0 or 81
values documented by IBM. And inside the DTP=12 data
segment, the characters do not conform with the expected
format, so this record was partially hosed, but still by
adding protection for these (invalid) unexpected lengths
in the DTP= 6 & 12, and for the unexpected DTP= 0 & 81,
the rest of the type 80 records can be read while IBM is
contacted to find a fix to prevent the bad record.
Thanks to Silva Viviani. Fondo Commune D.C. Rurali Trentine, ITALY.
Change 14.312 IMF flag variables in the DBD section were not reset for
VMACCIMS the next DBD segment, and thus were incorrectly carried
Jan 28, 1997 forward. ELSE variable=' '; clauses were added for the
variables: DBTOVFLW DBTMSCNT DBTTYDDN DBTTYOTH DBTTYSEC
DBTVSAM and DBTOSSB
Thanks to Sieghart Seith, FICUCIA, GERMANY.
Change 14.311 MXG now converts GMT timestamps in DB2 records to local
EXDB2ACC time automatically, but this change is INCOMPATIBLE for:
VMACDB2 sites that already use member EXDB2ACC to change GMT to
VMACDB2H local for variables QWHCBSC and QWHCESC (which was the
VMAC102 MXG recommendation prior to this change!). For those
Jan 27, 1997 sites, you must remove your conversion code and let MXG
convert those and all DB2 timestamps for you.
The revised algorithm detects not only the hours of delta
time between SMFTIME (local) and THISSTCK (GMT), but also
now detects the seconds of delta time (values of 20
seconds were seen, which is about the current number of
leap seconds that is included in the STCK value in
SYSPLEX environments, but leap seconds are not included
in SMFTIME values). The value of the GMT Offset,
GMTOFFDB, may not be exact hours. We found a THISSTCK
value of 16:00:20 and SMFTIME was 10:00:00 so GMTOFFDB
was -06:00:20! Without those extra 20 seconds in the
GMT offset, the converted local times would be off by 20
seconds, so don't disbelieve a GMT offset that is not
exact hours. I arbitrarily set any difference less
than 10 seconds to zero, even though current measurements
show a maximum real fuzziness of less than 0.12 seconds,
because I expect delta seconds to be due to leap seconds
and the value of 10 might cover pathological cases when
SMFTIME was delayed. The new algorithm to calculate the
GMT offset, GMTOFFDB, which is used in VMACDB2 & VMAC102
members, is contained in VMACDB2H:
DELTASMF=SMFTIME-THISSTCK;
GMTOFFHR=(100*FLOOR((DELTASMF+30)/100))/3600;
GMTOFFSC=DELTASMF-3600*GMTOFFHR;
IF ABS(GMTOFFSC) GT 10 THEN
GMTOFFDB=3600*GMTOFFHR+GMTOFFSC;
ELSE GMTOFFDB=3600*GMTOFFHR;
Thanks to Chuck Hopf, MBNA, USA.
Change 14.310 -Dataset PDB.DB2GBPST (Global Buffer Pool Interval Stats)
DIFFDB2 contained accumulated (and hence useless) values, but it
VMACDB2 is now deaccumulated to contain valid interval data by
Jan 27, 1997 its support in member DIFFDB2.
-Dataset PDB.DB2STAT1 and PDB.DB2STATS variable QBGLGN
should never have been kept; it is the Group Buffer Pool
ID in each of the segments, and is kept only in the
detail PDB.DB2GBPST dataset.
Thanks to Ermanno Bertolotti, Banca Commerciale Italiana
Thansk to Daniela Busani, Banca Commerciale Italiana
Change 14.309 Support for additional variables in type 42 subtypes 15,
EXTY42X1 16, 17, 18, and new subtype 19 creates new MXG dataset:
VMAC42 TYPE42X1 - VSAM RLS Local Buffer Manager counters.
Jan 25, 1997 See notes in member ADOC42 for details.
Thanks to Michael E. Friske, Fidelity Systems, USA.
Change 14.308 Support for NTSMF Beta added new records, support for NT
VMACNTSM 3.51, and graceful detection of new record types. Have
Jan 25, 1997 tested 34 record types, of the 56 known records. See the
status and complete technical discussion in ADOCNTSM.
Change 14.307 Support for APAF v3.0 added new Millennium subtype 31 and
EXAPAFCB 32 records which create three new APAF datasets:
EXAPAFLP Dataset Subtype Description
EXAPAFSY APAFSYSD 31 Global system data
IMACAPAF APAFLPAR 32 LPAR and Physical CPU data
VMACAPAF APAFCHN 32 Channel data
Jan 25, 1997 Member IMACAPAF was incompatibly changed (because of the
Jan 30, 1997 creation of new datasets) and must be refreshed in your
USERID.SOURCLIB tailoring library.
The new subtype 31 contains only the "Physical" partition
times, while the subtype 32 contains the Total Dispatch
and Effective Dispatch, from which LPAR Management Time
is calculated for the Millennium processors.
Thanks to Bob Gauthier, American Stores Company, USA.
Change 14.306 Variable QBACHRF was added to the SUM= list of variables
ASUMDB2B to be summarized in creation of ASUMDB2B.
Jan 21, 1996
Change 14.305 Year 2000 status was updated. Revised format now shows
YEAR2000 ongoing list of vendor fixes which are required for those
Jan 17, 1996 products that did not support 2000 but now do.
Change 14.304 MXG 14.05-MXG 14.10 only, using the supplied MXGSAS JCL.
MXGSAS Error 180-322, right after the NOTE: THE INITIALIZATION
Jan 17, 1996 PHASE USED 0.13 CPU SECONDS AND 2233K results because the
default value for the TAILORNG symbolic parameter in the
MXGSAS JCL Procedure was still wrong in MXG 14.10. The
error was supposedly fixed by Change 14.239, but that fix
was not implemented in the MXGSAS member until now. The
default TAILORNG symbolic in MXGSAS must be:
TAILORNG='*.NULLPDS,VOL=REF=*.NULLPDS',
Thanks to Ram V. Ramamurthy, Associates Corporation, USA.
Thanks to Walter ?, ???, USA.
Change 14.303 NJE devices with INDEVICE or DEVNAME of LnnnnJRm instead
VMAC26J2 of the (old) expected style of Lnnn.JRm caused INREASON
Jan 17, 1997 to be blank (instead of SR/JR/JT), so these NJE purge
Jan 21, 1997 records were not recognized and were kept as real purge
records in BUILDPDB, causing some fields (like JENDTIME)
to be taken from the wrong purge record. The MXG logic
to create INREASON was revised to recognize the old and
new style of INDEVICE and DEVNAME:
DOTLOC=INDEX(INDEVICE,'.');/*CHECK INDEVICE, 'JR' OR 'SR'*/
IF DOTLOC NE 0 THEN DO;
DOTLOC=DOTLOC+1;
INREASON=SUBSTR(INDEVICE,DOTLOC,2);
IF (INREASON='JR' OR INREASON='SR') AND ORIGNODE GT ' ' THEN
SOURCE=ORIGNODE;
ELSE INREASON=' ';
END;
ELSE IF INDEVICE=:'L' AND '0001' LE SUBSTR(INDEVICE,2,4) LE '9999'
THEN DO; /* FORMAT LnnnnSRm DOES NOT CONTAIN A DOT */
INREASON=SUBSTR(INDEVICE,6,2);
IF (INREASON='JR' OR INREASON='SR') AND ORIGNODE GT ' ' THEN
SOURCE=ORIGNODE;
ELSE INREASON=' ';
END;
IF INREASON=' ' THEN DO;/*IF STILL BLANK, THEN CHECK DEVNAME*/
DOTLOC=INDEX(DEVNAME,'.'); /* 'JT' */
IF DOTLOC NE 0 THEN DO;
DOTLOC=DOTLOC+1;
INREASON=SUBSTR(INDEVICE,DOTLOC,2);
IF INREASON='JT' AND ORIGNODE GT ' ' THEN SOURCE=ORIGNODE;
ELSE INREASON=' ';
END;
ELSE IF DEVNAME=:'L' AND '0001' LE SUBSTR(DEVNAME,2,4) LE '9999'
THEN DO; /* FORMAT LnnnnSRm DOES NOT CONTAIN A DOT */
INREASON=SUBSTR(DEVNAME,6,2);
IF INREASON='JT' AND ORIGNODE GT ' ' THEN SOURCE=ORIGNODE;
ELSE INREASON=' ';
END;
END;
Thanks to Silvio Orsini, Banca D'Italia, ITALY.
Change 14.302 The 22 new Shared Paging variables in TYPE71 starting
VMAC71 with SHPBINAU and thru SHPGLOAV need to be INPUT as
Jan 17, 1997 &RB.8. instead of &RB.4. This corrects Change 14.257.
Thanks to Don Deese, Computer Management Sciences, USA.
Change 14.301 MXG 14.07-MXG 14.10 only, JES3 only, and only if you use
BUIL3005 BUIL3xxx members instead of BUILDPD3. Error 22-7 UNKNOWN
JCLUXRE6 OPTION because SORTEDBY= was misspelled as SORTECBY=, and
Jan 15, 1997 because BUIL3005 was not in my QA stream (but now is)!
Thanks to Chris Weston, SAS Institute Cary, USA.
Change 14.300 RMDS Versions 1.3 and 1.4 records have an undocumented
VMACRMDS section (or one added by APAR) with Originating Job and
Jan 14, 1997 Originating JOBID that was not previously INPUT by MXG.
To add these variables, insert after the @; that is
immediately after the INPUT of RMDSUDAT:
IF RMDSORG='A' AND RMDSACT='C' AND RECKEY='8080'X
AND LENGTH-COL+1 GE 16 THEN
INPUT
RMDSARN $EBCDIC8.
RMDSARI $EBCDIC8.
@;
(These two variables are already INPUT in the code for
later RMDS versions, and so they are in the KEEP= and
LABEL statements already!).
Thanks to Steve Colio, CIGNA Corporation, USA.
===Changes thru 14.299 were included in MXG 14.10 dated Jan 10, 1997===
(although top of CHANGES said only thru 14.298, 299 was there!)
Change 14.299 Support for NTSMF (Windows NT) measurement is now ready
ADOCNTSM for beta testing, and is very well documented. ADOCNTSM
NTINTRV now documents all 54 NTSMF datasets, and the new NTINTRV
VMACNTSM dataset is created (like RMFINTRV). See NTSMF Technical
Jan 8, 1997 Notes.
Change 14.298 PRO/SMS dataset PROSMS does not contain DSN nor DDNAME,
EXPROSMS but new sample code in this exit member (commented out,
Jan 2, 1997 as it may be installation dependent) shows how one site
was able to parse the text to identify which dataset and
DDNAME was altered by PRO/SMS.
Thanks to Warren Hayward, TJX Companies, USA.
Spent an actual Christmas vacation with family, and nothing broke!
Change 14.297 Variables MVUOBMDN,MVUSBIN,MVUSBMDN,MVUSOBIN,MVRETDAT are
VMACEDGS now INPUT from the type 'V' DF/SMSrmm record and are kept
Dec 19, 1996 in dataset EDGSVREC.
Also, the CDS records can be read directly with TYPEEDGS,
so using IBM's utility to dump the data is not required!
Thanks to Richard Fortenberry, Mitsubishi, USA.
Change 14.296 H-P Measureware variable SOFTWARE was kept as a 200-byte
VMACMWAI variable because it was not in the LENGTH statement; now
VMACMWSU it is set LENGTH $30. (and variable AMPM is now $2) to
VMACMWUX reduce the size of the datasets.
Dec 18, 1996
Thanks to Al Holtz, Medco Data Corporation, USA.
===Changes thru 14.295 were included in MXG 14.09 dated Dec 17, 1996===
Change 14.295 If you create type 74 records for devices other than just
RMFINTRV TAPE and DASD, the DEV..... SIO74CNT and AVGRSPTM values
Dec 17, 1996 include those other devices (eg, CTC) counts. Since it
is the intention to have only DASD counts in those fields
by inserting ELSE DELETE; before LENGTH SIO74TAP 4; those
other device records will not be included in RMFINTRV.
Thanks to W. Rathfelder, Taylorix AG, GERMANY.
Change 14.294 For multi-volume non-HSM-backup tape datasets, only the
DAILYDSN last volume's size was included in variable SPACE5, the
Dec 17, 1996 megabytes on non-HSM tape. Replace SPACE5=BLKSIZE*BLKCNT;
with SPACE5=TAPEBYTE;
Thanks to Chuck Hopf, MBNA, USA.
Change 14.293 Support for Windows NT measurement with NTSMF records
ADOCNTSM created by Demand Technology's product. This support is
EXNTxxxx for the beta testers of NTSMF. The fifty-four new MXG
IHDRNTSM datasets (one per "object") are described in ADOCNTSM
IMACNTSM member, and a more extensive discussion of NTSMF records
TYPENTSM will be in the NT Technical Notes section of the next MXG
VMACNTSM Version. Status of testing is also in ADOCNTSM.
Dec 17, 1996
Change 14.292 The very last IMS log record was not processed, because
VMACIMSA the ELSE IF LCODE=07X THEN DO; statement should have been
Dec 17, 1996 IF LCODE=07X THEN DO;
Thanks to Juerg Frei, SAS Switzerland, SWITZERLAND.
Change 14.291 Coupling Facility data added by PTF UW90312 was on a per
VMAC74 structure basis, not per-CF basis, so variable names were
Dec 14, 1996 R744CCOC thru R744CXRL were moved from TYPE74CF to the
TYPE74ST dataset, and MXG input logic was revised.
IBM's "CF Reporting Enhancements to RMF 5.1", WSC Flash
9609 has an excellent discussion of how to use these
important fields for determining if your Coupling Fac.
becomes the bottleneck in your sysplex. The flash also
lists APARs OW11789, OW12415, OW13418, and OW13536 as
required and it lists the additional hardware ECs that
you want to have installed for accurate CF measures.
-R742MSTF was formated $HEX2, input $CHAR1.
-Variables R744FTIM, R744FSQU, R744FCTM, R744FCSQ are
input with PIB8 instead of the (IBM-documented!) RB8.6
informat, and variables R744CDEC,R744CDAC,R744CTCC, and
R744CDTA are input as PIB4 vice RB4.
Thanks to Steve Dodge, Amdahl Corporation, USA.
Attended CMG 96 in San Diego, and Bernie Davidovich's wedding in NY.
Change 14.290 If your SAP Accounting Exit was miscoded, invalid length
IMACICSA type 110 records can be created, causing INPUT STATEMENT
Dec 3, 1996 EXCEEDED error. This change, inserted after STCLEN has
been INPUT, verifies the real data length agrees with the
STCLEN value, eliminating the exposure.
Thanks to Helgund Linck, BASF Compuer Services, GERMANY.
Change 14.289 DF/SMS Rmm EDGS records type V can cause INPUT STATEMENT
VMACEDGS EXCEEDED error because variable length fields & variable
Dec 3, 1996 number of fields at the end of the record were not input
Dec 17, 1996 correctly. Conditional INPUT of the variables MVDSN1,
MVDSNL, MVACCINF and MVDESC with $VARYINGnn. INFORMATS
with associated length variable, and INPUT of variables
MVAUTID1-MVAUTIDC based on MVACCLST was necessary.
Dec 17: Input of MVVOLSEQ must be &PIB.2. vice &PIB.1.
Thanks to Richard Fortenberry, Mitsubishi, USA.
Change 14.288 Negative tape allocation duration can result when system
ASUMTALO clocks are out of synchronization, if the clock delta is
TRNDTALO greater than the duration of the allocation, because only
Dec 3, 1996 the start time of allocation had been adjusted. Now both
the front-end and back-end timestamps are adjusted, and a
note is printed on the log that we are adjusting times
(and by how much).
Thanks to Ruth Whitney, CITICORP, USA.
Change 14.287 The number of DB2 Plans executed is no longer equal to
ANALDB2R the number of observations in DB2ACCT, if DB2 Parallelism
ASUMDB2A is used. Variable DB2PARTY (Parallel Type) identifies a
Dec 3, 1996 "real" plan execution (DB2PARTY='S' or DB2PARTY='O'), but
Dec 19, 1996 observations with DB2PARTY='P' are additional records for
parallel tasks within a plan execution and must not be
counted. In ANALDB2R and ASUMDB2R, NUMPLANS is now
calculated as:
IF QWHSRELN GT 4.0 AND DB2PARTY='P' THEN NUMPLANS=0;
ELSE NUMPLANS=1;
and then NUMPLANS is summed to get total count.
Without this change, you will see very, very large counts
of plans executed and per-plan measures will be very
small, if your DB2 application exploits parallelism.
Dec 19: The original test QWHSRELN GE 4.1 was changed to
QWHSRELN GT 4.0 (because 4.1's value is 4.0999994278!).
Also, this change removed the parallelized transactions
from being counted as NUMPLANS, but sequential parts or
parallelized transactions are still counted in NUMPLANS.
I have to count the DB2PARTY='S' transactions, because
for a non-parallelized transaction, that's all there is!
I hope to review this counting and see if there is a safe
way to only count 'S' obs for non-parallelized trans.
Thanks to Glenn Bowman, Wakefern Food Corporation, USA.
Change 14.286 DB2 Buffer Statistics in the Accounting Detail Report did
ANALDB2R not include buffer pools 1 and 2, so they did not cross-
Dec 3, 1996 foot to the "Total Total" field. Additional corrections
were made and fields on HPOOL/VPOOL usage were added.
Thanks to Terry Dehart, First of America Services, USA.
Change 14.285 Change 14.251 circumvented the error in decoding COLLECT
VMAC102 in DB2 Trace IFCIDs 21 and 44, but the real fix is:
Dec 3, 1996 Change both occurrences of IF I=19 AND J=13 THEN J=20;
to IF I=19 AND J= 7 THEN J=20;
and change the LENGTH of COLLECT back to $ 26.
Thanks to Dr. Alexander Raeder, Karstadt AG, GERMANY.
Thanks to Hartmut Beckmann, Karstadt AG, Germany
Change 14.284 Support for Demand Technology's Stress Test SMF record.
EXTYSTRS This support decodes records into new dataset TYPESTRS,
IMACSTRS but enhancements under development will use your current
TYPESTRS TYPE74 and TYPE74CA statistics to create control cards
VMACSTRS that will drive Stress Test to simulate that current I/O
Dec 3, 1996 configuration.
Thanks to Chuck Hopf, MBNA, USA.
Change 14.283 The HP MeasureWare dataset HPUXGLOB for HP-UX operating
VMACMWUX system had incorrect values for some variables, because
Dec 2, 1996 -the variable PEAKTM should not have been INPUT, and it
must be removed (i.e., the line INPUTing PEAKTM was
deleted by this change, as was the line LABELing PEAKTM
and it was removed from the KEEP= list for HPUXGLOB), and
-the variable NTPACKRT should have been INPUT, between the
INPUT of variables NTOUPKTS and NTCOLPCT (and it was
LABELed as NET*TOTAL*PACKET*RATE, and added to the KEEP=
list for HPUXGLOB).
Thanks to Al Holtz, Medco Data Corporation, USA.
Change 14.282 The archaic ASMVTOC program (which should be replaced by
ASMVTOC using DCOLLECT and TYPEDCOL) is also a pig! For a system
Dec 2, 1996 with 2496 DASD devices, ASMVTOC took 3.25 CPU minutes,
10 million EXCPs and 2.5 elapsed hours, while DCOLLECT
took 2.72 CPU minutes, 86 thousand EXCPs and 23 elapsed
minutes (and got VVDSs, Migration, and Backup data too!).
Note that the MXG 13.13 version of ASMVTOC either failed
during assembly, or assembled but then produced no output
records when executed, so if you still use ASMVTOC, you
will need 14.01 or later (to get Change 14.003).
Thanks to Chuck Hopf, MBNA, USA.
Change 14.281 The T102S221 trace dataset did not keep the low and high
VMAC102 ranges (page range in QW0221PL,PH, index range in KL-KX,
Nov 23, 1996 and KH-KY), which are needed if you wish to verify that
the I/O parallelism partitioning was even, and obs were
only output for the record, not for each segment. The
segment variables were added to the KEEP= list, and the
OUTPUT T102S221; statement was moved to immediatley be
after the @; after the INPUT of QW0221KY.
Thanks to Ted Blank, IBM, USA.
Change 14.280 The BETA93 1.6.5 subtype=3 record is written twice, once
VMACBETA at the start of print, and once at the end of print. As
Nov 23, 1996 there are no resources in the start record, that record
is now deleted. In the SUBTYPE=3 logic, between BETAATTR
and BETABPGE, insert:
@; IF BETAATTR NE 'C5'X THEN DELETE; INPUT
Thanks to Paolo Carloni, AGIP PETROLI S.p.A., ITALY
Change 14.279 HP MeasureWare for AIX variable PROGRAM was added to the
VMACMWAI LENGTH statement for $16 (default of $8 was not enough,
Nov 23, 1996 causing trunctation but no error), and variable SWAPMEM
was added to the KEEP= list for dataset HPAICONF.
Thanks to Lorenzo Wright, NCCI, USA.
Change 14.278 Support for VTAM Session Management Exit SMF record that
EXTYVSME is described in Appendix K of IBM ITSC Red Book "Network
IMACVSME Security Using the VTAM Session Management Exit, pub nr
TYPEVSME GG24-3544-00).
VMACVSME
Nov 23, 1996
Thanks to Kwok Wong, Commonwealth Bank of Australia, AUSTRALIA.
Change 14.277 IMAC6ESS is a user exit that permits decoding of the ESS
IMAC6ESS segment in the type 6 SMF record, and variable ROOM was
VMAC6 used in that commented-out code, but variable ROOM also
Nov 23, 1996 exists in TYPE26J2, so to prevent a possible conflict, I
renamed the ROOM in IMAC6ESS/VMAC6 to ROOM6. This should
cause no compatibility issue, since ROOM was not kept in
TYPE6 unless you tailored IMAC6ESS, and ROOM from TYPE26
was not kept in PDB.JOBS unless you tailored IMACPDB.
Thanks to Helgund Linck, BASF Computer Services GmbH, GERMANY.
Change 14.276 Change 14.040 inadvertently relocated the code to decode
VMACTCP FTPLOCAL and FTPREMOT in the TYPETCPF dataset, causing
Nov 23, 1996 those two varibles to be missing in TYPETCPF. To correct
copy the 16 lines beginning with FTPLOCAL=PUT... ending
with FTPREMOT=COMPRESS... so they are immediately before
the %%INCLUDE SOURCLIB(EXTYTCPF) statement.
Thanks to Helgund Linck, BASF Computer Services GmbH, GERMANY.
===Changes thru 14.275 were included in MXG 14.08A dated Nov 18, 1996===
Change 14.275 Cosmetic changes. Duplicate variable names were removed
IMACAAAA from KEEP= list in VMACHARB and VMACMWAI, IMACAAAA was
VMACHARB updated with new member names that were overlooked, and
VMACMWAI the AS/400 support for Release 3.7 was listed under 14.08
Nov 18, 1996 in the list of Significant changes in 14.08.
Thanks to Freddie Arie, Lone Star Gas, TEXAS.
Change 14.274 SuperIND$FILE SMF record had some character fields off by
VMACSUIN one byte, because the +1 between XFERMODE and INBUFFSZ
Nov 18, 1996 does not belong and was deleted.
Thanks to Chuck Hopf, MBNA, USA.
Change 14.273 MXG 14.05-08 only. INVALID DATA FOR R744FCTM and FCSQ.
VMAC74 Added by Change 14.165, conditionally INPUT by Change
Nov 15, 1996 14.196, the fields were still wrong in MXG 14.07 because
the DSECT shows BL8, like the two preceding fields so
I expected &RB.8.6 fields, but actual data values show
the two fields must be INPUT as &PIB.8.6 instead!
Thanks to Diane Eppestine, Southwestern Bell, USA.
Thanks to Dr. Alexander Raeder, Karstadt AG, GERMANY.
Thanks to Hartmut Beckmann, Karstadt AG, Germany
Change 14.272 SAP Umbrella Transaction's Program and Tranname are kept
IMACICOC in variables OMUMBUSR and OMUMBPTC, while the variables
Nov 14, 1996 PROGRAM and TRANNAME contain the name of the SAP Primary
Program and Transaction. If you want your SAP reports to
show the Umbrella names rather than Primary names, you
can insert these lines in your reporting programs:
IF OMUMBUSR GT ' ' THEN PROGRAM=OMUMBUSR;
IF OMUMBPTC GT ' ' THEN TRANNAME=OMUMBPTC;
You could insert these lines in member IMACICOC to store
the Umbrella names into PROGRAM and TRANNAME in CICSTRAN,
but then you could not go back to determine the Primary
names, if they were ever needed. Thus there was no code
changed in MXG by this Documentation Note Change.
Thanks to Joan Nielsen, PKS Information Services, Inc., USA.
====Changes thru 14.271 were included in MXG 14.08 dated Nov 13, 1996===
Change 14.271 Support for AS/400-OS/400 Release 3.7.0 added many new
VMACQAPM variables to datasets QAPMBUS,QAPMCONF,QAPMJOBS,QAPMMIOP,
Nov 12, 1996 and QAPMRESP. Support for all fields added by 3.6.0 are
also now supported. All 3.7.0 changes were compatible,
except for the QAPMETH dataset, which had ETLFRT expanded
from three to six bytes (and I had misspelled it!). The
3.6.0 partial changes in CHANGE 14.098 were INCOMPATIBLE.
Thanks to Clark Jennings, Reynolds Metals Company, USA.
Change 14.270 Cosmetic. All of the LABEL, FORMAT, INFORMAT, and LENGTH
VMAC110 statements in the Statistics code (Subtype=2) were moved
Nov 12, 1996 together into single statements with alphabetic lists.
Change 14.269 Execution of MXG Software under Unix requires each PDS
IEBUPDTE member become an individual file with suffix "sas", AND
Nov 12, 1996 the filename must be in lower case! The IEBUPDTE.SAS
program creats the individual files, but their names are
in upper case, causing execution under UNIX to fail!
This change inserts MEMBER=LOWCASE(MEMBER); after the
MEMBER=TRIM.... statement to create the members in lower
case. Make sure the output directory is empty before
running the IEBUPDTE.SAS program, as it appears that if
the output file name already exists as an upper case name
that the data is copied but the name is not re-cased!
Thanks to Mike Orlando, Nalco Chemical Company, USA.
Change 14.268 Protection was added to eliminate DIVISION BY ZERO error
VMAC7072 if IOCCOEFF was zero. I had assumed IOCCOEFF would never
Nov 12, 1996 be zero, but if it was, the divide error occurred.
RMFINTRV Also, PGPIOTM is now forced missing for MVS/ESA 5.2 or
Mar 10, 1997 higher. When IO units could be based on either EXCP or
IOTM, both PGPEXCP and PGPIOTM (raw IO EXCP count or raw
IO Connect time) were calculated (even though only one
was ever valid), because IBM did not flag whether you had
specified EXCP or IOTM for your IO Service Units). But
with MVS/ESA 5.2+, IO Service Units can only be based on
EXCP count, so PGPIOTM has no meaning.
Mar 10, 1997: Because PGPIOTM in TYPE72 is missing, the
variables BATIOTM, CICSIOTM, IMSIOTM, TSOIOTM, OTHRIOTM
in dataset RMFINTRV will also be missing.
Change 14.267 This report showed zeros for channel busy in LPAR mode.
ANALPATH Change PNCHANBY=MIN(PNCHANBY,PCHANBY);
Nov 12, 1996 to read PNCHANBY=MAX(PNCHANBY,PCHANBY);
Nov 18, 1996 (Nov 12 text had PCHANBY on left, corrected Nov 18.)
Thanks to Jim Ray, Branch Banking and Trust, USA.
Change 14.266 MXG 14.04-MXG 14.07. The word "NEW" must be deleted from
VMACITRF line 245 to prevent INPUT STATEMENT EXCEEDED ERROR. This
Nov 4, 1996 was introduced by Change 14.128 and incomplete testing.
Thanks to Siegfried Trantes, IDG Informationsvararbeitung, GERMANY.
Change 14.265 Support for HP's MeasureWare for SUN operating system.
EXHPSUTT The same datasets that were created by HP's PCS for SUN
IMACMWUS are created, with one new dataset:
TYPEMWSU Dataset Description
VMACMWSU HPSUTRAN Transaction Tracker Record
Nov 1, 1996
Thanks to Gary Alexander, BMC, USA.
Change 14.264 Support for CA's ENDEVOR SMF record creates two datasets
EXENDVAC Dataset Description
EXENDVSE ENDEAVAC Action Record
FORMATS ENDEAVSE Security Record
IMACENDV The Action record has been validated with actual data,
TYPEENDV but no security records had been created (there were no
VMACENDV security violations!) so that code is untested.
Nov 1, 1996
Thanks to Grace Pergament, Amdahl Corporation, USA.
Thanks to Susan Walters, Michelin Tire Corporation, USA.
Change 14.263 Dataset DCOLAG (Aggregate Group Definitions) has several
VMACDCOL fields incorrect, because the @208 preceding DAGEXPYR
Nov 1, 1996 should have been @209.
Thanks to Gary Miner, Fidelity Investments, USA.
Thanks to Lawrence Jermyn, Fidelity Investments, USA.
Change 14.262 Calculation of DOMDSPCH and ADJTARG must be changed to:
VMACAPAF IF ACTIVE GT 0 THEN DO;
Nov 1, 1996 DOMDSPCH=INTERVAL*DOMDSPCH/ACTIVE;
ADJTARG =INTERVAL*ADJTARG /ACTIVE;
END;
(The variables are divided by INTERVAL earlier in code.)
Thanks to Stephen H. Lothes, Flexlogic, Inc., USA.
Change 14.261 Using the new High Level Assembler PGM=ASMA90 instead of
ASMIMSLG its predecessor Assembler PGM=IEV90, a syntax error that
Nov 1, 1996 was overlooked by IEV90 was encountered. The statement
STATS=SKIP following WRITEMSG IMSM101I needs a comma
(STATS=SKIP,) for the continuation.
Thanks to ???, BBK, SPAIN.
Change 14.261 The statement MONICASP=MONACISP; must be changed to
TYPEMON8 MONICASP=MONACASP; to pick up the correct
Nov 1, 1996 temporary value.
Thanks to Alfred Brunner, COMLAB Gmbh, GERMANY.
Change 14.260 DFSMS/RMM SMF records caused INPUT STATEMENT EXCEEDED.
VMACEDGS In the EDGATYPE='O' code, the test IF MOCFLG EQ '08'X ...
Nov 1, 1996 must be replaced with IF MORTYPE EQ '000000000000'X ...
and IF MOVOLNO GT 0 AND MOCFLG NE '08'X THEN DO ...
must be replaced with only IF MOVOLNO GT 0 THEN DO ...
In the EDGATYPE='P' logic, the statement
IF MOVOLNO GT 0 THEN DO _I_=1 TO MOVOLNO; must be
IF MPVOLNO GT 0 THEN DO _I_=1 TO MPVOLNO; must be
Thanks to Siegfried Trantes, IDG Informationsvararbeitung, GERMANY.
Change 14.259 Support for Omegamon for VTAM V200 was not complete; an
VMACOMVT extra four bytes added to IRNUM=13 segment was overlooked
Oct 30, 1996 in Change 14.268. After input of OM13GT, insert:
OM13DT &PIB.4. /*NCP*INTERVAL*DELTA*TIME*/
and add OM13DT to KEEP= list.
Thanks to Neil McMenemy, Royal Bank of Scotland, SCOTLAND.
Change 14.258 Goal Mode variable RPTCLASS was added to PDB.JOBS. The
IMACPDB variable name was added to the _PDB30_4 macro, and to
Oct 30, 1996 the ID statement in macro _PDBSUMS (just like SRVCLASS).
Thanks to Steve Colio, CIGNA, USA.
Change 14.257 The 22 new Shared Paging variables in TYPE71 starting
VMAC71 with SHPBINAU and thru SHPGLOAV need to be INPUT as
Oct 25, 1996 &RB.4. instead of &PIB.4.
Thanks to Don Deese, Computer Management Sciences, USA.
Change 14.256 Support for APAR OW22209 which (compatibly) adds fourbyte
VMAC21 counters for bytes read and bytes written, replacing the
Oct 24, 1996 two byte counters that could overflow! Also OW25262.
Change 14.255 Formats MGBYTES and MGBYTRT now format Petabytes, because
FORMATS I finally found (in an IEEE Computer Society article)
Oct 24, 1996 that 1000 Tera is 1 Peta!
Change 14.254 TYPE72GO variables R723CSRS, R723CSPA, R723CSPE are still
VMAC7072 wrong! Their informats are &RB.8.6, &RB.8., and &RB.8.
Oct 24, 1996 respectively.
Thanks to Bruce Widlund, Merrill Consultants, USA.
Change 14.253 The JCL example showed //SYSID instead of //SYSIN.
ANALDB2C While minor, its still worth fixing, since a non-expert
Oct 23, 1996 with JCL might not recognize the misspelling.
Thanks to David Middlebrook, National Exchange of Police, AUSTRALIA.
Change 14.252 An invalid RACF segment for RACFTYPE=03 caused STOPOVER.
VMAC80A Although IBM documents a single length of 1 byte, the
Oct 23, 1996 segment had 151 bytes! To protect, insert:
SKIP=RACFDLN-1;
IF SKIP GT 0 THEN INPUT +SKIP @;
just before the END; that ends the WHEN (3) DO; clause.
Thanks to Silva Viviani. Fondo Commune D.C. Rurali Trentine, ITALY.
Change 14.251 INVALID SECOND ARGUMENT TO FUNCTION SUBSTR in DB2 102 due
VMAC102 to incorrect length statement for variable COLLECT, which
Oct 23, 1996 must be $28 instead of $26.
Thanks to Dr. Alexander Raeder, Karstadt, AG, Germany
Thanks to Hartmut Beckmann, Karstadt, AG, Germany
Change 14.250 Cosmetic. TMON for CICS variables CPUTCBTM, UNKNCPTM and
TYPETMON CPUTM were not formatted as TIME12.2, but now are.
Oct 19, 1996
Thanks to Chris Weston, SAS Institute Cary, USA.
Change 14.249 Support for HP's Measureware for AIX has been written and
IMACMWAI tested. The same datasets that were created by HP's PCS
TYPEMWAI for AIX are created, although some variables were deleted
VMACMWAI and some new variables are created.
Oct 17, 1996
Thanks to Lorenzo Wright, NCCI, USA.
Change 14.248 Support for Applied Software's SUPER IND$FILE product's
VMACSUIN SMF record, which creates dataset SUPERIND with stats on
Oct 17, 1996 file trasnfer with that utility program under TSO.
Thanks to George Briscoe, MBNA, USA.
Change 14.247 Support for Oracle 7.0.16 and 7.2.3 is in MXG 14.02 and
VMACORAC later, as there was no change in the format of the SMF
Oct 17, 1996 record created by those releases.
Thanks to Paul Hassett, U.S. Department of Transporation, USA.
Change 14.246 AS/400 variable GDES4 (storage size) was increased by IBM
VMACQAPM causing truncation of the size of installed storage. The
Oct 16, 1996 &NUM.7. after GDES4 was changed to &NUM.10. to correct.
Thanks to Ed Shigo, Nabisco, USA.
Change 14.245 Testing with intentionally duplicated SMF data uncovered
BUILDPDB cases where the PROC SORT NODUP did not remove duplicate
BUILDPD3 observations, because the BY list was underspecified.
BUILD002 For TYPE30MU, add PRODOWNR PRODNAME PRODQUAL PRODVERS to
BUILD003 its BY list.
MONTHBLD For TYPE74CA, add DEVN SMFTIME to its BY list.
WEEKBLD For TYPE74CF, add R744FNAM SMFTIME to its BY list.
Oct 16, 1996 For TYPE74ST, add R744SNAM SMFTIME to its BY list.
For TYPE77, add QNAME RNAME SMFTIME to its BY list.
Thanks to Chuck Hopf, MBNA, USA.
Change 14.244 Change 12.179 was not applied to VMACIMSA, used by the
VMACIMSA ASMIMSLG processing, causing SAP variables SAPTIMTR,
Oct 15, 1996 SAPCPUT, and SAPELTI to be incorrect.
Thanks to Markus Joos, SAS Germany, GERMANY.
Change 14.243 Support for RACF 2.1 IRRDBU00 unload utility has now been
VMACRACF verified for most records. The only change was that the
Oct 11, 1996 variable TIMEOUT in RACF0230 should be INPUT as TIME5.,
instead of the previous ZDB5. input.
Thanks to Peter Cannone, The Great Atlantic & Pacific Tea Co., USA.
Change 14.242 A truncated catalog cell=04 record caused INPUT STATEMENT
VMAC6156 EXCEEDED RECORD LENGTH. The cell has VOLHYKLN=2, but
Oct 10, 1996 that is at the end of the record, and there was no high
key following the key length. Protection added so that
MXG checks to see there is still data in the record prior
to INPUT of VOLHIKY.
Thanks to Raff X. Rushton, Great Western, USA.
Change 14.241 Support for RACFEVNT=27 (GENERAL AUDIT) creates the new
EXTY8027 TYPE8027 dataset. RACFTYPE=36 is now decoded in SETROPS
IMAC80A (RACFEVNT=24) records.
VMAC80A
Oct 10, 1996
Thanks to Robert Miles Standish, Dean Witter Trust Company, USA.
Change 14.240 IPAC SMF records cause INVALID ARGUMENT TO FUNCTION MDY
VMACIPAC (and print hex dump with "RDS " in bytes 15-18) because
Oct 9, 1996 the SDATE and EDATE are julian dates, not MMDDYY as the
vendor documented.
Thanks to Shaheen Pervais, Trans Union, USA.
Change 14.239 The TAILORNG= JCL parameter added by Change 14.140 is bad
MXGSAS and in the sample MXGSAS JCL Procedureit must be:
Oct 7, 1996 TAILORNG='*.NULLPDS,VOL=REF=*.NULLPDS',
(like the LOAD= and SASAUTO= symbolic parameters).
With the delivered TAILORNG=NULLFILE, a JCL error occurs
(because NULLFILE is a sequential file, not a PDS).
Thanks to Mr. Harnischmacher, TEZ Test und Entwicklungszentrum, GER.
Change 14.238 Archaic IDMS 10.2.1 SMF records caused STOPOVER because
VMACIDMS the subtype 2 record is 4 bytes shorter, and the subtype
Oct 1, 1996 6 is one byte shorter than the code expected.
Oct 8, 1996 At the end of the INPUT for PMHRTYPE=2, change the +12 to
Oct 16, 1996 +8, and change SKIP=SKIP-108; to SKIP=SKIP-104;
I suspect a CA PTF changed the record, because I am sure
this code ran against 10.2.1 records in past years, but
the fix protects both 10.2.1 and 12.01 records.
-In the PMHRTYPE=6 code, replace the line with +1
after the line inputting JRLFILE with:
@; IF SMFHVER GE '1201' THEN DO;
INPUT +1 @; SKIP=SKIP-1;
END;
and change SKIP=SKIP-105; to SKIP=SKIP-104;
-In the PMHRTYPE=18 code, change code now reading:
DBKPGGRP &PIB.2.
+2
DBKKYFMT &PIB.4.
DBKLTYPE &PIB.4.
@;
SKIP=SKIP-14;
IF DBKOWNER='80'X THEN DO;
to instead look like this:
DBKPGGRP &PIB.2.
@;
SKIP=SKIP-4;
IF SMFHVER GE '1201' THEN DO;
INPUT +2
@;
SKIP=SKIP-2;
END;
INPUT DBKKYFMT &PIB.4.
DBKLTYPE &PIB.4.
@;
SKIP=SKIP-8;
IF DBKOWNER='80'X THEN DO;
Thanks to Paul Hasset, U.S. Department of Transportation, USA.
Change 14.237 Candle's EPILOG for MVS records with SM180SUB='RCCH' are
VMACEPMV not the expected record and are deleted. The test for
Sep 30, 1996 'RSRC' was expanded to OR SM180SUB='RCCH' THEN DELETE;
Also, the following INPUT statement is now conditionally
executed as IF LENGTH-COL+1 GE 152 THEN INPUT ....
Thanks to Dan Almagro, Automobile Club of Southern California, USA.
Change 14.236 Support for new RMF type 74 subtype 100 record, called
EXTY74LK the IRLM 'long lock' package, added by APAR OW20579 and
IMAC74 others, that measures held time for IRLM Structure locks
VMAC74 in the Coupling Facility. This APAR has been in FIXTEST
Sep 28, 1996 for quite a while but has been distributed to some
customers, and there is an RMF User report that displays
locks held/waited. New dataset TYPE74LK contains one
observation for each IRLM lock structure name. This code
has not been data-tested as yet.
Change 14.235 Support for several new fields (mostly SMS-related, like
VMXGHSM Data, Storage, and Management Classes) added to the HSM
Sep 28, 1996 MCC record. Additionally the SC,DC, and MC class names
Oct 9, 1996 in both MCC and MCD records are now input only if their
length is non-zero; some zero-length records had hex
zeroes instead of blanks for these name fields. Also, the
INFILE statements needed LENGTH=LENGTH COL=COL added.
Thanks to Terry Duchow, U.S. Postal Service, USA.
Change 14.234 PRO/SMS support in Change 14.207 was incorrect; test data
EXPROSRE for subtype 1 has now been verified, but subtype 2 record
IMACPROS documentation disagrees with actual content of test data.
VMACPROS There are now two datasets created:
Sep 28, 1996 Dataset Subtype Description
Oct 16, 1996 PROSMS 1 Message
Nov 1, 1996 PRORECOV 2 Recovery Performed
Both datasets have been tested with actual data.
Thanks to Warren Hayward, TJX Companies, USA.
Change 14.233 TYPE89 usage data variable MULCURD, for Batch Pipes, was
VMAC89 incorrectly input. The input format of MULCURD is set by
Sep 26, 1996 the value of MULTCURT, but MXG had reversed the INPUT for
MULTCURT 2 and 3. The correct statements should be:
IF MULCURT EQ 1 THEN INPUT MULCURD &RB.8.2 @;
ELSE IF MULCURT EQ 2 THEN INPUT MULCURD &PIB.8. @;
ELSE IF MULCURT EQ 3 THEN INPUT MULCURD &RB.8. @;
The choice of format for MULCURD is set by the product's
FUNCTIONDATA request in its macro IFAUSAGE; previous data
records contained MULCURT=1, which correctly read MULCURD
but BatchPipes sets MULCURT=3, exposing the error.
Thanks to Michael Oujesky, MBNA, USA.
Change 14.232 HSM warning "FSRTVOLS CAN CONTAIN ONLY 30 BYTES" is writ
VMACHSM in error. The two lines preceding the PUT of that
Sep 25, 1996 message, now reading IF LENGTH(FSRTVOLS) GT 23 THEN ...
must be changed to: IF LENGTH(FSRTVOLS) GT 30 THEN ...
Thanks to Robert Miles Standish, Dean Witter Trust Company, USA.
Change 14.231 Change 14.167 was implemented and printed incorrectly.
DIFFDB2 The four lines after that change that start with:
Sep 25, 1996 IF QWHSISEQ GE 1 AND PREVSSID .... must be changed to:
IF SEQCHECK GE 1 AND PREVSSID ....
One source of the skipped sequence numbers (QWHSISEQ) is
CA's INSIGHT monitor for DB2. When INSIGHT is started at
DB2 startup, several ISEQs are skipped, and several ISEQs
are skipped at shutdown. CA is investigating.
Thanks to Tom Parker, Hogan Systems, USA.
Change 14.230 Huron dataset HURN47 had zero observations if there were
VMACHURN no external resource segments at the end of the record.
Sep 23, 1996 After the END; statement that ends DO I=1 TO HU47XSNO;
insert:
IF HU47XSNO EQ 0 THEN DO;
%%INCLUDE SOURCLIB(EXHRN47);
END;
Thanks to Mark Totleben, Farm Bureau Insurance, USA.
Change 14.229 Support for Interlink's Harbor 4.1 SMF record creates
EXHARARC nine datasets for that backup product:
EXHARBKP Subtype Dataset Description
EXHARCON 01 HARBBKUP Harbor Backup Request Info
EXHARDIS 02 HARBREST Harbor Restore Request Info
EXHARFIL 03 HARBARCH Harbor Archive Request Info
EXHARMIG 04 HARBRETR Harbor Retrieve Request Info
EXHARREC 05 HARBDIST Harbor Distribution Info
EXHARRES 06 HARBMIGR Harbor Migration Info
EXHARRET 07 HARBRECA Harbor Recall Info
FORMATS 08 HARBCONS Harbor Consolidation Info
IMACHARB 09 HARBFILE Harbor File Pickup st
TYPEHARB The first two subtypes have been validated with test data.
VMACHARB
Thanks to Paul Hassett, U.S. Department of Transportation, USA.
Change 14.228 Support for EOS (Change 14.143) was not correct; the Audit
FORMATS records were INCOMPATIBLY changed, causing MXG to trash
VMACWSF the WSFAUDIT dataset (but there was no execution error,
Sep 22, 1996 and the other datasets were validly created). There were
additional compatible changes made to EOS (aka WSF2):
New values for format MGWSFAC
New Audit variables in dataset WSFAUDIT:
AUDCFO - Form Used to Create
AUDCUSR - Report Owned By
AUDCTIM - Report Capture Datetimestamp.
New event variables in dataset WSFEVTSC:
ACCIPAD - IP address
ACCLUTY2 - LU Type (VTAM or TCP/IP)
ACCRESP5 - Responses LE 30 seconds
ACCRESP6 - Responses LE 2 minutes
ACCRESP7 - Responses LE 5 minutes
ACCRESP8 - Responses GT 5 minutes
Thanks to Judy Arroyo, Summit Bank, USA.
Change 14.227 Variable R742PSTA in dataset TYPE74PA is now decoded to
FORMATS describe path status, based on APAR OW22735, with new MXG
VMAC74 format $MG074ST.
Sep 20, 1996
Thanks to Don Deese, Computer Management Sciences, USA.
Change 14.226 DB2 Group Buffer Pool dataset DB2GBPST repeats the first
VMACDB2 buffer pool's data because the pointer was not moved.
Sep 18, 1996 Insert @OFFQBGL @; before the DO _I_=1 TO NRQBGL;
statement, and then remove the @OFFQBGL from the INPUT
statement after that DO statement.
Thanks to Bertolotti Emmanno, Banca Commerciale Italiano, ITALY
Thanks to Burani Daniela, Banca Commerciale Italiano, ITALY
Change 14.225 CICS/ESA 3.3, with optional ONC RPC feature creates a 5th
VMAC110 TCB in SMF 110 Statistics STID=57 records that was not
Sep 18, 1996 expected in MXG, causing MXG to print "UNEXPECTED (NEW)
Oct 9, 1996 DATA WAS FOUND" message on the SAS log. The APAR that
made the change was PN63215, closed in 1994, so it seems
that few sites have the ONC RPC feature on CICS 3.3.
MXG supports the 5th TCB for CICS 4.1 (and the 6th for
CICS 5.1), so only the 3.3 logic had to be corrected.
Oct 9: DSGNTCB is supposed to be the number of TCBs, but
in some CICS 3.3 records, it is zero, so the logic was
revised.
Thanks to Siegfried Trantes, IDG, GERMANY.
Change 14.224 Labels for CONTROL-T variables DENSITY, RECFM, TRTCH, and
VMACCTLT VDENSITY were corrected.
Sep 16, 1996
Thanks to Paul Hassett, U.S. Department of Transportation, USA.
Change 14.223 The INFILE statements for TANDCTLR and TANDLINE must be
VMACTAND LRECL=86 and LRECL=128 respectively. While comments had
Sep 12, 1996 correct values, both INFILE statements had LRECL=342.
Thanks to Alan Phelan, Allied Irish Bank, IRELAND.
Change 14.222 ASM fails; last minute changes were not tested. Find
ASMDALO Find 'R12,R11' and remove the blank after MXGDALO
Sep 12, 1996 Exclude ALL, Find 71,71 'X' ALL and in those four lines
move the X in column 71 to column 72 (so the Assembler
will recognize them as continuations).
Thanks to Chuck Hopf, MBNA, USA.
====Changes thru 14.221 were included in MXG 14.07 dated Sep 11, 1996===
Change 14.221 Support for IMS 5.1 Fast Path records using TYPEIMS7 to
VMACIMS read IMSLOG was added. The ASMIMSLG processing member
Sep 10, 1996 VMACIMSA already supported the Fast Path changes; this is
the same code, moved into the VMAC used by TYPEIMS7.
Thanks to MH, Allied Irish Bank, IRELAND.
Change 14.220 CICS Exclude logic for CICS 4.1 had a missing semicolon
IMACEXCL (the line BASETIME=...) and the IF SMFPSRVR GE 41.1 THEN
Sep 10, 1996 must be IF 33.0 LT SMFPSRVR LE 41.0 THEN ...
Thanks to Pat Quinnette, Principal Mutual Life Insurance, USA.
Change 14.218 Support for SNMP IFENTRY tables from TRENDSNMP product
EXTRSIFE from Desktalk, which polls SNMP agents and builds SYBASE
IMACTRSN tables, either under UNIX or WINDOWS-NT. MXG can execute
TYPETRSN either on an ASCII platform that connects to the SYBASE
VMACTRSN system and uses PROC ACCESS to directly convert the data
Sep 10, 1996 into SAS datasets, or instead, you can use the SYBASE BCP
utility to create an ASCII flat file that MXG can read on
the PC/Workstation, or that ASCII file can be shipped to
MVS and processed there. Macro _SIFEN uses PROC ACCESS,
Macro _TIFEN uses INFILE/INPUT to read BCP data. This is
the preliminary implementation and has been tested, and
will read either the Rate table or the History Table.
This code does no date/time selection; you get all of the
data in the SYBASE table, so you will need to select the
desired data. Future enhancements to provide selection
of "just yesterday's" data are planned, as are support
for additional SNMP tables and RMON data. Benchmarks on
my 64MB 166MHz Pentium with Windows NT 3.51 reading 20MB
SYBASE table that contained 6 days hourly data from 1000
devices (66,816 rows):
PROC ACCESS convert SYBASE to SAS: 265 seconds
or
BCP dump SYBASE to ASCII file 471 seconds
INFILE/INPUT read BCP dump 21 seconds
Thanks to Bernie Davidovich, Predictive Systems, USA.
Change 14.217 DB2 4.1 variables QTGA and QBGA were trashed, because the
VMACDB2 offsets were input from the wrong location. After test
Sep 10, 1996 IF QWHSNSDA GE 11 THEN ... the INPUTs with @81,85,87,89,
93, and 95, should be 97,101,103,105,109,111.
Thanks to Bertolotti Emmanno, Banca Commerciale Italiano, ITALY
Thanks to Burani Daniela, Banca Commerciale Italiano, ITALY
Change 14.216 Three new utilities are now available for Beta testing:
UTILCONT UTILCONT produces a PROC CONTENTS-like output with the
UTILFATD size (MegaBytes and observations) of each data
UTILSIZE set in the library pointed to by the PDB DDna.
Sep 10, 1996 UTILFATD reads the directory of all of your FAT disks
connected to this PC and calculates how much
space the data would take on hard disks of
varying cluster size (512 to 32K).
UTILSIZE reads an MVS PDS to calculate how much space
is needed to put that PDB library on a FAT
disk on your PC for all valid Cluster Sizes.
Large Cluster sizes may waste large amounts of
space when you have many little files. This
is useful to predict how much free space you
will need on your PC to store the MXG source
library.
Thanks to Chuck Hopf, MBNA, USA.
Change 14.215 This is the Beta Version of the new MXG DASD Allocation
ASMDALO Monitor, which creates an SMF record for each of these
EXDALOAL DADSM events:
EXDALOEX DALOALOC ALLOCATE
EXDALOPA DALOSCRA SCRATCH
EXDALOPP DALORENA RENAME
EXDALORE DALOEXTN EXTEND
EXDALOSC DALOPART PARTIAL RELEASE
EXDALOVS DALOPPRL PARTREL PARTIAL RELEASE
IMACDALO DALOVSAM VSAM EXTEND WITHOUT A DEB
TYPEDALO and MXGDALO can be enabled for selected devices and/or
VMACDALO selected datasets. This monitor can be used to identify
Sep 9, 1996 jobs that are living on DASD extents (so you can increase
their primary allocation to avoid exposure to B37/E37
ABENDS. This monitor can be used to track (and charge?)
usage of temporary DASD space. Other uses are expected.
Read the comments in ASMDALO before you proceed.
Change 14.214 Variable SERVUNIT (total service units) was stored in 4
BUILDPDB bytes, whick keeps only 7 significant digits; a large
BUILDPD3 value in SERVUNIT (714 million units) was truncated by
BUIL3005 1000 units because 5 bytes storage is required to exactly
BUILD005 represent a numeric field that was input from four binary
VMAC30 bytes. SERVUNIT is now stored in 5 bytes. But the real
VMAC434 error here