COPYRIGHT (C) 1984-2019 MERRILL CONSULTANTS DALLAS TEXAS USA
MXG NEWSLETTER THIRTY-FIVE
MXG NEWSLETTER NUMBER THIRTY-FIVE February 20, 1999
Technical Newsletter for Users of MXG : Merrill's Expanded Guide to CPE
TABLE OF CONTENTS Page
I. MXG Software Version 16.16 was shipped with this newsletter. 2
1. Major enhancements added in MXG 16.16. 2
2. MXG 16.16 contains new "MACKEEP" architecture. 3
II. MXG Technical Notes 7
1. Counting tape mounts.
III. MVS Technical Notes 7
1. APAR OW35684 reports that the BLKSIZE in type 30 may be wrong. 7
2. APAR OW31700 RMF OS/390 type 74 subtype 5 "short records" 8
3. SMF type 42 APARS 8
4. APAR OW35952 corrects large value for IOUNITS in type 30. 8
5. APAR PQ18797 for MQ Series Release 1.3.0, PTF UQ23424 zeros. 8
IV. DB2 Technical Notes. 8
1. Boole and Babbage's MainView for DB2 product's THRDHIST VSAM file 8
2. After installing APAR PN55122, QWHCTOKN wrong for LU6.2 terms 8
3. APARs PQ10864/PQ06968/PQ10864 excessive numbers of DB2 type 101s. 8
V. IMS Technical Notes. 9
VI. SAS Technical Notes. 9
1. MXG 16.05 QA stream has executed using the SAS Version 7. 9
2. RETAIN statement only retains variables in assignment statements. 9
3. SAS 6.09 TS455 and TS460 on MVS SAS "VM1319" or "NO MKLE" error. 9
4. SAS 6.09 TS455/TS460 do not free memory for user formats. 10
VII. CICS Technical Notes. 10
1. There are two CICS summary programs in MXG, ASUMCICS/ASUMCICX. 10
2. APAR PQ13647 corrects invalid Y2K date in IBM type 110 subtype 2 10
VIII. Windows NT Technical Notes. 10
IX. Incompatibilities and Installation of MXG 16.16. 10
X. Online Documentation of MXG Software. 11
XI. Changes Log 11
Alphabetical list of important changes 11
Changes 16.367 thru 16.222 14-58
COPYRIGHT (C) 1999 MERRILL CONSULTANTS DALLAS TEXAS USA
So what's really important?
Year 2000 warrantee: 16.09+ is required for all products to be Y2K ok.
Lots of new product support in MXG 16.16 for OS/390 2.7, CICS TS 1.3,
DB2 1.6, NT 5.0, plus 360 other enhancements and changes, including:
The new "MACKEEP" architecture, introduced in MXG 16.04 last summer,
is inside MXG 16.16 and is in production at several hundred MXG sites.
The Possible DOWN Side:
This new design has incompatibilities with previously-valid tailoring,
if you have changed EXxxxxx or IMACxxxx members that "OUTPUT":
- Only if your tailored members uses "OUTPUT _Lxxxxxx" syntax.
- An incompatibility shows up as a syntax error in JCLTEST6/JCLPDB6.
- Member INSTALL shows error messages and their corrections.
- Usually, changing the "_L" to "_W" eliminates the incompatibility.
Before 16.04, MXG output datasets to their "_Lxxxxxx" macro name.
The new design outputs first to a new "_Wxxxxxx" macro name, that
defaults to the //WORK file, and then the data is sorted to their
"_Lxxxxxx" macro name. If you have tailored MXG and have an exit
member with "OUTPUT _Lxxxxxx" statement, change the _L to a _W.
You can scan your EXxxxxxx and IMACxxxx members for "OUTPUT"
to see which of your exit members (if any) need to be altered.
if you used TYPExxxx members, you may need to now use TYPSxxxx:
- The old TYPExxxx members wrote their data, unsorted to //WORK and
used their _L macroname. Now, TYPExxxx still write to work, but
to their _W macroname, and new TYPSxxxx members should be used in
place of the old TYPExxxx members, because the TYPSxxxx members
create sorted datasets (written to their _L macroname) so that you
can use &Pdddddd macros for their output destination without EDITs.
The UP Side:
With the new design, you may not need that exit member anymore!
- If you tailored the EXxxxxxx/IMACxxxx member just to change the
destination DDNAME of an MXG dataset, you can do that now with the
new &Pdddddd macro and a %LET statement, in //SYSIN, and no longer
have to EDIT/SAVE members to change the output.
- In the old design, IMACxxxx members defined product macros, so
your tailoring member had my macro with all of its definitions.
Now, IMACxxxx members define nothing, as all macros are now
defined in their VMACxxxx. Only the macros you want to change
need to be in your IMACxxxx tailoring members. Furthermore, you
can put all of your changes in the single member, IMACKEEP.
- And still further, you don't even have to have any EDIT/SAVED
member to tailor MXG. Instead, you can pass all of your changes
"instream", thru //SYSIN, using the new MACKEEP= feature.
The Bottom Line:
Dropping in a new MXG Version is usually a "piece-of-cake", and for
most sites this one will be too, but everyone should plan an extra
hour for this install, to read the new INSTALL and DOCMXG members.
In the worst case, any incompatibility problem can be solved by MXG
Technical Support by emailing your "USERID.SOURCLIB" tailoring
library. You can use member JCLZERO to create a single text file in
IEBUPDTE format that can then be emailed (it will compress nicely)
so that I can recreate your error. Out of several hundred sites
running 16.04+, only three have had to send their tailoring library!
I. MXG Software Version 16.16 was shipped with this newsletter.
1. Major enhancements added in MXG 16.16:
While this newsletter is at the printer, additional changes may
be made; check member CHANGES of the MXG 16.16 library to confirm
that these enhancements did in fact occur:
Member INDEX should exist to index MXG subjects and programs.
Support for CO:DI(NDM), a unix log file, is planned.
Support for UNICENTER logs is planned.
Analysis of Job-Delay (HSM,TMNT,TALO) will have been enhanced.
Major enhancements added in MXG 16.10:
OS/390 R2.7, CICS TS 1.3 and DB2 6.1 were supported in MXG 16.09
and that support is now documented. See 16.09 enhancements.
Support for IDMS Version 14 Journal Records.
Support for Sterling's SOLVE NetMaster TCP/IP SMF.
Support for BETA93 subtypes 1,2,3,4,20,40,41,42.
Support for WINDOWS NT 5.0 (INCOMPATIBLE) with NTSMF.
Support for new NT 4.0 objects.
Major enhancements added in MXG 16.09 (revised):
Support for Year 2000 kept Julian date fields input as 0cyyddd.
Support for CICS TS 1.3 (INCOMPATIBLE):
Lots of new CICSTRAN data, including Java execution
and wait times and web statistics, and new statistics data for
each of the now-eleven CICS TCBs. See Change 16.322.
Support for DB2 Version 6.1 (COMPATIBLE).
New header identifies end user's USERID and TERMINAL, more
wait information, CPU time for Stored Procs and Triggers and
User Defined Functions (with SQL time separated). Change 16.318.
Support for OS/390 Release 2.7 (COMPATIBLE)
New Type 74-6 HFS Global/Buffer/File Statistics, Type 73/79 CPMF
mode, Type 70 Dec/Shared Processors Changed, new type 74 time of
Device-Active-Only, and OS/390 Firewall Server Log Messages are
written in new Type 109 SMF record. See Change 16.329.
Major enhancements added in MXG 16.08:
Support for APAF for more than 8 CPU Engines.
Support for BETA93 Release 3.1.3 INCOMPATIBLE subtype 0, 20.
VMXGSUM will use new INHERIT if executed under SAS Version 7.
IMS 6.1 support corrected for APPC, CPIC driven transactions.
Support for DOS/VS Power V6.3.0 (COMPATIBLE).
Revisions to RMM EDGR support - numeric date variables.
Major enhancements added in MXG 16.07:
Support for APAF 4.1 and 4.3 (INCOMPATIBLE).
Support for BETA93 Release 3.1.3 INCOMPATIBLE subtype 21.
ANALRMFR RMF reports added REPORT=XCF.
Major enhancements added in MXG 16.06:
Support for NPM 2.4, unfortunately very INCOMPATIBLY changed!
PDB.CICINTRV dataset may be real bad; please get this new code!
Support for CICS TS 1.2 Journal Format, INCOMPATIBLE.
Support for PSF/MVS Release 3.1.0 (COMPATIBLE).
Support for subtypes 17-20 (FSRTYPE=) HSM FSR records.
Support for IXFP / ICEBERG fields added by APAR L170017.
Support for Boole & Babbage MainView for CICS CMRDETL file.
Correction for SMF 118 TCP/IP logic to not use length/subtype.
MXG 16.04-16.05 only. ASUM70PR summarized to SHIFT vice HOUR.
Major enhancements added in MXG 16.05:
Fix for TMS5 multi-datasets tapes (was wrong).
Fix for IMS 6.1 Log Records (TYPEIMSA) if GMT Offset was not zero.
Support for OAM (Optical Access Method) SMF type 85 record
Support for DFSORT Release 15 (no change)
Support for Interlink TCPaccess Version 5.2 (INCOMPAT)
Support for decompression of MainView history files.
Support for RACF "installation-defined data field".
ML-18 of MXG ASMTAPES MXGTMNT monitor fixes DSAB circular queue.
Major enhancements added in MXG 16.04:
2. MXG 16.04 is a major internal redesign of MXG, the new "MACKEEP"
architecture, which makes tailoring of MXG datasets simpler and more
powerful. You can change the output DDNAME for a large dataset with
a simple "%LET Pdddddd=DDNAME;" statement, you can put all of your
MXG changes in the single member IMACKEEP (instead of having to EDIT
an IMACxxxx for each product), or you can even tailor MXG instream
using the new "%LET MACKEEP = ;" logic, and never have to EDIT any
members into your USERID.SOURCLIB!. This redesign to externalize
all attributes of every dataset began in MXG 10.10 with the "_L,_K"
macros; now that the software is finally done, I can get back to the
rewrite of MXG documentation (but note that member DOCMXG already
exists to document the new architecture, with examples!).
And most, if not all, of your existing MXG tailoring should still
work without change!
"MACKEEP" Architecture of MXG-built SAS "Datasets"
Everything about the creation of an MXG dataset is now
fully externalized, and ALL MXG tailoring can now be done
EDIT into a single member, IMACKEEP (instead of EDITing
a separate IMAC for each product)
all tailoring can be done "instream" using the new syntax
%LET MACKEEP= MACRO _oldname newvalue % ;
All MXG datasets now have an &Pdddddd macro variable as the
destination DDNAME/LIBREF, so you can use %LET Pdddddd=MYDD;
in IMACKEEP or with MACKEEP to change the DD to which each
MXG dataset is written or read from.
See member DOCMXG, INSTALL, and Change 16.134 for details.
Major enhancements added in MXG 16.04:
MXG "MACKEEP" Architecture - see INSTALL, DOCMXG, Change 16.134.
Support for OS/390 Release 2.6 (COMPATIBLE).
Support for IMS Log processing for IMS 6.1.
Support for NTSMF Version 2.2.
Support for ACF2 Version 6.2 type 'V' (INCOMPATIBLE).
Support for TCP/IP 3.4 SMF type 118 (INCOMPATIBLE) changes.
Support for NCR Teradata DBS performance data.
Support for Landmark's SQL/CAPTURE Products 'D6' record.
Support for XCOM Release 3.0 (COMPATIBLE).
Support for Soft Audit's Installed Products File.
Support for BGS I/O Monitor Version 5.1.0 (COMPAT).
Support for HSM APAR OW31281 adds RECALL, DSR, FSR statistics.
Support for DFSMS 1.4.0 added WFSCPUTM for ABARS CPU cost.
Support for NTSMF CachingManager and Packet Filter objects.
Support for NT Service Pack 5A SYSTEM/PROCESS fields.
Major revision of TMS/CA-1 processing logic in TYPETMS5.
ML-17 of MXGTMNT/ASMTAPES synchronizes automatically.
Enhanced TPM support reads all possible variables in TYPETPMX.
Analysis of SMF Write Rates (MEGABYTES at 10/100sec)
MXG CONFIG value of VMCTLISA=40K raised to 160K.
VMXGSUM syntax for "DATETIME" now uses real name.
ABEND/CONDCODE in PDB.JOBS is now valid, has 1st ABEND.
(MXG 16.03 was only released as a Beta.)
Major enhancements added in MXG 16.02:
Support for TYPEIMS7 for IMS 6.1.
Support for OS/400 Version 4.2.0 COMPATIBLE.
Support for MQ Series Version 1 Release 2 INCOMPATIBLE.
Support for Landmark's Monitor for DB2 V 3.1 INCOMPATIBLE.
Support for Candle Omegamon V400 CANMQ and CANWLMSC.
Support for Candle Omegamon CICS V400 "255" record.
Support for Raptor Systems' Eagle Firewall 121 Log.
Support for TME 10 NetView for OS/390 V1 R1 SMF 38.
Support for Web Proxy logs Extended Common Log format.
Support for Magstar tapes in TYPETMS5 INCOMPATIBLE.
&PDBxxxx and &yyyzzz "Dataset &Macro" naming rules.
New PDB datasets TYPE74CO/ME/PA/SY/OM/LK added to daily PDB.
New ANALABND report ABENDs from PDB.STEPS, uses PROC TABULATE.
Multiple JES3 purge records created duplicate PDB.JOBS obs.
All MXG variables with format MGBYTES are now stored in 8-bytes.
New ANAL6264 merges VSAM type 62 and 64 for OPENTIME.
Major enhancements added in MXG 16.01:
The major thing in 16.01 is support for Year 2000 products that
were not Y2K compliant when 15.15 was built, so MXG 16.01 is now
the minimum level to support all vendor records that provide year
2000 dates, but there are also a few fixes and several enhancements
and new products supported.
Year 2000 issues that require MXG 16.01 or the specific change:
TYPE6 READTIME was 1900 in 2000 due to MXG error (Change 16.039).
AS/400 Year 2000 Support was Incorrect (Change 16.035).
NETVIEW NPM type 28 year Y2K Ready but INCOMPATIBLE record change.
Landmark TMON for CICS V2 converted to V8.1 Y2K Ready, INCOMPAT.
IPAC RDS View Direct V 6.1 Y2K Ready, but INCOMPATIBLE change.
MXG Software now warrants it is "Year 2000 Ready".
Support for new NTSMF objects (Database, SMTP Server, WEB Service).
Support for revised NTSMF Active Server Pages and IISG records.
Support for Software Engineering's SpaceManager data records.
Support for DECnet/SNA DTF SMF records.
MXG 15.15 problems reported and fixed:
Variable MXGVERSN in TYPE70 was blank in 15.15; impacts CPEXPERT.
Deactivated PR/SM Partition may cause over 100% CPU Busy for CEC.
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 Compatibility Mode Mar 28 1997 14.14
OS/390 1.3.0 WLM Goal Mode Mar 28 1997 15.02
OS/390 2.4.0 Sep 28 1997 15.06
OS/390 2.5.0 Feb 24 1998 15.06
OS/390 2.6.0 Sep 24 1998 16.04
OS/390 2.7.0 Mar 26 1999 16.09
CICS/ESA 3.2 Jun 28, 1991. 9.9
CICS/ESA 3.3 Mar 28, 1992. 10.01
CICS/ESA 4.1 Oct 27, 1994. 13.09
CICS/ESA 5.1 aka CICS/TS V1R1 Sep 10, 1996 14.07
CICS-Transaction Server V1R1 Sep 10, 1996 14.07
CICS-TS V1R1 with APAR UN98309 Sep 15, 1997 15.06
CICS-TS V1R2 Oct 27, 1997 15.06
CICS-TS V1R3 Mar ??, 1999 16.09
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 Sep 11, 1996 14.07
DB2 5.1.0 Tolerate Jun 27, 1997 14.14
DB2 5.1.0 Full support Jun 27, 1997 15.02
DB2 6.1.0 Mar ??, 1999 16.09
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
DFSMS/MVS 1.4 Sep 28, 1997. 15.04
DFSMS/MVS 1.4 HSM Sep 23, 1998. 16.04
MQM 1.1.2, 1.1.3, 1.1.4 Apr 25, 1996. 14.02
MQ Series 1.2.0 May 26, 1998. 16.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 ??? ??, 1996. 15.08
NPM 2.4 Nov 18, 1998. 16.06
RMDS 2.1, 2.2 Dec 12, 1995. 12.12
TCP/IP 3.1 Jun 12, 1995. 12.12
TCP/IP 3.4 Sep 22, 1998. 16.04
DOS/VSE POWER V6.3.0 Dec 19, 1998. 16.08
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
VM/ESA 2.3 ??? ??, ???? 16.08
IMS 4.1 Aug 6, 1994 12.02
IMS 5.1 Jun 9, 1996 14.05
IMS 6.1 ??? ?, 199? 16.04
AS400 3.7.0 Nov 1, 1996 15.01
AS400 4.1.0 Dec 30, 1996 15.08
AS400 4.2.0 Apr 27, 1998 16.02
Availability dates for non-IBM products and MXG version required:
Product Name Required
Windows NT 4.0 and NT 3.51 14.14
Windows NT 4.0 Service Pack 2 15.03
Windows NT 4.0 Service Pack 5 16.04
NTSMF Version 1 Beta 14.11
NTSMF Version 2.0 15.05
NTSMF Version 2.1 15.06
NTSMF Version 2.2 16.04
The Monitor for DB2 Version 2 13.06
The Monitor for DB2 Version 3.0 16.02
The Monitor for DB2 Version 3.1 16.02
The Monitor for CICS/ESA 1.2 - 12.12
The Monitor for CICS/ESA 1.3 - 15.01
The Monitor for CICS/ESA 2.0 - 15.06
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.09
Omegamon for CICS V200 User SMF 12.05
Omegamon for CICS V300 User SMF 13.06
Omegamon for CICS V400 User SMF 16.02
Omegamon for CICS V400 type 110 segments 16.02
Omegamon for IMS V110 (ITRF) 12.12
Omegamon for IMS V300 (ITRF) 14.04
Omegamon for MVS V300 13.05
Omegamon for MVS V400 13.06
Omegamon for DB2 Version 2.1/2.2 13.05
Omegamon for VTAM V160 12.04A
Omegamon for VTAM V400 15.15
Omegamon for SMS V100/V110 12.03
ACF2 6.2 16.04
ASTEX 2.1 14.04
NETSPY 4.7 14.03
NETSPY 5.0 14.03
NETSPY 5.2 16.05
Boole & Babbage
IMF 3.1 (for IMS 5.1) 12.12
IMF 3.2 (for IMS 6.1 only) 15.09
IMF 3.2 (for IMS 5.1 and 6.1) 16.04
LMS 3.1 12.12A
MXG IMS-Log Not-Officially-Supported
IMS 6.1 - ASMIMSL6/TYPEIMSA 16.06
IMS 5.1 - ASMIMSL5/TYPEIMSA 16.01
APAF 4.1, 4.3 16.08
II. MXG Technical Notes
1. Counting tape mounts.
Tape mount counts from the MXGTMNT monitor can be compared with the
tape mount counts (TAPNMNTS+TAPSMNTS) in the step records, and there
can be differences, mostly due to the difference in time frame of
the mount records (when they occur) and the step records (when the
- MXG will count high for Started Tasks that never end (e.g. DFHSM),
or for any job whose step record had not yet been written in the
SMF time frame you examined.
- MXG will count low for steps that ended in the SMF time-frame, but
whose mounts occurred before the start of that SMF file.
- MXG counts physical mount events, but the type 30 counts completed
mounts, so when your tapeape intentionally mounts the wrong VOLSER
if they can't find the right tape, they mount any tape, knowing
MVS label-check will prevent it from being used, but any mount
terminates the outstanding mount message so the MVS console guy
can't see how long the real mount has been waiting!
the MXG count is five mounts, the step record count is one.
- MXG misses some VTS scratch mounts, when using the default two
second sampling in MXGTMNT, because scratch mounts to VTS can be
fast. In one day MXG missed 200 VTS scratch mounts out of 2000
total VTS mounts with the two-second sampling, but MXGTMNT saw
all of the VTS scratch mounts with one-half second sampling.
If you want to compare totals, use the TYPE30_V or PDB.SMFINTRV data
from type 30 interval records instead of TYPE30_4 or PDB.STEPS data
to minimize (but not eliminate) time-frame error, since the interval
records will count the mounts for those long-running jobs and STCs.
If you do have Virtual Tape Devices, you could change the interval
constant in member ASMTAPES (INTERVAL DC F'200' to DC F'050') to
change the MXG default of 2.00 seconds to 0.50 seconds, and then
re-assemble to change the MXGTMNT program to sample at half-second
intervals. While 2 seconds is still the MXG default, half-second
was tested and briefly suggested as an alternative, as the CPU cost
was still small:
At half-second sampling, it took less than 3 CPU seconds per
15 minute interval to scan 100 tape devices, and another 1 CPU
second for every 100 tape mounts, or a few minutes per day with
However, even with .5 second interval, the mount monitor missed some
fast VTS mounts, which caused me to create the completely new logic
in the ASUMTAPE program, which creates the new PDB.ASUMTAPE dataset
(that should be used in place of PDB.TYPETMNT in tape mount
analysis). The new logic is driven by the type 21 dismount record,
so even if MXGTMNT missed the fast mount, PDB.ASUMTAPE has the tape
event, albeit with the tape mount duration missing (so you know it
was less than 2 secs!), so the original 2 second default was kept.
If you decide to change the sample interval, you can compare the
number of observations in PDB.ASUMTAPE that have missing TAPMNTTM,
to see how many more of the fast-scratch-VTS-mounts you actually
capture at 1/2 second instead of the MXG default of 2 seconds.
This note was revised for clarity about the MXG default 19Jun2001.
III. MVS Technical Notes.
1. APAR OW35684 confirms that the BLKSIZE in the DD segments of type 30
records is correct for tape but incorrect for a DASD dataset that is
being opened for output DISP=NEW when DADSM allocate did not
determine a system determined blocksize (SDB) even though BLKSIZE=0
was specified on the DD statement. DADSM SDB processing was not
done because DSORG and/or LRECL were not also specified. The APAR
is closed "FIN" - Fixed in Next DF/SMS Release in 18-24 months.
2. APAR OW31700 RMF OS/390 type 74 subtype 5 describes "short records"
created when there are more than 153 devices on a cache controller
(because 153 segments fills the 32756-byte limit of SMF data). They
have no impact on MXG, as MXG reads each record and outputs from
each device data section (but IBM had to add counters so RMF
could reassemble the large event from these 32K "small" records).
There may be an error, as I have seen type 74 subtype 5 records with
only the Product and Control section, with no status nor data and
with R745CCNT, record sequence, of 2. Site is talking to IBM.
3. SMF type 42 APARS:
APARs OW29633 corrects timestamps in TYPE42DS (type 42 subtype 6)
SMF records that caused SMF42PTS to be much earlier than the job's
READTIME. Reported in OW10694 (closed RET) and OW25624 (closed PER)
the actual error was a failure to free main between jobs, so you
would have someone else's READTIME in your record. This error was
not fixed to correct SMF, but because someone's system stayed up
long enough that the memory leak causes a storage shortage ABEND!
APAR OW32248 discusses type 42 VSAM/RLS counter errors, affecting
APAR OW35762 corrects count of SEQ blocks read and written for PS
datasets on non-SMS managed volumes.
4. APAR OW35952 corrects large value for IOUNITS in type 30 records;
the problem primarily affected DB2 address spaces with very large
(but legitimate) I/O counts that caused an overflow in IO Servunits.
5. APAR PQ18797 for MQ Series Release 1.3.0, PTF UQ23424 corrects zero
values for 'QMSTxxxx' variables in dataset MQMMSGDM from type 115
SMF record subtype 2.
IV. DB2 Technical Notes.
1. Boole and Babbage's MainView for DB2 product's THRDHIST VSAM file is
used for online access and its keyed record format is not public, so
MXG cannot support that file. But Boole recommends you create DB2
SMF records (their DB2 batch reports use the 100/101/102 records) so
THRDHIST was never intended to be useful for accounting or trending.
2. MXG Newsletter 34 reported that after installing APAR PN55122 and
migrating to CICS/ESA 5.1 (that's /ESA in 1996 not /TS 5.1 in 2012!)
that LU6.2 terminal's QWHCTOKN no longer had the UOWID token in
their DB2ACCT record (as a result, MXG's ASUMUOW could not match
DB2ACCT to CICSTRAN by Unit-of-Work ID). IBM has now released APAR
PQ15565 (and PTF UQ18583) to correct their error.
3. APARs PQ10864/PQ06968/PQ10864 discuss excessive numbers of DB2 type
101 SMF records that are created with CPU parallelism; if your DB2
application is running with more than 1 degree of CPU parallelism,
the child tasks will create SMF 101 accounting records every time
they are spawned (i.e., every SQL execution). In cases where an
application loops thru static SQL frequently or for transaction type
queries the volume can be a very serious problem. This problem will
NOT be fixed until DB2 Version 6, but APAR PQ06968 has been created
to allow RLF to disable modes of parallelism during static BIND; by
using RLFFUNC=4 during BIND, you can force problem applications back
to IOP parallelism (versus CPU parallelism).
V. IMS Technical Notes.
VI. SAS Technical Notes.
1. MXG 16.05 QA stream has executed using the SAS Version 7 Beta, under
OS/390, Windows 95/98 and Windows NT. Minor changes were needed in
MXG code, mostly to circumvent Beta things that SAS will have fixed
by the Production release this fall. A complete list will be in a
future MXG Technical Note when Version 7 is available.
Initial performance measurements of the MXG QA stream show no change
in the runtime between Version 6.12 TS045 and Version 7 Beta, so
it looks like lots of new features at no cost, for a change!
SAS Version 7 datasets cannot be read by SAS Version 6; the format
of SAS data libraries on all platforms was changed incompatibly.
Fortunately, MXG will not exploit on any SAS Version 7 features in
the near future, and there are no compelling reasons to migrate to
SAS Version 7 (run times and resources were about the same), but
when you do migrate to SAS V7, you will either have to drop it in
all at once, or at least you will need to install from the back end:
convert your report programs first and then convert the programs
that build the datasets that the reports use.
2. RETAIN statement only retains variables in assignment statements.
You cannot use a RETAIN statement with SET A B logic to retain the
value of variable A from dataset A into processing of observations
from dataset B. While the A variable will exist in the OUT dataset
its value will be missing:
DATA A; A=1;
DATA B; DO B=1 TO 5; OUTPUT B; END;
DATA OUT; SET A B;
To retain the value of variable A, you must assign it to a new name
(AA) while reading an observation from dataset A, retain that AA
name, and then when reading an observation from dataset B, assign AA
back to its original name A (and then DROP variable AA from OUT):
DATA OUT; SET A (IN=INA) B (IN=INB);
RETAIN AA; DROP AA;
IF INA THEN AA=A;
IF INB THEN DO; A=AA; OUTPUT; END;
Fortunately, variable A's attributes (LABEL, FORMAT, etc) are indeed
propagated into variable A in the OUT dataset.
3. SAS 6.09 TS455 and TS460 on MVS may encounter SAS "VM1319" or "NO
MKLEs" ABENDs, due to a memory overlay introduced by TS455. SAS ZAP
Z609E449 exists and is flagged as REQUIRED, but is not a true fix.
That ZAP forces SAS options MVARSIZE=0 and MSYMSIZE=0, which causes
%MACRO variables and symbol tables to be written/read to/from disk
instead of from memory. By reducing memory for macros, the overlay
may be avoided, but depending on how %macros are used, that ZAP
could impact runtime performance. The text of ZAP Z609E449 suggests
that increasing MEMSIZE may circumvent the error, since the overlay
is less likely with more addressability, so if you encounter the
error, first increase MEMSIZE by 8MB (and remember to increase your
REGION size), and then if that doesn't work, then either install the
ZAP, or install its effect by setting MVARSIZE=0 and MSYMSIZE=0
4. SAS 6.09 TS455/TS460 do not free memory for user formats, which can
cause an out of memory error if there are repeated references to a
user format, e.g., a DO Loop around PUT(variable,format) statement
where the format is NOT one supplied with SAS (MGxxxxx formats or
your own build with PROC FORMAT are "user formats").
SAS ZAP Z609F331 will correct this memory "leak".
VII. CICS Technical Notes.
1. There are two CICS summary programs in MXG:
ASUMCICS summarizes the detail CICSTRAN.CICSTRAN transactions, so
variable NUMTRANS counts the number of transactions.
ASUMCICX summarizes the already-summarized ASUMUOW unit-of-work
dataset, so NUMTRANS counts the number of unit's-of-work,
and variable MROTRANS counts the number of CICSTRAN
transactions that were executed by that unit-of-work.
2. APAR PQ13647 corrects invalid Y2K date in IBM type 110 subtype 2
TS Server records written by CICS TS 1.1 and 1.2. The dates will
contain 1AYY instead of 20YY without this fix.
VIII. Windows NT Technical Notes.
There are no Windows NT Technical Notes in this Newsletter.
IX. Incompatibilities and Installation of MXG 16.16.
1. Incompatibilities introduced in MXG 16.16 (since MXG 15.15):
a- IMACs that were changed (if they exist in your USERID.SOURCLIB, you
must refit your tailoring, starting with the new IMAC member):
Almost all IMACxxxx members can be consolidated into "IMACKEEP".
b- Other incompatibility changes:
The "MACKEEP" re-design may be incompatible with some previously
valid user-tailoring. See instructions in member INSTALL, which
show examples of the error messages which can result and their fix.
All MGBYTES formatted variables are now length 8, instead of 4.
If you use PROC APPEND without FORCE, SAS will ERROR when you try
to combine new and old datasets with dissimilar length variables.
c- The products that were incompatibly changed by their vendor are
listed in the Changes Log, section XI, below.
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.
X. Online Documentation of MXG Software.
MXG Documentation is now described in member DOCUMENT.
XI. 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 is normally
created after the newsletter is sent to the printer! Member CHANGES
on the www.MXG.com homepage are the most timely, as they are updated
(sometimes) between MXG versions.
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 15.15 now in MXG 16.16:
Member Change Description
Many 16.216 Support for OS/390 Release 2.6 (COMPATIBLE).
Many 16.078 MXG variables with format MGBYTES are now 8-bytes.
Many 16.068 &PDBxxxx and &yyyzzz "Dataset &Macro" naming rules.
ADOCQAPM 16.301 Enhanced documentation for AS/400 processing
ANAL6264 16.071 Analysis merges VSAM type 62 and 64 for OPENTIME.
ANALABND 16.082 ABEND stats from PDB.STEPS, uses PROC TABULATE.
ANALCISH 16.104 MORE THAN 32767, MORE THAN 10 errors corrected.
ANALPATH 16.006 SUBSCRIPT OUT OF RANGE, report expected 10 LCUs max.
ANALRMFR 16.295 ANALRMFR RMF reports added REPORT=XCF.
ANALSRVC 16.098 Report now works for CPU Percent by Service Class.
ANALUOW 16.075 Enhancements, DB2 Class 3 waits. etc were added.
ANALVTS 16.162 Analysis combines 30s, TMNT, TALO and 21s for tapes.
ANANCNCR 16.206 COUNT= option corrected.
ASMIMSL5 16.058 ASMIMSL5 in MXG 15.15 failed during assembly.
ASMIMSL6 16.185 Support for IMS Log processing for IMS 6.1.
ASMMNVW 16.247 Support for decompression of MainView history files.
ASMTAPES 16.154 ML-17 of MXGTMNT synchronizes automatically.
ASMTAPES 16.164 MXGTMNT misses too-fast VTS tape mounts.
ASMTAPES 16.259 ML-18 of ASMTAPES protects DSAB circular queue.
ASUM42DS 16.046 New summary member for TYPE42DS by dataset.
ASUM70PR 16.028 Deactivated Partition may cause over 100% CPU Busy.
ASUM70PR 16.271 16.04-16.05. ASUM70PR summarized at SHIFT vice HOUR.
ASUMCACH 16.141 DURATM in ASUMCACH revised for accuracy.
ASUMCICS 16.137 INVALID ARGUMENT TO FUNCTION SQRT when N=1.
ASUMHSM 16.315 Revision to Support HSM Y2K Julian dates.
ASUMHSM 16.345 HSM summarization separates HSM active from queued.
ASUMTALO 16.076 Revised to work with TALO records from old ASMTAPES.
ASUMTALO 16.169 SPIN.SPINTALO now backed up into PDB library.
BLDNTPDB 16.180 NTSMF Daily/Weekly/etc BUILD program enhanced.
BUILDPD3 16.080 JES3 BUILDPDB - Multiple PDB.JOBS obs - multi purges.
BUILDPDB 16.008 Duplicate TYPE30_V records might not be deleted.
BUILDPDB 16.107 PDB.TYPE74CO/ME/PA/SY/OM/LK added to day/week PDB.
BUILDPDB 16.183 ABEND/CONDCODE in PDB.JOBS now valid, has 1st ABEND.
BUILDPDB 16.230 Duplicate type 30 records caused RESTARTS to be high.
BUILDPDB 16.231 TYPE6 vars STDUPLEX/FCB/OVLYLOAD/OVLYUSED added.
BUILDPDB 16.348 BINxxxx variables added to PDB.PRINT.
CICINTRV 16.253 Revision of CICINTRV auto-determine input location.
CICINTRV 16.277 PDB.CICINTRV dataset may be real bad; get this code!
CONFIG 16.066 Option SASAUTOS=(SOURCLIB SASAUTOS) is now used.
CONFIG 16.117 CODEPCT=150 now set to eliminate SAS message.
CONFIG 16.157 MXG CONFIG value of VMCTLISA=40K raised to 160K.
CONFIG 16.209 NOSTIMER now specified, SAS 6.12 TS045 changed.
DOCGRAF 16.018 Examples of getting graphs from mainframe to your PC.
DOCMXG 16.134 New &MACKEEP and IMACKEEP MXG architecture changed.
FORMATS 16.214 Support for DF/SMS 1.4 changes to HSM (COMPAT).
IMACFILE 16.016 &MACFILE macro added for instream tailoring.
IMACICDM 16.067 Support for Candle Omegamon V400 CANMQ and CANWLMSC.
IMACPDB 16.106 Enclave CPU time and count added to PDB.STEPS/JOBS.
IMACPDB 16.341 IMACPDB documentation, no code was changed.
MXGSAS 16.081 JCL parameter TAILORNG now spelled TAILOR.
RMFINTRV 16.288 Sort order of RMF is now BY SYSPLEX SYSTEM STARTIME.
TRND70 16.021 TRENDing of TYPE70 now supports 16 buckets of CPUs.
TRND72GO 16.029 Variable R723CIMP in TRND72GO SUMmed vice IDd.
TRNDTALO 16.221 Overlapped hour could miscount tape allocations.
TYPE109 16.329 Support for TYPE109 OS390 Firewall Server.
TYPE110 16.031 CICS UNEXPECTED STID=0 was error in STID=94 segment.
TYPE110 16.153 GMT offset calculation in CICS off by up to 1.4 secs.
TYPE110 16.270 Support for CICS TS 1.2 Journal Format, INCOMPATIBLE.
TYPE110 16.322 Support for CICS TS 1.3 (INCOMPATIBLE).
TYPE115 16.099 Support for MQ Series Version 1 Release 2 (INCOMPAT).
TYPE16 16.254 Support for DFSORT Release 15 (No Change).
TYPE28 16.003 NETVIEW NPM type 28 INCOMPATIBLE year 2000 change.
TYPE28 16.290 NPMLANOD dataset TIC_UTIL variable was missing.
TYPE28 16.336 STOPOVER NPM 2.4 NPMSUBTY='DD'x; IBM doc was wrong.
TYPE30 16.150 TYPETASK='ASCH' or TYPETASK='OMVS' now set in PDB.
TYPE38 16.101 Support for TME 10 NetView for OS/390 V1 R1 SMF 38.
TYPE42 16.339 SMF type 42 subtypes 15-19 (VSAM RLS) now validated.
TYPE57 16.234 JES3 with more than 9999 job numbers INVALID DATA.
TYPE6 16.039 READTIME in TYPE6 and hence PRINT is 1900 in 2000.
TYPE6 16.264 Support for PSF/MVS Release 3.1.0 (COMPATIBLE).
TYPE7072 16.009 Variable MXGVERSN in TYPE70 was blank in 15.15.
TYPE7072 16.194 Delay Percents now divided by R723CTSA.
TYPE7072 16.326 TYPE72 Compat Delay variables were incomplete.
TYPE7072 16.327 PERFINDX sometimes missing for Average Resp Goals.
TYPE7072 16.328 Variable PCTMETGO added to TYPE72GO for Percentiles.
TYPE7072 16.342 New variable CECSER with CPU Serial of the CEC.
TYPE72GO 16.064 Variables AVGRESP, EXETTM, AVGXETTM added/changed.
TYPE72GO 16.083 Variables R723CQDT/CADT/CCVT/CIQT wrong multiplier.
TYPE74 16.032 NO STRUCTURE MATCH message understood and eliminated.
TYPE74 16.095 TYPE74 variable IORATE changed to match IBM's RMF.
TYPE74 16.329 Support for TYPE746B/F/G datasets in OS/390 R2.7.
TYPE79 16.213 Type 79 Subtype 15 (IMS Long Lock) corrected.
TYPE7xxx 16.288 Sort order of RMF is now BY SYSPLEX SYSTEM STARTIME.
TYPE80A 16.236 Support for RACFEVNT=26 APPCLU Session Establish.
TYPE80A 16.245 Support for RACF "installation-defined data field".
TYPE85 16.255 Support for OAM type 85 SMF record, 11 datasets.
TYPE94 16.135 VTS variables SMF94VBA/VLA were mis-documented by IBM
TYPE99 16.026 New subtype 6 SMF type 99 INVALID SERVER SECTION.
TYPEACF2 16.215 Support for ACF2 Ver 6.2 type 'V' (INCOMPATIBLE).
TYPEAPAF 16.305 Support for more than 8 engines in APAF data.
TYPEBETA 16.293 BETA93 Version 3.1.3 INCOMPATIBLY changed.
TYPEBETA 16.351 Support for BETA93 subtypes 1,2,3,4,20,40,41,42.
TYPEBGSI 16.155 Support for BGS I/O Monitor Version 5.1.0 (COMPAT).
TYPECIMS 16.030 ABENDUSR in CIMSPROG has never been right.
TYPECIMS 16.227 IMF 3.2 with IMS 5.1 INPUT STATEMENT EXCEEDED.
TYPEDB2 16.318 Support for DB2 Version 6.1 (COMPATIBLE).
TYPEDB2 16.148 Dataset DB2STATR was invalid, duplicate observations.
TYPEDCOL 16.017 DCOLLECT DSORG field expanded to 3 in MXG (PSU etc).
TYPEDECS 16.034 Support for DECnet/SNA DTF SMF records.
TYPEDOS 16.312 Support for DOS/VS Power V6.3.0 (COMPATIBLE).
TYPEEAGL 16.102 Support for Raptor Systems' Eagle Firewall 121 Log.
TYPEEDGR 16.308 Revisions to RMM EDGR support - numeric dates.
TYPEHSM 16.136 DFSMS 1.4.0 added WFSCPUTM for ABARS CPU cost.
TYPEHSM 16.145 Support for APAR OW31281 adds RECALL, DSR, FSR.
TYPEHSM 16.149 SHORT ABAR message after Change 16.025 fixed.
TYPEHSM 16.263 Support for FSRTYPE=17 thru 20 HSM FSR records.
TYPEHSM 16.315 Revision to Support HSM Y2K Julian dates.
TYPEICE 16.280 Support for IXFP fields added by APAR L170017.
TYPEIDMJ 16.361 Support for IDMS Version 14 Journal Records.
TYPEIDMS 16.002 New TASNxxx variables labels were incorrect.
TYPEIDMS 16.012 IDMS 10.2.1 caused INPUT STATEMENT EXCEEDED.
TYPEIDMS 16.033 IDMS 10.2 records were not output.
TYPEILKA 16.249 Support for Interlink TCPaccess Vers 5.2 (INCOMPAT)
TYPEIMS7 16.119 Support for TYPEIMS7 for IMS 6.1.
TYPEIMSA 16.069 ASMIMSL5 process now has _L, _K macros, exit members.
TYPEIMSA 16.257 IMS 6.1 Support correct only in European Summer Time.
TYPEIMSA 16.343 Zero observations in IMSFASTP, SUBCODE not kept.
TYPEIPAC 16.052 Y2K INCOMPATIBLE IPAC RDS 6.1 user SMF record.
TYPEMON8 16.049 Y2K Support for TMON V2 records converted to 8.1.
TYPEMON8 16.073 INVALID DATA FOR TMMDMODL message corrected.
TYPEMON8 16.091 TMON for CICS V2 Converted records MONIRECD='D'.
TYPEMVCI 16.260 Support for Boole & Babbage MainView CMRDETL file.
TYPENDM 16.060 Sterling's Connect Direct aka NDM PI=754129 open.
TYPENSPY 16.147 NETSPY='N' record support was restored for old 4.4.
TYPENTSM 16.024 Support new "Database" object and EXCHANGE 5.5.
TYPENTSM 16.045 Support for IISG, Active Server Pages, Web Service.
TYPENTSM 16.049 New SNA LU, SNA 3270 Response, etc, NTSMF objects.
TYPENTSM 16.121 Support for NTSMF Cache Mgr & Packet Filter objects.
TYPENTSM 16.133 Summarization of NETWSEGM into NTINTRV wrong if two.
TYPENTSM 16.177 Support for NT Service Pack 5A SYSTEM/PROCESS fields.
TYPENTSM 16.199 NTSMF Object='WidetoMBErr' explained.
TYPENTSM 16.208 Support for NTSMF internal 0.1 configuration record.
TYPENTSM 16.217 New objects NetShow Station/Unicast Service support.
TYPENTSM 16.228 Support for NTSMF V2.2 with Record Header 2.2.1.
TYPENTSM 16.317 Support for NTSMF 2.2.1 header (or use COMPRESS).
TYPENTSM 16.337 Support for new NT 4.0 objects.
TYPENTSM 16.350 Support for WINDOWS NT 5.0 (INCOMPATIBLE) with NTSMF.
TYPEOMCI 16.116 Support for Candle Omegamon CICS V400 "255" record.
TYPEOMVT 16.262 Candle Omegamon for VTAM documentation error.
TYPEQAPM 16.035 Year 2000 Support for AS/400 was corrected.
TYPEQAPM 16.063 Support for OS/400 Version 4.2.0 (COMPATIBLE).
TYPESFTA 16.175 Support for Soft Audit's Installed Products File.
TYPESOLN 16.356 Support for Sterling's SOLVE NetMaster TCP/IP SMF.
TYPESPMG 16.020 Support for Software Engineering's SpaceManager data.
TYPETAND 16.118 Tandem variables CnBLKS and CnBLKSAV corrected.
TYPETCP 16.211 Support for TCP/IP 3.4 (sorta INCOMPATIBLE).
TYPETCP 16.242 TCP SMF record subtype externalized _SUBTCP5 macro.
TYPETDTA 16.170 Support for NCR Teradata DBS performance data.
TYPETMDB 16.097 Support for Landmark's Monitor for DB2 V 3.1 INCOMPA
TYPETMDB 16.160 Support for Landmark's SQL/CAPTURE type 'D6' record.
TYPETMO2 16.122 Variables SYSID,APPLID,SYSPLEX blank in MXG.
TYPETMS5 16.088 Lost obs in TMS dataset DSNBRECD for Magstar tapes.
TYPETMS5 16.129 Major revision of TMS/CA-1 processing logic.
TYPETMS5 16.191 Final revisions to TMS logic changes for FILSEQ.
TYPETMS5 16.251 TMS support for multi-dataset tapes now correct.
TYPETMV2 16.212 TMON for MVS V2 variables wrong in TMVSSYS dataset.
TYPETPMX 16.189 Enhanced TPM support reads all possible variables.
TYPETPX 16.019 TPXBYTI/BYTO wrong due to CA's documentation error.
TYPEVLFC 16.089 Zero observations in dataset TYPEVLFC corrected.
TYPEVMXA 16.310 Support for VM/ESA 2.3 MTRSYS and USEACT segments.
TYPEWWW 16.105 Support for Web Proxy logs Extended Common Log fmt.
TYPEXCOM 16.114 XCOM variable REQTYPE renamed REQTYPEX, conflict.
TYPEXCOM 16.187 Support for XCOM Release 3.0 (COMPATIBLE).
USMFRATE 16.158 Analysis of SMF Write Rates (MEGABYTES at 10/100sec)
UTILBHEX 16.070 Utility creates SMF records from hex dump from LIST;.
UTILCICS 16.061 Incorrect Candle value ERRMQ=64 in CANMQ detected.
VMAC7072 16.130 Type 70 records have CPU segment after VARY OFF.
VMACIMSA 16.313 IMS 6.1 type 08 correction for APPC, CPIC driven.
VMXGSUM 16.120 New ERASEOUT parameter added.
VMXGSUM 16.131 UNIX forward slashed caused VMXGSUM to fail.
VMXGSUM 16.146 VMXGSUM syntax for "DATETIME" now uses real name.
VMXGSUM 16.179 Support for SAS Version 7 (INCOMPATIBLE).
VMXGSUM 16.306 INHERIT (SAS V7 only) now exploited in VMXGSUM.
VMXGSUM 16.306 INHERIT parameter used if under SAS Version 7.
VMXGSUM 16.323 Correction after Change 16.271 &DATETIME=DATETIME;
VMXGWORL 16.266 Sorted status now validated by SORT flag for _L data.
WEEKBLDT 16.140 Weekly build of ASUMDB2B fails with wrong sort order.
XMXGSUM 16.314 New function enhancements for VMXGSUM for testing.
YEAR2000 16.330 MXG 16.09 now required for 100% YEAR2000 Support.
Inverse chronological list of all Changes:
Look for additional changes in MXG 16.16 in member CHANGES.
While this newsletter was being printed, changes may have been made.
Changes 16.222 thru 16.367 were printed in MXG Newsletter THIRTY-FIVE,
and are listed in member CHANGESS.
Changes 16.221 thru 16.001 were printed in MXG Newsletter THIRTY-FOUR,
and are listed in member CHANGESS.