COPYRIGHT (C) 1984-2005 MERRILL CONSULTANTS DALLAS TEXAS USA
Newsletter THIRTY ONE
/* COPYRIGHT (C) 1984-2005 MERRILL CONSULTANTS, DALLAS, TEXAS */
****************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 MXG
Version and Newsletter shipment sent in First Quarter, and a Summer
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 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, 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.
PetaByte is 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 not included in MXG 14.14 because Landmark was unable
to provide documentation in time. The new product is a complete
rewrite and no longer modifies the kernel, so some of the unique
data elements in the earlier product have been lost. If you are
interested in this support, send a request and the enhancement
will be sent to you when available.
b. Landmark's The Monitor for CICS/ESA Version 2 will be released in
spring, but the documentation and test data had not yet arrived.
c. ASMTAPES, ML12, is still in final testing (see Change 14.322). Al
sites using ASMTAPES with MVS 5.2.2 or OS/390 should install ML11
now, and request ML12 when it is available (soon).
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!
II. MXG Technical Notes.
1. MXGTMNT's Tape Allocation Monitor logic at MAINTLEV 9 (MXG 14.05
and later) once put one MVS system in an unrecoverable Spin Loop,
requiring the site to IPL. The error is caused by the SRB routine
in the Allocation side of the monitor, so starting MXGTMNT with
ALLOC=NO
to suppress the allocation monitor while continuing to write SMF
records for Tape Mounts was recommended until MAINTLEV 11; that
Mount monitor does not issue SRBs. MAINTLEV 10 (MXG 14.08) did
not correct the exposure, but this problem has only been seen by
one site, which is massive and has horrendous tape activity, and
appears to have additional glitches (pseudo stalls?) that last for
tens of seconds that prevents us for getting the response to our
SRB. The permanent correction is contained in MAINTLEV 11 (MXG
14.11) which replaced the SRB routine with cross memory services.
ALL SITES SHOULD NOW RE-INSTALL MXGTMNT USING MXG 14.14 ASMTAPES!
2. If MONTHBLD fails due to NOTSORTED error, because you have skipped
major MXG versions (like jumping from 11.11 to 14.07), the cause
is that some of the weekly PDBs had one sort order, while the new
weekly PDBs have a different sort order. To get thru the night to
build the Monthly PDB, you can circumvent the sort order
Note originally read:
you can comment out the BY _BYLIST; statement
but that was inside the definition of MACRO _MNTHBLD, and
could not be selectively applied without multiple MONTHBLDs.
Revised note, Feb 10, 1998:
You can circumvent by changing the list of sort variables in the
line: MACRO _BYLIST APPLID OPERATOR ... % _MNTHBLD
to contain only the first By variable:
MACRO _BYLIST APPLID % _MNTHBLD
The _BYLIST macro definition to change is the one after the _DSET
macro definition for the dataset causing the NOTSORTED problem.
the monthly PDB won't be sorted, but at least the monthly PDB will
be valid. If one of your report programs now fails because it
expected the data set to be sorted, you can insert a PROC SORT in
that report program for this month's report. MXG build's PDB
datasets in sort order so that you can avoid SORTs in your report
programs, but the removal of the BY statement is the easiest way
to complete the creation of the Monthly PDB, and then individually
deal with any repercussions in your report programs.
III. MVS Technical Notes.
1. APAR OW15356 now writes type 21 SMF records (Tape Volume Dismount)
for tape devices with 4-digit (hex) UCB addresses. Without the APAR
type 21 are only written for 3-digit addresses.
2. APAR OW10686 corrects errors in counting I/Os in type 30 records if
more than 8,000 DDs exist in the step record.
3. A site still running MVS/XA found type 30 subtype 2, 3, & 4 records
had hex zeroes for variables JOB,JESNR,READTIME,TYPETASK, JCTJOBID.
APAR OY38538 (closed, 1991) describes the error introduced by APAR
UY56157 (DDCONS, 1990!) and provides a Local Zap to fix the problem.
4. Increased Logical Swaps becoming Physical Swaps with Goal Mode has
been observed by MVS/ESA sites moving from Compatibility to WLM; IBM
now reports APARs OW11423 and OW20486 tune the WLM algorithms to
correct the problems. More details are in the APAR text.
5. The new type 74 subtype 5 Cache record (TYPE74CA) may have logically
duplicated data, if you have multiple systems sharing 3990 control
units, because each MVS system writes a record with its perspective
of 3990 usage. Previously, you typically ran the predecessor Cache
RMF Reporter on only one system, which produced only one set of data
for 3990 usage. These logically duplicate records can take up quite
a bit of DASD space, so you may need to use the EXTY74CA data set
exit member to control the OUTPUT of observations in TYPE74CA so as
to only keep data from the one system that is always there and has
access to all of your 3990 control units!
6. APAR OW23225 reports EXCP counts in TYPE30 for VSAM RLS datasets
are zero. PTF is in testing.
7. Boole & Babbage CMF 5.2 will create type 72 records with STARTIME
one second later than true STARTIME, if you have installed their
APAR BAM4508. The correction to that APAR is now APAR BAM5929.
8. Nov 23, 1996. APAR OW23872 for 3590 Model A00 Control Unit corrects
the tape drive serial number in HDR2/EOF2/EOV2 Tape Labels on tapes
created on 3590s behind those CUs, and corrects the value in the
TYPE21 dataset (variable TAPCUSER, which contains an encoded value
containing a product identifier, a unique drive serial number, plus
information on the manufacturer and plant of manufacture of the
tape drive on which the tape was created).
9. Nov 23, 1996. APAR OW23814 documents errors in DCOLLECT type A
(DCOLCLUS dataset) variable DCAFLAG1 with incorrect bits set for
KSDS datasets.
10. Nov 23, 1996. As discussed in NEWSLETTER THIRTY MVS Technical Note,
Media Manager EXCP counts for DB2 VSAM are recorded in type 30 EXCP
buckets, but that note should also point out that those EXCP counts
are also recorded in the type 72 records for the PERFGRP/SRVCLASS of
the DBM1 ASID. Also, to get these counts, you must specify
SMFIO=YES on the MMSRV CONNECT request, and be at DFSMS 1.1 or
above, and at DB2 4.1, or if at DB2 3, you need PTF PN76648.
Support in MXG is automatic.
11. Dec 18, 1996. TCP/IP SMF records with invalid data for FTPCLIENT
records were corrected by APAR PN96013 PTF UN92936. Jan 11, 1997,
see also APAR PN91783 for LOGN/LOGF record errors using USSMSG10
or the Telnet Solicitor panel.
12. Dec 18, 1996. Type 6 records with non-matching READTIME values were
found when SYSOUT was sent from one NJE node to another NJE node and
then processed by CA-DISPATCH product; the type 6 record created by
CA-DISPATCH has a semi-current time value, but it is not the actual
READTIME of the other records for the job, but CA's error is fixed
by CA-DISPATCH maintenance fix T7H0121.
13. Jan 29, 1997. Slow TSO Logon duration due to massive STEPLIBs.
Walt Kraslawski of the Library of Congress writes:
Thanks for your help with our TSO response problem. As you
requested, here is a recap of the problem and solution.
Until recently, the Library of Congress has been almost exclusively
a ROSCOE shop, with only a handful of low priority TSO users. Long
TSO response times were never an issue. However, with the addition
of a number of new applications, each requiring administration and
usage via ISPF, response suddenly became a high-to-critical issue.
A typical LOGON to "READY" would take 35 seconds: 10 seconds to "NO
Broadcast Messages", 15 seconds to start the "%LOGIN," and 10
seconds to complete the "%LOGIN," (which included only a few trivial
commands). From there it would take another 45-60 seconds to get
into ISPF! Analysis of SMF TYPE30_4 records for a LOGON-LOGOFF
session showed only 3 to 5 seconds from READTIME to LOADTIME (which
was thought to be the time of "READY"). Looking inside the
SELAPSTM, the DSPDLYTM showed 30 seconds, and the only other
significant value was IOTMNODD with 11 seconds I/O time for catalog,
linklist, and JES2. So SMF showed that the time to program load was
small, and that most of the delay to get "READY" occurred after the
TSO program IKJEFT01 was loaded, with lots of linklist I/O.
The default TSO LOGON proc is very large, with 135 cataloged
datasets covering almost every application on site. These included
23 load libraries in the STEPLIB, with the rest mostly being ISPF
libraries, panels, tables, etc. A simple test showed that deletion
of the entire STEPLIB concatenation dropped the time to get into
ISPF to 7 seconds instead of 90! This revealed that every command,
internal or otherwise, was being searched in the STEPLIB
concatenation, and then going to SYS1.CMDLIB in the LINKLIST only
after being not-found in the STEPLIB. The desired solution was
therefore to keep the function and purpose of the STEPLIB without
the overhead.
We created a new CSVLLA00 PARMLIB member with "LIBRARIES(...)"
listing all of the load libraries in the TSO LOGON STEPLIB, followed
by "FREEZE(...)" listing all the load libraries again. The LLA
address space is started at IPL without reference to this list,
because we did not want to place every application library in the
master catalog. After VTAM comes up, an automatic start command is
issued to "MODIFY LLA,UPDATE=00" to bring the TSO list into the LLA.
The result is that TSO LOGON response time to get into ISPF is only
7 seconds, just as if there were no STEPLIB concatenation. The only
down side is that we must do an LLA refresh whenever a load library
in the list is changed. We will see whether this becomes an issue.
In the meantime, we are set up to do an automatic refresh every
twelve hours.
14. Feb 24, 1997. Type 42 records were enhanced by APAR OW20866 (DCME
enhancements for DFSMS 1.3.0 and above) to improve I/O statistics.
New TYPE42VT (subtype 5) dataset now measures I/O activity to the
VTOC, VTOC index, and VVDS at the volume level. Multi-volume or
striped datasets now have separate observations in TYPE42DS (subtype
6) for each volume. TYPE42DS also now captures I/O to JOBLIB and
STEPLIB datasets, and block counts and block sizes are reportedly
now corrected. The new I/O delay statistics S42AMSRR and S42AMSWR
contains the total I/O delay (time between wait and post). Unlike
total I/O time, the sum of all data set delays are additive and
cannot sum to greater than the elapsed time of the job, making them
very useful for job performance analysis. MXG already supported the
changes; this PTF populates the fields that were coded earlier.
Revised: May 27, 1997. See Change 15.105.
IV. DB2 Technical Notes.
1. Nov 25, 1996. Now that DB2 has more than four buffer pools, where
are the activity counts? MXG Change 12.033 described how I chose to
support the new buffer pools that were added by DB2 Version 3.1, but
the text of that change was not easily read. The implementation:
In the DB2ACCT and DB2STATS datasets, there are still only four sets
of Buffer Pool variables (QBnCaaa in DB2ACCT, QBnTaaa in DB2STATS,
where n=1, 2, 3, or 4) but now they contain summarized counts:
QB1 variables - Only Buffer Pool BP0 (4K)
QB2 variables - Only Buffer Pool BP1 (4K)
QB3 variables - Buffer Pools sum BP2 thru BP49 (all other 4K)
QB4 variables - Buffer Pools sum BP80 thru BP89 (all 32K)
For activity for a specific buffer pool, two other datasets exist:
DB2ACCTB - One obs for each Buffer Pool used by each Plan.
DB2STATB - One obs for each Buffer Pool used during the interval.
However, by default, there will be zero observations in DB2ACCTB
until you remove the comment block in member EXDB2ACB, the exit
member for DB2ACCTB. I chose to comment out that OUTPUT statement,
because DB2ACCTB could be large (one obs for each buffer pool that
was used by each plan, although the length is only 294 bytes) so
why waste space until you need the details! DB2STATB will always
have observations, since it has only one obs for each buffer pool
that was used during each interval.
2. Dec 3, 1996. The number of observations in DB2ACCT no longer counts
the number of plan executions, if DB2 Parallelism is used. DB2ACCT
observations with DB2PARTY='P' are parallel tasks within a single
plan execution, and should not be counted in NUMPLANS. See member
ANALDB2P (for an example of DB2 parallelism) and Change 14.287.
V. IMS Technical Notes.
1. Jan 28, 1997. Boole & Babbage IMF had negative values for RESPTM
(END time was earlier than both ARRV and STRT) that is now fixed
by their patch number BPI6881.
2. Feb 14, 1997. Boole & Babbage IMF caused a significant increase in
CPU usage (measured in RMFINTRV and SMFINTRV) on the order of 20%
moving from MVS 5.1 to MVS 5.2.2 with IMS 4.1. Boole has a user
mod (UMODIMS in BOOL9601.BBSAMP) that disables IMS/DC and IMF/EC
data collection to reduce overhead, but that mod also causes DB2
calls and DB2 CPU time to be not recorded. It is alleged that IBM
is working with Boole for a better solution.
Jul 28, 1997 update: Boole PTFs BPI7166 and BPI7167 corrected the
problem. See IMS Technical Note in Newsletter THIRY-TWO.
VI. SAS Technical Notes.
1. SAS USER ABEND 318 may result with SAS 6.08 at TS425 when a SAS
data library is allocated to a device with 4-digit UCB address.
A new problem is currently being opened.
2. SAS usage note 8243 acknowledges that SAS data libraries cannot use
"data striping" or "hardware compression", because both of those
technologies do not support the EXCP access method that SAS uses for
SAS data libraries on MVS systems. If you attempt to write a SAS
data library to one of these "Extended Format" (Extended Sequential)
datasets, you will be greeted with an ABEND 213-B8 (as was noted in
Newsletter TWENTY-EIGHT, but only under "hardware compression").
Added 12Mar97: Hardware compression can be used if the SAS Data
Library is in "Tape Engine" format. See Newsletter THIRTY-TWO.
3. IBM APAR OW14045 causes SYNCSORT to ABEND with 0C4 and HOST SORT
CANNOT BE USED message on SAS log. SYNCSORT Early Warning EW4874-2
contains the ZAP that will correct the error. The IBM APAR applies
to MVS/ESA 4.3, 5.1, and 5.2
4. Nov 25, 1996. SAS Usage Note 5637 (from 1992) said that you cannot
use ftp to transfer V, VB, or VBS files from MVS to unix, but that
was never true, and that usage note has now been deleted.
All that you need do is to first create a copy of the original file
on MVS that has DCB attributes of RECFM=U and BLKSIZE=32760, and
then download that "RECFMU" copy of the data as a binary file using
ftp. You can use the (free) IBM utility program IEBGENER and this
JCL example to create the required "RECFMU" copy of your data:
// EXEC PGM=IEBGENER
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
//SYSUT1 DD DSN=MXG.ORIGINAL.VARIABLE,DISP=SHR,
// DCB=(RECFM=U,BLKSIZE=32760)
//SYSUT2 DD DSN=MXG.COPY.RECFMU,DISP=(NEW,CATLG),
// UNIT=DASD,VOL=SER=MXGNNN,SPACE=(CYL,(60,5)),
// DCB=(RECFM=U,BLKSIZE=32760)
After the download, you would use the FILENAME statement to tell
SAS this data is V,VB, or VBS using RECFM=S370V, S370VB, or S370VBS,
and SAS will have no problem reading the MVS data file.
This was originally described in Newsletter TWENTY-FIVE, in the
example "e. Downloading raw SMF, VM/Monitor etc., data" in the
article "Executing MXG on PCs and Workstations", although that
example originally did not mention that ftp could also be used.
5. Dec 3, 1996. If you use the FILE command from a Display Manager
Session to SAVE a program, report, etc., without exiting, and you
are creating a new file, the file will be allocated unblocked, which
will waste space and time. To be fixed in SAS Version 7, you can
circumvent by pre-allocation of the file. This only applies to a
SAVE to a new sequential dataset; saving to an existing PDS will
result in a properly blocked file.
6. Feb 12, 1997. To count the number of bits that are on ('1') in a
two-byte character variable (BITMAP), a hexadecimal bit map, this
algorithm
ONESTRNG=PUT(BITMAP,$BINARY16.);
IF BITMAP='0000'X THEN NRBITSON=0;
ELSE NRBITSON=LENGTH(COMPRESS(ONESTRNG,'0'));
was developed. Note that BITMAP='00'X had to be forced to zero, as
the LENGTH(COMPRESS(ONESTRNG,'0')) algorithm returns an incorrect
value of one when BITMAP='00'X.
Added 12Mar97: Don Friesen showed how to do this in one line:
NRBITSON=LENGTH(COMPRESS('1'!!PUT(BITMAP,$BINARY16.),'0'))-1;
I also observed you can use either $BINARY or BINARY as the format
name for a character variable without error, while using $BINARY
format name with a numeric variable, gets the correct result, but
then you also get: "BITMAP HAS ALREADY BEEN DEFINED AS NUMERIC".
VII. CICS Technical Notes.
1. APAR PN70228 has extensive discussion concerning Short on Storage.
in CICS/ESA 4.1 caused by storage fragmentation, though the primary
tool IBM suggests using is the examination of a Dump with IPCS!
Apparently, SOS is again a serious problem in CICS 4.1, and there
are new SIT overrides (CDSASZE, UDSASZE, SDSASZE and RDSASZE) that
may be used to resolve critical SOS problems.
VIII. Windows NT Technical Notes.
1. MXG Support for Windows NT requires Demand Technology's NTSMF. WHY?
At the 1997 August SHARE meeting, Mark Friedman suggested that we
collaborate to provide MXG support for the Windows NT platform.
We recognized the incredible depth of detail available in the NT
registry, and initially looked at the PERFMON application, but we
saw a need for a data management tool (akin to the SMF writer's
function of continuous measurement) with more power and function.
Right now, most MXG sites want to bring the raw Windows NT data to
their MVS platform, where they will process the NTSMF data into an
NT PDB (just like they now process the MVS SMF data into their MVS
Performance Data Base), but PERFMON log record length can grow
without limit preventing processing under MVS, and we had observed
occasional horrific spikes in PERFMON data values that suggested
their extraction and deaccumulation may be in error.
We decided to jointly design our own "SMF" record writer, creating a
format that could be read under MVS or under Windows, with file
management for continuous recording and file switching without
having to start and stop the monitor, and taking less disk space
that does PERFMON for the same data!
Demand Technology sells the "NTSMF" product that creates the raw
data records containing counters from all NT objects. Contact them
at 941-261-8945 for details.
MXG Software then processes the NTSMF records into SAS datasets.
Future enhancements (data filtering, different intervals for
different records, monitoring of selected processes, accounting
data, etc.) are planned, and enhancements are certain to be
suggested by our initial users. (E.g., Mark intends to provide a
utility that will convert NTSMF record into Microsoft's LOG format
in case you ever need to send problem documentation to Microsoft!).
2. So what is NTSMF and what measures do you get from NT registry?
NTSMF has a "server" and a "client". The server is an NT System
Service currently named DMPERFSS that is started once on the machine
to be measured; this "server" responds to calls from the "client",
gets the data from the NT registry, and then sends the data buffers
to the "client". The "client" is an NT process named NTSMF that you
start and control, telling it which records are to be collected and
at what interval. The "client" can run on the measured machine or
on a different machine, and can write the NTSMF records locally
or send them to another machine's disk.
There is an NTSMF record created for each Performance "Object", and
the format is a comma-delimited ASCII file which can be read under
Windows, or sent to MVS, converted ASCII-EBCDIC during transmission,
and read there. For Objects that have multiple instances per
interval (e.g., Logical Disk object has an instance for each logical
drive letter, and one for "_Total"), one record per instance is
written (rather than writing out an ever-growing segmented record).
The complete documentation of each dataset, each variable, etc., is
contained in new member ADOCNTSM; the first ten pages of that
documentation are provided here:
Contents of this NTSMF documentation:
Execution Instructions
Testing Status
Big Picture Description of NT Datasets ('Objects')
List of MXG Data Sets created from NTSMF data records
Common variables in every dataset created from NTSMF records:
Sort Order for each dataset
Documentation of Each Dataset and Each Variable
========================================================================
Execution Instructions
========================================================================
Execution of MXG to read NTSMF data on your MVS platform:
Transmit the NTSMF output data file (a series of ASCII data records,
with comma delimited fields, and CRLF line terminators) from NT to
MVS into a RECFM=VB,LRECL=32756,BLKSIZE=32760 dataset (and specify
conversion from ASCII to EBCDIC, CRLF or equivalent).
Then use //NTSMF DD DSN=your.ntsmf.data,DISP=SHR in your JCL.
Execution of MXG to read NTSMF data under SAS FOR WINDOWS (95 or NT):
Read "Executing MXG on PCs and Workstations", Newsletter TWENTY-FIVE
(in member NEWSLTRS, or file NEWSLTRS.SAS) for instructions on how
to download the MXG Software from MVS to your PC (must be unnumbered
and "member" becomes file "MEMBER.SAS").
You must copy MXG member AUTOEXEC (which would be the file named
AUTOEXEC.SAS in the MXG Source Directory) into the AUTOEXEC.SAS in
your SAS root directory, and add to that list of FILENAMEs:
FILENAME NTSMF 'C:\wherever\is\your\datafile.NTS';
Source Program:
Then under either MVS or PC SAS, run this SAS program:
%INCLUDE SOURCLIB(TYPENTSM);RUN;
to create all possible MXG datasets (that I currently know about) from
your NTSMF data. The datasets will only have observations for those
objects that were found in your data records. (Datasets with zero
observations take essentially no space, so no tailoring is required.)
The default TYPENTSM program invokes _SRTPRNL and _SRTPRNV macros to
print the first fifty observations of each dataset. The table below
identifies those objects for which I have actually had test records;
note that I have coded several datasets but have no test data yet.
In addition, there will be new data sources that I don't know about
yet - dataset UNKNOWN will contain observations if there are any new
records at your site - let's talk when there are!
Make sure you look at these PROC PRINT outputs, and make sure the
numbers make sense at your installation, as this is all very new and
very untested across diverse platforms!
========================================================================
Testing Status
========================================================================
Testing Status: Of the 55 datasets created, I have had test data only
for 28 of those datasets. Datasets with "none" in the following table
have not been tested with data, and may be wrong. If you have obs in
those untested datasets, lets talk!
Data Status: Of the datasets created with observations, these data
values are suspect and under investigation:
DATASET: LOGLDISK, PHYSDISK
Variables: AVGDSKQL, AVGDSKRQL, AVDSKWQL
Values: Always missing.
DATASET: NWLINKSP
Variable: AVGWINSN, MAXWINSN
Values: 3640M in NWLINKSP, but reasonable in NWLINKN
DATASET: SERVWORK
Variable: CTXBLKQU
Values: 218405888 in one instance.
DATASET: SQLUSERS
Variables: USRCPUTM, USRDSKIO
Values: Accumulated, rather than interval values.
DATASET: THREAD
Variable: CNTXTSWT
Values: Reasonable in some cases, 789,849,600 in some.
========================================================================
Big Picture Description of NT Datasets ('Objects')
========================================================================
There are currently 55 "Objects" (NTSMF Record Types) created by NTSMF,
and there are 55 corresponding MXG Datasets created from NTSMF records.
Each "Object" (Record Type) is a set of counters, and a separate record
is created for each instance of an object. A separate MXG Dataset is
created for each Object (dataset SYSTEM for the System object counters,
dataset PROCESOR for the Processor object counters), and a separate
observation is created in the appropriate MXG Dataset for each record.
Some Datasets contain only one instance per interval (Memory, System).
Other Datasets have multiple instances per interval; dataset LOGLDISK
might have three observations per interval, one each with the value of
"D:", "E:", or "_Total" for "instance" variable LDSKNAME.
For these datasets the "Instance Variable" (a/k/a BY variable) is listed
below. Detail examples of actual values found for these BY variables is
given in the individual dataset documentation sections, below.
========================================================================
List of MXG Data Sets created from NTSMF data records
=======================================================================
Object/
Dataset Obs Vars OID Instances Full Descriptive Name
BROWSER 18 26 052 Browser
CACHE 18 33 086 Cache
FTPSERV 18 23 824 FTP Server
GOPHER none 26 ??? GOPHER
HTTP none 35 ??? ? HTTP
ICMP 18 34 582 ? ICMP
IMAGE none 7 ??? ? IMAGE
IISG none 20 ??? ? Internet Information Services Global
IP 18 25 546 IP
LOGLDISK 30 30 236 PDSKNAME,LDKSNAME Logical Disk
MEMORY 18 34 004 Memory
MSEXCHDB 1 26 2574 DBNAME MS Exchange DB ISAM
MSEXCHDS none 19 2198 ? Microsoft Exchange Directory Services
MSEXCHIS none 25 2536 ? MS Exchange Information Store
MSEXCHMC none 14 2286 ENTYNAME MSExchangeMTA Connections
MSEXCHMS none 13 2610 ? MS Mail Connector Interchange
MSEXCHMT none 37 2224 ? MSExchangeMTA
MSEXCHPC none 24 2624 ? MSExchangePCMTA
MSEXCHPR none 26 2300 ? MSExchange Information Store (Private)
MSEXCHPU none 28 2418 ? MS Ex Information Store Public
NBTCONN 90 11 502 CONNNAME NBT Connection
NETBEUI 54 47 492 DEVNAME NETBEUI
NETBEUIR 486 12 494 DEVNAME,ADDRNAME NETBEUI RESOURCE
NETWINTR 1 24 510 INTRNAME Network Interface
NETWSEGM none 15 1110 ? Network Segment
NWLINKIP 18 47 488 DEVNAME NWLINK IPX
NWLINKNB 18 47 398 DEVNAME NWLINK NETBIOS
NWLINKSP 18 47 490 DEVNAME NWLINK SPX
OBJECTS 18 13 260 Objects
PAGEFILE 72 10 700 PAGEFILE Paging File
PHYSDISK 72 27 234 PDSKNAME PhysicalDisk
PENTIUM 1 75 2704 CPUNAME Pentium
PROCASID none 45 786 PROCESS Process Address Space
PROCESS 756 26 230 PROCESS Process
PROCESOR 18 18 238 CPUNAME Processor
RASPORT 18 26 870 COMNAME RAS Port
RASTOTAL none 25 906 ? RAS Total
REDIRECT 18 44 262 Redirector
SERVER 18 33 330 Server
SERVWORK 36 24 1300 QUEUNAME Server Work Queues
SQLICENS 18 10 2108 SQLServer-Licensing
SQLLOCKS 18 28 2064 SQLServer-Locks
SQLLOG 144 11 2170 LOGNAME SQLServer-Log
SQLPROCA 18 17 2116 SQLServer-Procedure Cache
SQLREPDB none 10 2190 ? SQLServer Replication-Published DB
SQLSERVR 18 32 2012 SQLServer
SQLUSERS 144 12 2160 USRNAME SQLServer-Users
SQLUSRCT 18 17 2138 SQLServer User Defined Counters
SYSTEM 18 32 002 System
TCP 18 16 638 TCP
TELEPHNY none 15 1150 Telephony
THREAD 7303 21 232 PROCESS,THRDNAME Thread
THREADET none 10 816 PROCESS,THRDNAME Thread Details
UDP 18 12 658 UDP
UNKNOWN 1 10 --- Unknown/New NTSMF Objects
WINSERV none 920 WINS Server
========================================================================
Common variables in every dataset created from NTSMF records:
========================================================================
DOMAIN DURATM SEQNR SMFTIME STARTIME SYSTEM ZDATE
Variable Type Length Format Label
DOMAIN CHAR 32 DOMAIN*NAME
Header variable. Domain in which this computer SYSTEM is
located.
DURATM NUM 4 TIME13.3 INTERVAL*DURATION
Header variable. Duration of this interval. It is used to create
variable STARTIME=SMFTIME-DURATM; and is a constant value in each
set of records written at end of interval, but it may vary some,
and since NTSMF records are synchronized to time of day, the
DURATM will be less than your chosen recording interval in the
first and last intervals. Compares favorably with DELTA(SYSUPTM)
values, thus validating the accuracy of NTSMF time stamps.
SEQNR NUM 4 RECORD*SEQUENCE*NUMBER
Header variable. All records written at one interval pop will
have the same record sequence number, and each subsequent
interval will have SEQNR incremented by 1. Probably not needed.
SMFTIME NUM 8 DATETIME22.3 TIMESTAMP*WHEN RECORD*WAS WRITTEN
Header variable. Date and timestamp (to nearest millisecond)
of the end of this interval. This time value is on the local
clock of the MONITORING system, not the monitored system.
STARTIME NUM 8 DATETIME22.3 START*DATETIMESTAMP*OF*INTERVAL
Header variable. Datetimestamp (to nearest millisecond) of the
Start of this interval. Calculated STARTIME=SMFTIME-DURATM.
This time value is on the local clock of the MONITORING system,
not the monitored system.
SYSTEM CHAR 32 SYSTEM*NAME
Header variable. Name of this Computer System. Always use in
Sorting, usually in the second position (BY DOMAIN SYSTEM ...).
=======================================================================
Sort Order for each dataset is defined in the _B (for "BY) macros:
=======================================================================
Dataset Macro BY Variables
Name
BROWSER _BNTBROW DOMAIN SYSTEM
CACHE _BNTCACH DOMAIN SYSTEM
FTPSERV _BNTFTP DOMAIN SYSTEM
GOPHER _BNTGOPH DOMAIN SYSTEM
HTTP _BNTHTTP DOMAIN SYSTEM
ICMP _BNTICMP DOMAIN SYSTEM
IMAGE _BNTIISG DOMAIN SYSTEM
IISG _BNTIMAG DOMAIN SYSTEM
IP _BNTIP DOMAIN SYSTEM DEVNAME
LOGLDISK _BNTLDSK DOMAIN SYSTEM PDSKNAME LDSKNAME
MEMORY _BNTMEM DOMAIN SYSTEM
MSEXCHDB _BNTMSDB DOMAIN SYSTEM DBNAME
MSEXCHDS _BNTMSDS DOMAIN SYSTEM
MSEXCHIS _BNTMSIS DOMAIN SYSTEM
MSEXCHMC _BNTMSMC DOMAIN SYSTEM ENTYNAME
MSEXCHMS _BNTMSMS DOMAIN SYSTEM
MSEXCHMT _BNTMSMT DOMAIN SYSTEM
MSEXCHPC _BNTMSPC DOMAIN SYSTEM
MSEXCHPR _BNTMSPR DOMAIN SYSTEM
MSEXCHPU _BNTMSPU DOMAIN SYSTEM
NBTCONN _BNTNBTC DOMAIN SYSTEM CONNNAME
NETBEUI _BNTNBUI DOMAIN SYSTEM DEVNAME
NETBEUIR _BNTNETB DOMAIN SYSTEM DEVNAME ADDRNAME
NETWINTR _BNTNETI DOMAIN SYSTEM
NETWSEGM _BNTNETS DOMAIN SYSTEM
NWLINKIP _BNTNWLI DOMAIN SYSTEM DEVNAME
NWLINKNB _BNTNWLN DOMAIN SYSTEM DEVNAME
NWLINKSP _BNTNWLS DOMAIN SYSTEM DEVNAME
OBJECTS _BNTOBJ DOMAIN SYSTEM
PAGEFILE _BNTPAGE DOMAIN SYSTEM PAGEFILE
PHYSDISK _BNTPDSK DOMAIN SYSTEM PDSKNAME
PENTIUM _BNTPENT DOMAIN SYSTEM
PROCASID _BNTPRAS DOMAIN SYSTEM PROCESS
PROCESS _BNTPROC DOMAIN SYSTEM PROCESS
PROCESOR _BNTPROR DOMAIN SYSTEM CPUNAME
RASPORT _BNTRASP DOMAIN SYSTEM COMNAME
RASTOTAL _BNTRAST DOMAIN SYSTEM
REDIRECT _BNTRDIR DOMAIN SYSTEM
SERVER _BNTSERV DOMAIN SYSTEM
SERVWORK _BNTSERW DOMAIN SYSTEM QUEUNAME
SQLICENS _BNTSQNS DOMAIN SYSTEM
SQLLOCKS _BNTSQKS DOMAIN SYSTEM
SQLLOG _BNTSQOG DOMAIN SYSTEM LOGNAME
SQLPROCA _BNTSQCA DOMAIN SYSTEM
SQLREPDB _BNTSQDB DOMAIN SYSTEM
SQLSERVR _BNTSQVR DOMAIN SYSTEM
SQLUSERS _BNTSQUS DOMAIN SYSTEM USRNAME
SQLUSRCT _BNTSQCT DOMAIN SYSTEM
SYSTEM _BNTSYST DOMAIN SYSTEM
TCP _BNTTCP DOMAIN SYSTEM
TELEPHNY _BNTTELE DOMAIN SYSTEM
THREAD _BNTTHRD DOMAIN SYSTEM PROCESS THRDNAME
THREADET _BNTTHRX DOMAIN SYSTEM PROCESS THRDNAME
UDP _BNTUDP DOMAIN SYSTEM
WINSERVR _BNTWINS DOMAIN SYSTEM
========================================================================
Documentation of Each Dataset and Each Variable
========================================================================
Alphabetic Documentation of each Dataset, with alphabetical list of
each MXG variable's name, type (NUM/CHAR), stored length, FORMAT and
LABEL, along with Microsoft's description of that variable.
For data-tested datasets, there is an enhanced PROC PRINT output:
the variable name is printed in lower case under the LABEL as heading
so you can easily see which MXG variable name is what data.
While you will need to learn the MXG variable name of each object, to
use in your SAS analysis programs, the LABEL of each variable is the
OBJECT NAME of that counter.
Variables that contain byte counts are formatted with the MGBYTES
format (the internal value is always the number of bytes, but that
format prints a value like 200K, 42M, converting and adding the
suffix).
Variables that contain byte rates are formatted with the MGBYTRT
format (the value is bytes per second, but that format prints a value
like 11KB/SEC OR 518B/SEC, converting and adding the suffix).
Most of the other variables are rates, as indicated in the LABEL.
The NTINTRV dataset created by member NTINTRV, (automatically
included by TYPENTSM) will be your primary source of NTSMF measures
(much like RMFINTRV was for RMF data for MVS). Please read the
comments in member NTINTRV to map your PROCESSes to WORKLOADS in the
NTINTRV dataset.
One Workload, NTSMF, that measures the cost of our data capture, has
been created as an example, but you will need to suggest to me how to
name workloads and identify which processes are grouped into which
workloads.
This is the first release of the NTSMF support; I appreciate your
input as we learn what's important and what's not. I hope you
found my variable names understandable, and am ready to fix any
errors and am open to suggestions for enhancements and hereby
solicit your report programs as examples for others.
========================================================================
1. Dataset BROWSER (WIN NT BROWSER)
26 variables, 168 bytes per observation.
One instance per interval. Browser Statistics.
Variable Type Length Format Label
ANNDOMAI NUM 4 ANNOUNCEMENTS*DOMAIN/SEC
(079) Announcements Domain/sec is the rate that a Domain has announced
itself to the network.
ANNDUPMS NUM 4 DUPLICATE*MASTER*ANNOUNCEMENTS
(809) Duplicate Master Announcements indicates the number of times that
the master browser has detected another master browser on the
same domain.
ANNSERVR NUM 4 ANNOUNCEMENTS*SERVER/SEC
(055) Announcements Server/sec is the rate that the servers in this
domain have announced themselves to this server.
ANNTOTAL NUM 4 ANNOUNCEMENTS*TOTAL/SEC
(813) Announcements Total/sec is the sum of Announcements Server/sec
and Announcements Domain/sec.
DOMAIN CHAR 32 DOMAIN*NAME
Header variable. Domain in which this computer SYSTEM is
located.
DTGRILEG NUM 4 ILLEGAL*DATAGRAMS/SEC
(811) Illegal Datagrams/sec is the rate of incorrectly formatted
datagrams that have been received by the workstation.
DTGRMIMA NUM 4 MISSED*MAILSLOT*DATAGRAMS
(169) Missed Mailslot Datagrams is the number of Mailslot Datagrams
that have been discarded due to configuration or allocation
limits.
DURATM NUM 4 TIME13.3 INTERVAL*DURATION
Header variable. Duration of this interval. It is used to create
variable STARTIME=SMFTIME-DURATM; and is a constant value in each
set of records written at end of interval, but it may vary some,
and since NTSMF records are synchronized to time of day, the
DURATM will be less than your chosen recording interval in the
first and last intervals. Compares favorably with DELTA(SYSUPTM)
values, thus validating the accuracy of NTSMF time stamps.
ELECTION NUM 4 ELECTION*PACKETS/SEC
(081) Election Packets/sec is the rate of browser election packets that
have been received by this workstation.
ENUDOMAI NUM 4 ENUMERATIONS*DOMAIN/SEC
(163) Enumerations Domain/sec is the rate of Domain browse requests
that have been processed by this workstation.
ENUOTHER NUM 4 ENUMERATIONS*OTHER/SEC
(165) Enumerations Other/sec is the rate of browse requests processed
by this workstation that were not domain or server browse
requests.
ENUSERVR NUM 4 ENUMERATIONS*SERVER/SEC
(161) Enumerations Server/sec is the rate of Server browse requests
that have been processed by this workstation.
ENUTOTAL NUM 4 ENUMERATIONS*TOTAL/SEC
(815) Enumerations Total/sec is the rate of browse requests that have
been processed by this workstation. This is the sum of
Enumerations Server, Enumerations Domain, and Enumerations Other.
MISSRVRA NUM 4 MISSED*SERVER*ANNOUNCEMENTS
(167) Missed Server Announcements is the number of server announcements
that have been missed due to configuration or allocation limits.
MISSRVRQ NUM 4 MISSED*SERVER*LIST*REQUESTS
(171) Missed Server List Requests is the number of requests to retrieve
a list of browser servers that were received by this workstation,
but could not be processed.
MSALLOCF NUM 4 MAILSLOT*ALLOCATIONS*FAILED
(383) Mailslot Allocations Failed is the number of times the datagram
receiver has failed to allocate a buffer to hold a user mailslot
write.
MSOPENSF NUM 4 MAILSLOT*OPENS*FAILED/SEC
(807) Mailslot Opens Failed/sec indicates the rate of mailslot messages
received by this workstation that were to be delivered to
mailslots that are not present on this workstation.
MSRECVSF NUM 4 MAILSLOT*RECEIVES*FAILED
(385) Mailslot Receives Failed indicates the number of mailslot
messages that couldn't be received due to transport failures.
MSWRITEF NUM 4 MAILSLOT*WRITES*FAILED
(387) Mailslot Writes Failed is the total number of mailslot messages
that have been successfully received, but that were unable to be
written to the mailslot.
MSWRITES NUM 4 MAILSLOT*WRITES/SEC
(083) Mailslot Writes/sec is the rate of mailslot messages that have
been successfully received.
SEQNR NUM 4 RECORD*SEQUENCE*NUMBER
Header variable. All records written at one interval pop will
have the same record sequence number, and each subsequent
interval will have SEQNR incremented by 1. Probably not needed.
SMFTIME NUM 8 DATETIME22.3 TIMESTAMP*WHEN RECORD*WAS WRITTEN
Header variable. Date and timestamp (to nearest millisecond)
of the end of this interval. This time value is on the local
clock of the MONITORING system, not the monitored system.
SRVANALF NUM 4 SERVER*ANNOUNCE*ALLOCATIONS*FAILED/SEC
(381) Server Announce Allocations Failed/sec is the rate of server (or
domain) announcements that have failed due to lack of memory.
SRVLSTRQ NUM 4 SERVER*LIST*REQUESTS/SEC
(085) Server List Requests/sec is the rate of requests to retrieve a
list of browser servers that have been processed by this
workstation.
STARTIME NUM 8 DATETIME22.3 START*DATETIMESTAMP*OF*INTERVAL
Header variable. Datetimestamp (to nearest millisecond) of the
Start of this interval. Calculated STARTIME=SMFTIME-DURATM.
This time value is on the local clock of the MONITORING system,
not the monitored system.
See member ADOCNTSM for rest of NTSMF document (including PROC PRINTs).
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):
NONE
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 to prevent duplicate observations in TYPE74CA.
- 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, earlier.
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 3155+ 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 after MXG 13.13:
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.
ANALDB2R 14.340 DB2PM-like 4.1 reports & each buffer pool and package
ANALDSET 14.064 Using Tape instead of DASD for ANALDSET fails.
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!
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 Combine CICSTRAN and DB2ACCT by Unit of Work
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.
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. (1024 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.
TYPEEPMV 14.337 EPILOG for MVS I/O and ENQ data in EPMVEP, reports.
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.284 Support for Demand Technology's Stress Test SMF.
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 recs with only DRU had 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:
===Changes thru 14.343 were included in MXG 14.14 dated Feb 21, 1997===
Changes 14.210 thru 14.343 were printed in MXG Newsletter THIRTY-ONE and
are listed in member CHANGESS (and member CHANGES of MXG Version 14.14).
Changes 14.001 thru 14.209 were printed in MXG Newsletter THIRTY and are
also listed in member CHANGESS (and member CHANGES of MXG Version 14.14)