See member ADOC110 for the new note on CPU capture in the
CICSTRAN, CICDS/CICINTRV, SMFINTRV and TYPE72/72GO data,
which provides a schematic of what's captured where.
Thanks to Trevor A. Holland, TELSTRA, AUSTRALIA.
Change 19.013 Support for TLMS Release 5.5 (COMPATIBLE). Two new
VMACTLMS variables, BACUNIT (Create Unit) and BALUNIT (Last Unit)
Feb 23, 2001 were added compatibly at the end of the record; both of
these new fields were actually added back in Release 5.4.
Thanks to Jon Whitcomb, Great Lakes Higher Education Corp, USA.
Change 19.012 Change 18.348 created QWACALOG/AWCL/AWAR/OCSE/SLSE/DSSE/
ASUMDB2A OTSE/IXLT from QWAX variables, but did so incorrectly,
VMACDB2 they were not formatted as TIME12, and ASUMDB2A was not
Feb 23, 2001 revised to include the QWACs instead of the QWAXs.
Apr 4, 2001 Line 105 in 18.18's ASUMDB2A was removed to eliminate the
"duplicate variables" message (but it had no impact).
Thanks to Chris Weston, SAS Institute ITSV, USA.
Change 19.011 MXG 18.18 only, new variables only. Incorrect SUBSTR()
VMXGRMFI argument caused CPCNRCPU to be missing, CPFCNAME could
Feb 19, 2001 have extraneous characters, CPUTYPE='2064'x was not found
Mar 1, 2001 in the MG070CP table because CPCMODE3='404040'x should be
removed. The correct block of code now reads:
END;
CPUSTUFI=CPUTYPE!!CPUVERS1!!CPCMODE3;
CPUSTUFO=PUT(CPUSTUFI,$MG070CP.);
IF CPUSTUFO NE CPUSTUFI THEN DO;
CPCMSU =INPUT(SUBSTR(CPUSTUFO,1,4),4.);
CPCFNAME=SUBSTR(CPUSTUFO,6,8);
CECSUSEC=INPUT(SUBSTR(CPUSTUFO,15,10),10.);
CPCNRCPU=INPUT(SUBSTR(CPUSTUFO,26,2),2.);
SMF70WLA=CPCMSU*NRCPUS/MAX(CPCNRCPU,PARTNCPU,NRCPUS)
END;
No change was made to the logic in member FORMATS that
creates the MG070CP format, but comments that describe
that format's format were revised to match the format.
Note: This correction only applied if the FORMAT was
used. If SMF70WLA was populated, the FORMAT is
not used. But Change 20.168 is then needed.
Thanks to Pat Curren, SuperValu Inc, USA.
Change 19.010 The FTPREPLY character variable contains '000000FA'x, but
VMACTCP is converted by this change to ' 250', its numeric value
Feb 19, 2001 in a character variable, by inserting this statement
FTPREPLY=PUT(INPUT(FTPREPLY,&PIB.4.),4.);
and by changing the input from $EBCDIC4. to $CHAR4. to
prevent conversion of the binary value.
Using $CHAR versus $EBCDIC under OS/390 doesn't matter
here, but under ASCII, leaving the $EBCDIC4. informat
would convert any binary value that happened to be a
valid EBCDIC character into its ASCII equivalent:
(eg: '0000C1FA'x becomes '000041FA'x when INPUT with
$EBCDIC4. informat under ASCII SAS.)
Now the Reply values for the Client (FTPREPLY) will be in
the same format as the Server (FTPRSRSR) reply.
Change 19.009 Support for CA/TNG post-9907 (INCOMPAT). The initial MXG
VMACTNG support was for the "old" data records, which had simple
Feb 19, 2001 data format, but CA's complete revision (with internal
version 6 or higher), with its base-36 counting and with
repeat-count counters, is now supported with this change.
Thanks to Roman Jost, Gjensidige, NORWAY.
Change 19.008 Variable SYNCNAME was added to the KEEP= for IMS597 so
VMACIMSA that variable PROGRAM will be populated in Fast Path
Feb 19, 2001 dataset.
Thanks to Bruce Widlund, Merrill Consultants, USA.
Change 19.007 MXG 18.18 only. The BY statement in _SHPSUGL was missing
VMACMWSU its ending semicolon, and the extra semicolon at the end
VMACMWUX of MACRO _BHPUXDS was removed.
Feb 19, 2001
Change 19.006 The calculation of RDHITPCT in TYPE42DS was incorrect in
VMAC42 the denominator; the revised equation is:
Feb 19, 2001 RDHITPCT=(CACHHITS-WRITHITS)/(CACHCAND-WRITCAND);
The previous denominator was just CACHCAND and the value
calculated was too low.
Thanks to Ep van der ES, Dow Chemicals, BELGIUM.
Change 19.005 NTSMF files that have been COPYed and APPENDed without
VMACNTSM the /B parameter (search NEWSLTRS) and/or concatenated on
Feb 16, 2001 MVS have been found with a record of nulls (hex zeroes)
that MXG did not expect. This change detects and deletes
those records, printing a message that these bad records
were found in your input.
Thanks to Howard Glastetter, Weyerhaeuser, USA.
Change 19.004 SAS does not permit an ARRAY name to be the same as a
VMACSYNC variable name; a new ARRAY named DD defined in VMACSYNC
Feb 16, 2001 conflicted with a variable named DD in VMACRMDS, (only
if you tailored MXG to process both RMDS and SYNCSORT SMF
records in the same MXG datastep). Changing the ARRAY
names in VMACSYNC transparently corrects the conflict.
Thanks to Chris Weston, SAS Institute ITSV, USA.
Change 19.003 IMS Version 7 requires Omegamon/IMS V500, but Candle says
TYPEITRF the upgrade from V300 to V500 is transparent as far as
Feb 14, 2001 their ITRF data records are concerned.
Thanks to Gene Quinn, Blue Cross of Rhode Island, USA
Change 19.002 Two new VGETxxx %MACROs were included in MXG 18.18 but
VGETENG they (and the new VGETxxx prefix) were not documented.
VGETOBS %MACROS that "Get" and return a value are named VGETxxx,
VMXGENG and the value "got" is returned in a macro variable that
Feb 14, 2001 is named VGETxxx. The two new implementations are:
Executing Will return
%VGETENG(DDNAME=yyyyyyyy); The Name of the SAS Engine
that created that yyyyyyyy
data library, in &VGETENG.
(Needed by MXG so we can
exploit V8 features.)
%VGETOBS(DDNAME=,DATASET=); The number of observations
in dataset DDNAME.DATASET
in &VGETOBS.
The earlier %VMXGENG macro still exists for compatibility
but it now invokes %VGETENG.
Thanks to Chuck Hopf, MBNA, USA.
Change 19.001 The _BTY30UV BY list in VMAC30 was not quite the same as
VMAC30 the order needed in BUILDPDB, and was corrected to be:
Feb 12, 2001 MACRO_BTY30UV READTIME JOB JESNR INITTIME INTETIME
DESCENDING INTBTIME MULTIDD EXTRADD %
(Note that SMFTIME is appended during the initial NODUP
sort in _STY30UV sort, but is not needed subsequently.)
Thanks to Barry McQueen, Department of Defence, Australia.
LASTCHANGE: Version 19.
=========================member=CHANGE18================================
/* COPYRIGHT (C) 1984-2001 MERRILL CONSULTANTS DALLAS TEXAS USA */
MXG Version 18.18 is dated Feb 12, 2001, thru Change 18.360.
MXG Newsletter THIRTY-EIGHT is dated Feb 12, 2001.
MXG Version 18.12 was dated Jan 30, 2001, thru Change 18.341.
MXG Version 18.11 was dated Jan 4, 2001, thru Change 18.315.
First MXG Version 18.10 was dated Dec 20, 2000, thru Change 18.303.
MXG Version 18.09 was dated Oct 24, 2000, thru Change 18.264.
MXG Newsletter THIRTY-SEVEN was dated Oct 24, 2000.
MXG Version 18.08 was dated Sep 25, 2000, thru Change 18.238.
MXG Version 18.07 was dated Aug 31, 2000, thru Change 18.217.
First MXG Version 18.07 was dated Aug 30, 2000, thru Change 18.216.
Test MXG Version 18.07 was dated Aug 27, 2000, thru Change 18.204.
MXG Version 18.06 was dated Jul 28, 2000, thru Change 18.177.
MXG Version 18.05 was dated Jul 1, 2000, thru Change 18.154.
MXG Version 18.04 was dated May 15, 2000, thru Change 18.109.
Final MXG Version 18.03 was dated Apr 17, 2000, thru Change 18.086.
MXG Version 18.03 was dated Apr 12, 2000, thru Change 18.083.
First MXG Version 18.03 was dated Apr 11, 2000, thru Change 18.081.
Final MXG Version 18.02 was dated Mar 29, 2000, thru Change 18.052.
Second MXG Version 18.02 was dated Mar 16, 2000, thru Change 18.046.
First MXG Version 18.02 was dated Mar 15, 2000, thru Change 18.043.
MXG Version 18.01 was dated Mar 3, 2000, thru Change 18.021.
MXG Version 17.17 was dated Feb 7, 2000, thru Change 17.398.
Newsletter THIRTY-SIX was dated Feb 7, 2000, thru Change 17.398.
Contents of member CHANGES:
Member NEWSLTRS (and the Newsletters frame at http://www.mxg.com) now
contain the current MXG Technical Notes that used to be put in member
CHANGES between Newsletters. New Technical Notes are now added (and
now dated!) in NEWSLTRS/Newsletters with each new MXG Version.
I. MXG Software Version 18.18 was shipped to all MXG licensees.
II. Incompatibilities and Installation of MXG 18.18.
III. Online Documentation of MXG Software.
IV. Changes Log
=======================================================================
I. MXG Software Version 18.18 is the annual version, Feb 12, 2001, and
it was sent to all MXG sites, and contains NEWSLETTER THIRTY-EIGHT.
Major enhancements added in MXG 18.18:
Support for z/OS Version 1.1 (COMPATIBLE).
Support for CICS/TS for z/OS Version 2.1 (INCOMPATIBLE).
Support for DB2 Version 7.1 (COMPATIBLE).
Support for Vital Signs VisionNet VSV TCPIP stats.
Support for Innovation Data Processing's FDR SMF.
Support for SYNCSORT Release 3.7 (COMPAT).
Support for IBM TapeTools MOUNTMON user SMF record.
ASUMTALO MAXDRVS greater than installed tape drives corrected.
New MACRO _Vdddddd KEEP=x y z %; finally makes KEEP= easy.
Major enhancements added in MXG 18.12:
Support for CA UNICENTER TNG AIX, CISCO, NT, and SOLARIS objects.
Support for SOLVE SMF Subtypes 1 and 2.
Support for SHADOW SMF Subtype 6.
Support for IBM Domino WebServer Logs enhanced.
Support for DFSMSRMM 1.5 changes (COMPATIBLE).
Major enhancements added in MXG 18.11:
Support for DB2 Space Manager 2.1 (INCOMPAT).
Support for NPM APAR OW45788 corrects LXETxxxx.
Scheduling Environment variables added to PDB.JOBS
MXG execution under SAS V8.1 notes consolidated in NEWSLTRS member.
Documentation of the Internal Logic of BUILDPDB in DOCPDB member.
Erroneous EXCLUDED FIELDS message, MXG 18.10 only, TS 1.3 only.
Major enhancements added in MXG 18.10:
RMFINTRV now calculates MSU4HRAV 4-hour running MSU avg for z/OS.
DB2ACCT variable DB2TCBTM included Stored Proc AS CPU time twice.
Support for MQ Series V5.2 (INCOMPATIBLE) SMF 115 and SMF 116.
Support for Websphere Appl Server (EE) Component Broker SMF 120.
Support for TMON for MVS 2.0 NQ records corrected.
Support for ANALRMFR to create HTTP Server Report from SMF 103.
Using IMACJBCK for DB2ACCT selection saves CPU time
NPM Type 28 Subtype 'DC'x caused INPUT EXCEEDED.
CICINTRV request for "EOD" did not sum correctly.
CICS 1.3 SAP Journal records in CICSJOUR vice CICSSAP
Support for Vital Signs VisionNet VSAM file.
Short JES3 type 6 record protected.
Support for APAR OW37743 corrected.
CICINTRV DSA size variables corrected.
Support for NETVIEW SMF 38 APAR OW45728.
Major enhancements added in MXG 18.09:
Support for NPM APAR OW37743 (INCOMPATIBLE if TIC3 and 3746).
Support for Neon System's Shadow Server V4.5 SMF record.
Support for NTSMF ADSM, ColdFusion, MQSeries, WorldSecure objects.
Support for Candle's Omegamon for VTAM TCP record.
TYPE74 PCTDVUSE,PCTDVCON, etc for PAV Volumes now less than 100%.
GRAFWORK/GRAFRMFI/GRAFTAPE SAS/GRAPH examples now output as HTML
TYPE70 variable CPCMODEL ('RX6') added, was already in TYPE70PR.
Format $MGSASPR maps SAS PROC name to Product name, for SAS SMF.
Major enhancements added in MXG 18.08:
Support for Landmark TMON for VTAM.
Support for Landmark TMON for DBCTL.
Support for Omegamon for VTAM V500 (COMPAT).
Support for Enterprise Data Access, EDA, SMF record.
Support for AS/400 Collection Services records.
Summarization/Trending for STC datasets.
ANALUAFF finds wasted tape drives for SORT without UNIT=AFF.
Major enhancements added in MXG 18.07:
Support for OS/390 R2.10 (INCOMPAT!). See Change 18.134.
R2.10 support was included in MXG 18.06, although there was no
statement of support in that Version, and the Change text was
"Reserved". MXG 18.06 or later is required for OS/390 R2.10.
Support for BMC MainView for MQ Series History File V2.1.
Support for APAR II11493 (INCOMPAT) type 50 SMF.
Support for APAR PN61399 TCP type 118 SMF.
Support for NTSMF object "SESSION", from Term Svcs.
Support for APAR OW45168 SMF type 94 confirmed.
Support for APAR OW43854, adds OPENTIME to SMF 62 and 64.
VMXGSUM revisions, VIEW used, can avoid I/O, can be big savings.
ASUMUOW revised, MQ Series added to DB2+CICS, VIEW used for speed.
TYPE71 Memory (Hi,Med,Low Impact Frames) now correct and useful.
Datasets TYPE7 and TYPE23 now automatically built by BUILDPDB/3.
Example ANALCNCR and PROC TABULATE create HTML format reports.
New %MACRO VMXGENG returns the ENGINE of a SAS dataset.
MXG Y2K error, BMC CICS Manager type 110 segment corrected.
Major enhancements added in MXG 18.06:
Support for OS/390 R2.10 (INCOMPAT!). See Change 18.134.
Support for OS/400 Release 4.5.0 (INCOMPATIBLE).
Support for IHS WEBSERVER SMF 103 APAR PQ32435, adds JOB/ASID.
Support for BETA93 Release 321 INCOMPATIBLE subtype 1 record.
Revised support for TYPEEDGS/TYPEEDGB for DFSMS/rmm.
TCP SMF 118 Bad Record INPUT STATEMENT EXCEEDED corrected (again).
SAS Version 8.1 causes Condition Code 4 and prints log message:
WARNING: ARGUMENT 3 TO MACRO FUNCTION %SUBSTR IS MISSING
because the length of their &SYSVER Version macro was shortened
from four to three. There is no execution impact, fortunately,
except that the warning causes MVS Condition Code/Return Code of
four instead of zero, and wastes your time in reading this!
See further discussion in Change 18.159 which revises MXG.
Major enhancements added in MXG 18.05:
Support for Domino Server R5.0.3 subtypes 2 and 6.
Support for Type 42 RLS Subtype 19 enhanced, fixed.
Support for COM Tran Integrator, TN3270 Server, etc.
Support for new NTSMF Objects in Windows 2000 Server.
Support for IBM Websphere SMF type 103 subtype 2 undoc field.
Support for 3494 Peer-to-Peer (Gemini).
Support for APAR OW41317 support, INCOMPAT R2.7, R2.8, R2.9.
IMS Log Version 5.1 caused zero obs in IMSTRAN in TYPEIMSA.
ANALSMJB Who is filling your active VSAM SMF file utility.
MEMSIZE removed, S=72,S2=72 restored to CONFIGV8.
Trending of NTSMF LOGLDISK for NT disk space in TRNDNTLD.
Additional ESS variables now decoded from type 6.
Summarize TYPETCPT to track concurrent users in ASUMTCPT.
Major enhancements added in MXG 18.04:
SAS V8.0/V8.1 errors can corrupt variable labels in tape datasets
built by the V8SEQ "tape" engine. Until the errors are fixed, I
strongly recommend that you change the default "tape" engine to
V6SEQ instead of V8SEQ (by adding SEQENGINE=V6SEQ to the CONFIGV8
member in your CONFIG concatenation, and by changing any LIBNAMEs
with "TAPE" engine specified to "V6SEQ", as discussed in the SAS
Technical Note 5 in Newsletter-to-be THIRTY-SEVEN (in NEWSLTRS &
in Newsletters on homepage), and in the text of Change 18.104.
Update July 26: SAS ZAP Z8002651 exists and corrects the error,
so that with that ZAP installed, the V8SEQ engine can be used.
TYPEIMSB correction for IMS 6.1 log processing.
Support for Roger Software Development RSD FOLDERS.
Support for MainView for CICS 5.3.01 (INCOMPATIBLE).
Major enhancements added in MXG 18.03:
Support for OS/390 Release 2.9 (17.17 support was not correct).
Support for NETSPY Release 5.3 (COMPATIBLE).
Support for CMA Release 1.11 (COMPATIBLE).
Support for OAM Release 1.5.0 (INCOMPATIBLE) SMF 85.
Support for Systemware SYSOUT X/PTR, JHS, MPS, and C/QUE.
IMS Log OTMA/APPC transactions supported, dates fixed in ASMIMSLx.
ASUM70PR/ASUMCEC with ICFs had PCTLnBY and LPnDUR wrong
ASUMTALO corrected for SPINning (in-flight) allocations.
KEEPALL= argument for VMXGSUM was externalized to a Global macro.
Major enhancements added in MXG 18.02:
Support for Tivoli Netview Performance Monitor NPM 2.5 (SMF 28).
Support for GUTS Gutenberg Time Sharing user SMF records.
Support for optional CICS RMI counters.
Support for Oracle Version 7.3.3 (INCOMPATIBLE)
Support for retrofit APAR OW41317 was in MXG 17.17
Support for type 21 APAR OW40414, added four byte fields.
Recognition and non-counting of ICF processors is now corrected.
Major enhancements added in MXG 18.01:
MXG 18.01 replaced MXG 17.17 for ITSV sites. Changes made in MXG
17.17 to BUILDPDB/BUILDPD3, RMFINTRV, and ASUMTALO members had not
been tested with ITSV when MXG 17.17 was shipped. Change 18.009.
Using Report Performance Groups or Reporting Classes in IMACWORK
to define the workloads in our RMFINTRV dataset did not work in
MXG 17.17; enhancements to VMXGRMFI (invoked in RMFINTRV) support
using any mixture of report/control/service class to define your
RMFINTRV workloads. Revised UTILRMFI can be used to discover any
overlap if you get the "CPU TIMES DO NOT MATCH" error message.
Support for DB2 6.1 Buffer Pools 100+ in DB2ACCT/DB2STATS.
Support for Type 79 Subtype 15 IRLM Long Lock now validated.
ASUMUOW adds DB2ELAP to output, corrects wait for SPUN UOWs.
You can now use (COMPRESS=YES) with MACRO _Ldddddd definitions.
Blank value in JOBCLASS corrected.
ANALDSET needed _NULL to be added to its DATA statement.
Invalid Y2K date in BETA93 product now protected.
Type 39 record INPUT EXCEEDED RECORD error corrected.
See member NEWSLTRS or the Newsletters frame at www.mxg.com for
current MXG Technical Notes that used to be in CHANGES.
MXG 18.18 has been tested with SAS 6.09, SAS V8.0 TS M0/M1 and V8.1.
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 15, 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
OS/390 2.7.0 APAR OW41317 Mar 31, 2000 18.03
OS/390 2.8.0 Aug 24, 1999 16.09
OS/390 2.8.0 APAR OW41317 Mar 31, 2000 18.03
OS/390 2.8.0 FICON/SHARK Aug 24, 1999 17.08
OS/390 2.8.0 APAR OW41317 Mar 31, 2000 18.03
OS/390 2.9.0 Mar 31, 2000 18.03
OS/390 2.10.0 Sep 15, 2000 18.06
OS/390 PAV Oct 24, 2000 18.09
z/OS 1.1 Mar 30, 2001 18.11
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 CICS/TS 1.2 Oct 27, 1997 15.06
CICS-TS V1R3 CICS/TS 1.3 Mar 15, 1999 17.04
CICS-TS for Z/OS Version 2.1 Mar 15, 2001 18.11
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 initial support Mar 15, 1999 16.09
DB2 6.1.0 all buffer pools Mar 15, 1999 18.01
DB2 7.1.0 Mar 30, 2001 18.11
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
DFSMS/MVS 1.5 ??? ??, 1999 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
MQ Series 2.1.0 Oct 2, 1999 17.07
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 17.01
NPM 2.5 Feb ??, 2000 18.02
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 Jul 4, 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
AS400 4.4.0 Sep 27, 1999 17.07
Availability dates for non-IBM products and MXG version required:
MXG Version
Product Name Required
SAS Institute
SAS V8 (TS M0), (TS M1):
(Read member NEWSLTRS (search 'V8') for other V8 notes.
MXG 16.16 runs, prints "options CODEPCT/BLKSIZE don't exist".
MXG 17.01 removed options in CONFIGv8 member, Change 17.073.
MXG 17.07 exploits 32K character var length, Change 17.253
MXG 17.08 exploits INHERIT option VMXGSUM, Change 17.265.
MXG 18.04 changes V8 default to SEQENGINE=V6SEQ. Change 18.104.
Microsoft
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
Windows 2000 Build 2195 17.10
Demand Technology
NTSMF Version 1 Beta 14.11
NTSMF Version 2.0 15.05
NTSMF Version 2.1 15.06
NTSMF Version 2.2 16.04
NTSMF Version 2.3 17.10
Landmark
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
Candle
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 CICS V500 User SMF 18.01
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 VTAM V500 18.08
Omegamon for SMS V100/V110 12.03
CA
ACF2 6.2 16.04
Dostları ilə paylaş: |