* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
(the 20th century) and will contain '01' in the 21st century. Therefore, for any NPM record, it is always possible to identify the century" but nothing in that Informational APAR said that the 99 internal date values (like start and stop times!) were changed to CYYMMDDF, which is a new brand new date format that exists in no other SMF record, and that new format causes an INVALID ARGUMENT error when MXG 15.15 read NPM records with year 2000 dates. So NPM users do in fact have to do something special - they now have to install (unnecessarily) a new version of MXG because the NETVIEW NPM product did not document their INCOMPATIBLE changes to type 28 SMF records!
another unique date format of "MM/DD/YY.DDDHH.MM.SS" which does not have room for a "century" nybble, so NPM is still NOT YEAR 2000 READY. However, by adding MXG windowing protection (YY LE 59) for LXETTMST, I have now changed member YEAR2000's NPM entry to move NPM from the "IS NOT" to "NOW IS" YEAR2000 compliant, even though NPM really is not compliant without help from MXG logic. Finally, the implication in the Informational APAR that only the date field in the SMF header needs a century bit to be "YEAR 2000 READY" is inaccurate. To truly be YEAR 2000 READY requires that each date value be complete and self-described. A record that requires programming logic to test one date field to then set the date of another date field (which may or may not have been on the same date as the first date value) is not YEAR 2000 READY. That IBM ultimately had to change all 99 internal fields shows that setting only the century bit in the SMF header was not sufficient!
an error in NPM's computation of leap years; without that APAR, NPM incorrectly thinks 2000 is not a leap year. This extensive MXG change inserted seven new lines for each of the ninety-nine date values to decode the new format, and exists only because CIGNA found the data values in their year 2000 test partition's type 28 data. Thanks to Steve Colio, CIGNA, USA. Change 16.002 IDMS 14.0 new variables TASNINS,TASNUPD,TASNDEL,TASNSRT VMACIDMS TASNSRR,TASNSMI,and TASNSMX had incorrect labels, and new Mar 3, 1998 variable TASNAMC was not created. TASNAMC is now INPUT as &PIB.4. following TASNSMX and the labels corrected. Thanks to Chris Weston, SAS Institute Cary, USA.
VMACNTSM NETWINTR for consistency with PKRCNONU, but variable Mar 3, 1998 PKSENOUN is still built, so your old programs won't fail. Thanks to Marti Henley, MatriDigm, USA. LASTCHANGE: Version 16 =========================member=CHANGE15================================ /* COPYRIGHT (C) 1984-1998 MERRILL CONSULTANTS DALLAS TEXAS USA */
Second MXG Version 15.09 - dated Feb 17, 1998, thru Change 15.384. First MXG Version 15.09 was dated Feb 16, 1998, thru Change 15.382. Newsletter THIRTY-TWO was dated Feb 23, 1997, thru Change 15.382. MXG Version 15.08 was dated Jan 15, 1998, thru Change 15.340. MXG Version 15.07 was dated Dec 18, 1997, thru Change 15.311. MXG Version 15.06 was dated Nov 24, 1997, thru Change 15.287. MXG Version 15.05 was dated Oct 02, 1997, thru Change 15.238. Newsletter THIRTY-TWO was dated Sep 12, 1997, thru Change 15.206. MXG Version 15.04 was dated Sep 01, 1997, thru Change 15.206. Final+ MXG Version 15.03 was dated Jun 30, 1997, thru Change 15.151. Final MXG Version 15.03 was dated Jun 26, 1997, thru Change 15.148. Second MXG Version 15.03 was dated Jun 25, 1997, thru Change 15.145. First MXG Version 15.03 was dated Jun 24, 1997, thru Change 15.144. MXG Version 15.02 was dated May 23, 1997, thru Change 15.103. MXG Version 15.01 was dated May 6, 1997, thru Change 15.087. Newsletter THIRTY-ONE was dated Feb 21, 1997, thru Change 14.343.
II. MXG Technical Notes III. MVS Technical Notes. IV. DB2 Technical Notes. V. IMS Technical Notes. VI. SAS Technical Notes. VII. CICS Technical Notes. VIII. Windows NT Technical Notes. IX. Incompatibilities and Installation of MXG 15.15. X. Online Documentation of MXG Software. XI. Changes Log
along with the printed copy of MXG Newsletter THIRTY-THREE, during the last week of February, 1998, by US Air Mail.
Support for RMF Monitor III CPU, PGP, ENC records. Support for TME 10 Netview OS/390 1.1 SMF type 37.
Support for AIX commands IOSTAT/PSSTAT/VMSTAT output into SAS. Support for StorageTek's VSM SMF records subtypes 9 thru 25. Support for IDMS Journal format for IDMS V12. Support for Boole's IMF 3.2 (for IMS 6.1) INCOMPATIBLE Landmark TMON for CICS V2 variables renamed. Landmark for MVS V2 INPUT STATEMENT EXCEEDED. New &MACxxxx macro variable added to all VMACs to override IMACs. All VMACs for SMF records now start with IF ID=....
Support for AS/400 - OS/400 Release 4.1.0 (INCOMPATIBLE). Support for ICSS SMF type 103 (Internet Connection Secure Server). Support for RMF type 79 subtype 15 (IMS IRLM Long Lock) record. Hardcoded "PDB." DDname externalized into &PDBxxxx macro variables. ASUMUOW option to get real TRANNAME instead of CPMI/CSMI tranname. Performance improvements in BUILDPDB (_CDE's ordered, ELSE DOs). New _Sxxyyy "PROC SORT" macros defined for PDB datasets in IMACs. Major enhancements added in MXG 15.07 dated 18Dec1997: Support for DPPX/370 Performance Reporter output. Support for MODEL204 Version 3.4 INCOMPATIBLE. Support for SAR CA-VIEW SMF exit SARSRQUX. Support for Omegamon for VTAM V400 (COMPATIBLE). Support for Landmark the Monitor for MVS Version 2 (INCOMPATIBLE). Support for SAR CA-VIEW SARSRQUX SMF record. Support for Fujitsu's AIM V20 AIM/RDBII SMF type 98 record. ASMTAPES ML-15 adds dump suppression, OS/390 1.3 JCT changes. (MXG 15.06 said it contained ML-15, but actually still had ML-14). VELOCITY variables are now multiplied by 100. Major enhancements added in MXG 15.06 dated 24Nov1997: Support for CICS Transaction Server 1.2, INCOMPATIBLE. IBM inserted new fields in the middle of CICSTRAN record, so you must install MXG 15.06 or later for CICS TS 1.2 processing. New statistic data is also captured; see Change 15.274. Support for Landmark's The Monitor for CICS/ESA 2.0, INCOMPATIBLE. CICS TS V1.1 APAR UN98309 INCOMPATIBLE, Must install MXG 15.06. Support for NTSMF Version 2.1 (INCOMPATIBLE), install MXG 15.06. CICINTRV logic validated, must use this newest revision. Duplicate CICS UOWTIME values due to SAS non-resolution of DATETIMEs. Support for Subtype 11 Type 88 System Logger. Support for Applied Expert Systems Clever TCP/IP. Support for HP MeasureWare for Terra Data OS. Support for DFSORT APAR PN71137 (COMPATIBLE). Support for HP MeasureWare for Terra Data OS in TYPEMWTE. Support for Boole & Babbage MQ Series MVMQS VSAM History Records. OS/390 R2.4 Goal Mode IBM Doc Error INVALID DATA R723CIDT fixed. New IHDR110 exit for CICS record selection by APPLID. Utility to recreate VBS from data with no RDW/BDW. Major enhancements added in MXG 15.05 dated 02Oct1997: Support for JES3 TYPE26 APAR OW26297 adds account fields. Support for APPC APAR OW16975 APAR-in-Error (INCOMPATIBLE). Support for 255 Structures in a Coupling Facility (INCOMPAT). Support for CA's IDMS 14.0 (INCOMPATIBLE). Support for BETA93 Release 1.3 (INCOMPATIBLE) (subtype 21 only). Support for SMF type 91 new subtype 21 (SmartBatch) data. Support for TCP/IP 3.2 API Calls record changes. Duplicate MULTIDD='Y' step records may not be deleted in BUILDPDB. Catalog SMF Type 65 record INPUT STATEMENT EXCEEDED corrected. PDB.ASUMUOW options externalized, zero obs now created by default. DB2 Trace 102 subtype 140 INPUT STATEMENT EXCEEDED. Iceberg / IXFP subtypes 2,3,4 not output, MXG 15.02-15.04 only. TYPE70 variable PCTMVSBY incorrect in MXG 15.01-15.04.
Support for OS/390 Version 2 Release 4 (COMPATIBLE). Support for "Goal Mode SMF" type 99 subtype 6. Support for DCOLLECT in DFSMS 1.4 (COMPATIBLE) Support for VTAM 4.4 changes to SMF type 50. Support for CA-1/TMS Release 5.2 (COMPATIBLE). Support for ObjectStar 3.0 (INCOMPATIBLE in MXG). Support for Xerox's XPSM Version 2 SMF records. Support for HMF SMF Subtype 11 (DS3 Statistics). Support for five new NTSMF Objects. Support for VM ADSM Account Records in VM/ESA. Support for TMON/DB2 record type "DE". Support for Boole MainView for CICS stat records. Support for Catalog Cell 'E7'(Alias) and invalid '05'x segment. Support for RACFEVNT=22 and 59 in TYPE80A. Support for Shared Medical CICS Journal OASMON records. Support for Peregrine's Service Center SMF record. Table of Holidays for SHIFT example added in IMACSHFT. Major enhancements added in MXG 15.03 dated 30Jun1997: Support for NTSMF Version 2.0 (INCOMPATIBLE; 15.02 was not correct). Support for Windows NT 4.0 Service Pack 2 (INCOMPATIBLE also). Support for IXFP SMF subtypes 6 and 7 (SNAPSHOT, SPACE UTILIZATION) Support for TYPE1415 APAR OW25263 (for 3590s). Support for TYPE42 APAR OW26451/OW26543/OW26497 MAXRSPTM added. Support for TYPE42 APAR OW20921 adds TYPE42VT VTOC/VVDS counts. Support for OMVS RACF data with RACF utility IRRDBU00. Support for new fields in TYPEEDGR DFSMSrmm extracts. ASMTAPES at ML-14 populates fields, protects 0C4 ABENDs better. RMFINTRV now allows Report RPGNs/Classes to be used in IMACWORK. Format MGBYTRT (Bytes per Second) can truncate value on the left. BUILDPDB enhanced to rename WORK.STEPS for IT Service Vision. Leap second support for type 30, 110, and 100-102 "GMT" conversion Trending for TYPE72GO into TREND.TRND72GO added. ANALCNCR Example counts Avg & Max Logged-ON TSO users from PDB.JOBs.
Support for Filetek's Optical Disk SMF record Support for OMVS data in RACF database (IRRDBU00 unload) Enhancements to VMXGSUM for OBS=0 processing Replacement for MXG 15.01's defective CICINTRV. ASMTAPES Technical Note updated - cause of 0C4 is now known. Major enhancements added in MXG 15.01: Errors in MXG 14.14 that are fixed in MXG 15.01: ASMTAPES (ML13) is available, recovers from 0C4s, see MXG Tech Notes. WORK.CICINTRV.DATA DOES NOT EXIST. OS/390 R3 Goal only: Type 72 INPUT STATEMENT EXCEEDED RECORD LENGTH. FILE counts in TYPETMON were incorrect before and after 14.14. New Support in MXG 15.01: ANALDDCN to analyze impact of DDCONS(NO) on duplicated SMF bytes TYPEIMSD for IMS DBCTL transactions from IMS 07/08 log records SMFPRM00 with first draft of MXG discussion for SMF parameters Support and exploitation of new TALO fields added by ASMTAPES ML-12. Support for APAR OW25152 (adds PRINTWAY Queue Name to TYPE6). Support for Altai's ZARA Tape Management Release 1.2 Support for Anacom's Anastack spooler's type 6 SMF Support for Boole and Babbage IMF 3.2. Support for CA-DISPATCH Version 6 with 5-digit JESNR Support for CA-ROSCOE Version 6 SMF record verified. Support for COMPAQ hardware NTSMF objects. Support for Hitachi 7700 changes to TYPE74CA/CACHET90 (INCOMPAT) Support for Landmark's Performance Works/Smart Agents for UNIX 4.0 Support for MEMO subtype 8 creates new MEMODIST dataset. Support for NETSPY Version 5.0 is already in MXG 14.14 Support for Virtual Tape Server additions to SMF type 94 Support for World Wide Web Common Log Format records. Support for all OS/400 Release 3.7.0 records. UDUMPEBC utility for MVS-like LIST; hex dump under ASCII systems.
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 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 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 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 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 ??? ??, 1996. 15.08 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 AS400 3.7.0 Nov 1, 1996 15.01 AS400 4.1.0 Dec 30, 1996 15.08
Product Name Date or Change Required Microsoft Windows NT 4.0 and NT 3.51 14.14 Windows NT 4.0 Service Pack 2 15.03 Demand Technology NTSMF Version 1 Beta 14.11 NTSMF Version 2.0 15.03 NTSMF Version 2.1 15.06 Landmark
The Monitor for DB2 Version 2 13.06 The Monitor for DB2 Version 3 15.03 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 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 SMS V100/V110 12.03 CA ASTEX 2.1 14.04 NETSPY 4.7 14.03 NETSPY 5.0 14.03 Boole & Babbage IMF 3.1 (for IMS 5.1) 12.12 Memorex/Telex LMS 3.1 12.12A II. MXG Technical Notes
%INCLUDE SOURLIB(ASUM70PR); as shown in JCLPDB6 example. There is one observation in ASUM70PR from each MVS SYSTEM for each RMF Interval, and that observation describes the utilization of each of the LPARS, and their sum, which is the hardware busy of the platform. If you have multiple MVS Systems, and if you process their SMF data together, then duplicate data will exist in ASUM70PR, since SYSA's type 70 record will describe all LPARs, and SYSB's type 70 will also describe all LPARs, so you must select only one set of observations (from SYSA or from SYSB) to avoid duplication. For each partition, the Partition Dispatch Time and the Effective Dispatch Time (and their difference, the CPU time when this partition was dispatched for LPAR management of this partition) are recorded. There is also a "pseudo" partition named "PHYSICAL" that exists only in the RMF type 70 record that records the LPAR management dispatch time that could not be charged to a specific partition. Schematic of ASUM70PR observation
CPUACTTM= LPnUPDTM summed for all real partitions + LPPUPDTM CPUACTTM |______________________________________________________________| | |
| LP1UPDTM | LP2UPDTM | LP3UPDTM | LPPUPDTM | | Dispatched | Dispatched | Dispatched | Dispatched | |_______________|_______________|_______________|______________| | | | | | | | | | | LP1UEDTM | | LP2UEDTM | | LP3UEDTM | | | LPAR1 | | LPAR2 | | LPAR3 | | | Effective | | Effective | | Effective | | | | |
| | | | | | | | 1 2 3 "Physical" LP1MGTTM LP2MGTTM LP3MGTTM LPPUPDTM In-partition LPAR Management Time Unassigned LPAR time
LPnUEDTM - Partition Effective Dispatch Duration for LPAR n. LPnMGTTM - LPnUPDTM minus LPnUEDTM, this partition management. LPPUPDTM - Physical partition dispatch duration. PARTNCPU - Number of engines in this platform. PCTCPUBY - Percent CPUs were Busy in all LPARS, equal to the sum of all partition's (including PHYSICAL) dispatch time, minus HiperDispatch Parked Time, divided by the Total "capacity" of all ONLINE, NON-PARKED engines: 100*CPUACTTM/(NRCPUS*DURATM). This is the percent of the total capacity of the box that was used. If the Average NRCPUS is 5.5, and CPUACTTM was 4 hours in a one hour interval, PCTCPUBY would be 72% busy. PCTLnBY - Percent "Physically" Busy in LPAR n, equal to the LPAR Dispatch time divided by the Total "capacity" of all engines in the box: 100*LPnUPDTM/(PARTNCPU*DURATM). If an LPAR was dispatched for 1 hour, and the CEC has 5 engines, then PCTLnBY for that LPAR would be 20%, because that LPAR used 20% of the hardware platform. PCTLnOV - Percent "Phsyically" Busy in "LPAR Overhead" in this LPAR, 100*LPnMGTTM/(PARTNCPU*DURATM). LPnNRPRC - Number of engines available to LPAR n. LPnDUR - LPAR n's "Up time" or "Availability time to execute CPU", the sum of DURATM across all LCPUs in LPAR n, or LPnDUR=LPnNPRC*DURATM. This is the duration when this LPAR could have been dispatched. If the LPAR was IPLed as a 3-engine MVS machine, in one hour, it would have 3 hours of "Up Time" (or 3 hours of "capacity"). LPCTnBY - Percent "Logically" Busy in LPAR n, equal to the LPAR Dispatch time for the partition divided by the LPAR's "Up Time", 100*LPnUPDTM/LPnDUR. If a 3-engine LPAR was dispatched for 60 minutes in one hour, its LPCTnBY would be 33%. This variable describes the percent of LPAR capacity, in contrast to variable PCTLnBY which describes the percent of Hardware Platform capacity. If that same 3-engine LPAR was executing on a 5-engine CEC, PCTLnBY would be 20%, because that LPAR used 20% of the hardware platform, while LPCTnBY is 33% of the CPU time available to this LPAR. LPnCAP - 'Y' if this partition is capped. LPnCHG - 'Y' if something changed in LPAR n. LPnDED - 'Y' if this partition has all-dedicated-CPUs. LPCTnOV - Percent "Logically" Busy in "LPAR Overhead" 100*LPnMGTTM/LPnDUR, describes how much of the Dispatch Duration was for management of this LPAR.
LCPUPDTM - Partition Dispatch Time LCPUEDTM - Partition Effective Dispatch Time
Electronic Complex, the preferred name for a platform). This CEC has three LPARs: LP1 has two engines (and is lightly used), LP2 has five engines, and LP3 has three engines. All CPUs are shared and Wait Completion is No. One hourly observation in ASUM70PR showed:
DURATM 1:00:00.05 - Duration interval CPUACTTM 4:40:35.32 - Total CPU Dispatch, all engines CPUOVHTM 15:35.40 - Total CPU Overhead in LPARS LPPUPDTM 6:40.28 - Total "Physical" Overhead PCTCPUBY 93.53% - CPUACTTM as a percent of hardware PCTOVHD 5.20% - CPUOVHTM as a percent of hardware PCTPOV 2.22% - LPPUPDTM as a percent of hardware LP1 LP2 LP3 LPnNRPRC 2 5 3 LPnDUR 2:00:00.10 5:00:00.25 3:00:00.15 LPnUPDTM 4:49.67 3:33.06.54 55:58.85 LPnUEDTM 2:56.63 3:29:16.51 52:46.77 LPnMGTTM 1:53.03 3:50.02 3:12.07 LPCT1BY 4.02% 71.04% 31.10% LPCT1OV 1.57% 1.28% 1.78% PCTL1BY 1.61% 71.04% 18.66% PCTL1OV .63% 1.28% 1.07% The LP2 has the same PCTL2BY as LPCT2BY because it can use all five engines, and its logical and physical utilization are the same. The LP3, with only three engines available to its MVS, shows it is using 18.66% of the five hardware engines (PCTL3BY), while LPCT3BY shows that this actually is 31.1% of the CPU time possible for those three logical CPUs available to LP3.
describing the total platform busy and each LPARs use of the total, because when an LPAR is dispatched, its processors are not available to any other LPAR, and thus ASUM70PR does report platform capacity. Furthermore, if all CPUs are shared and Wait Completion is No, the ASUM70PR dispatch duration is the actual CPU busy time, so not only Yüklə 28,67 Mb. Dostları ilə paylaş:
|