* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
transaction records. But VMXGUOW should not have failed when a variable in the sum list is deleted from your SMF record, so by inserting OPTIONS DKRICOND=NOWARN; and OPTIONS DKRICOND=ERROR; appropriately, VMXGUOW now only sums variables that are found in your CICSTRAN dataset. -UTILEXCL did not correctly recognize DBCTL and IMS data segments, causing messages "POSSIBLE CRITICAL ERROR" and UNKNOWN FILED CMODHEAD=PSB WAIT CMODNAME=USER UNKNOWN FILED CMODHEAD=DBCTL CMODNAME=DBCTL UNKNOWN FILED CMODHEAD=RMIDATA CMODNAME=DBCTL notes on the UTILEXCL log. The CICS dictionary lists the DBCTL/DBCTL fields as 64 individual 4-byte fields, while the DBCTL/RMIDATA field is a single field of 256 bytes; I believe both describe the same DBCTL data fields, and are processed by IMACICDB, and are different than the 60-byte example in IMACICUS (that I want to believe was replaced by the DBCTL/DBCTL and DBCTL/RMIDATA data segment). This note will be revised if the two DBCTLs are not the same. Thanks to Barry Mueller, Tyco Electronics, USA. Thanks to Donald Williams, University of North Carolina, USA.
VMACORAC in TYPEORAC from the old-format Oracle SMF records. Feb 22, 2002 -Oracle8 i Enterprise Edition with OSDI, Release 3 (8.1.7) Mar 1, 2002 for OS/390 has INCOMPATIBLY changed the layout from "MPM" based to "OSDI" based, and it took several iterations to discover their data did not agree with their DSECT: DSECT: DTAI-8,DTAO-8,XCPU-8,RPCS-4,HWST-4,INV-1 but the DATA: DTAI-8,DTAO-8,RPCS-4,XCPU-8,HWST-8,INV-1 showed where the fields really were to get realistic values. The only CPU time measure now is the CPUXMETM, so CPUTM variable (always the total of all CPU times) will only be equal to CPXMETM in the OSDI records; the other CPUxxxx variables are all missing, as are all of the variables that are no longer created in the new OSDI record. And that includes the ORACMSB field added earlier in this change that is not carried forward into the OSDI record. This support also protects the READTIME field from CA-7, which writes a 'EE'x or 'EF'x in the first byte of Read Time to flag jobs, but CA-7 did not provide the exit code for IEFU83 to correct their overwrite. MXG detects and resets to 00, but it turns out that SAS read the EE1B897F time value as a negative, and shifted the READTIME back four days; I've suggested that the SAS SMFSTAMP8 format should not treat the first bit as a sign bit, but instead should have input the field as positive, causing the READTIME to be 462 DAYS into the future, and more likely to be detected as incorrect, so you will notice and then get the fix you need from CA to correct the Oracle SMF. Mar 1: the above change did handle the OSDI format Oracle 8.1.7 records, but there was a missing @; in the MPM-only section of code, so the 8.1.7 MPM format records were not correct; this change inserted the missing @;. Thanks to Sudie Wulfert-Schickedanz, Anheuser-Busch, USA. Thanks to Matt Martin, United States Post Office, USA. Thanks to Leslie Arndt, NITC/USDA, USA Thanks to Yvonne McDonough, NITC/USDA, USA Change 20.006 READDB2 and VMAC102 only recognized DB2 102 subtypes thru EX102316- 314; this changes adds the exits and macros needed to EX102350 recognize those subtypes. However, the actual subtypes READDB2 themselves are not decode; test data is required to write VMAC102 the support code, so only when you enable a new subtype VMXGINIT and send sample data can the subtype be supported. Feb 15, 2002 Thanks to Ford Wong, Workers Compensation Board of Alberta, CANADA. Change 20.005 -Variables STC16SCL, STC17SCL, and STC17MVC were created VMACSTC as stated in MXG Change 19.298, but only in my test lib. Feb 15, 2002 The tested member is now moved to the source library and Feb 27, 2002 those three variables will now be created and kept. -Variables STC11CUB is now FORMATed TIME12.2; it was always the time in seconds and fractions, but now will be printed as a time duration, and documented as a time variable by virtue of being formatted with a TIME format. Thanks to Kis Ranai, Citicorp, USA.
VMACQACS CPU time fields are wrong; documented as in milliseconds, Feb 15, 2002 the data in QAPMJOBM is in microseconds, but QAPMJOBL's same-named variables are still in milliseconds. The two &PIB.8.3 in the INPUT lines for JBCPU and JBTCPU after the INFILE QAPMJOBM statement were changed to &PIB.8.6 and the QAPMJOBM CPU times now match the QAPMJOBL CPU. Thanks to Pat Wingfield, Bank of America, USA. Change 20.003 Change 19.264 described NPM documentation errors for the VMAC28 NRP/NRT/NIT RTYP field in APAR OW53087 which led me to Feb 12, 2002 think there were undocumented data, but IBM has clarified and will revise their APAR text. There is only one value for RTYP in each of those segments: NRPRTYP=2, NRTRTYP=1 and NITRTYP=3, so there is no need to test RTYP value. NRPRTYP was correctly tested in 19.264, but the MXG test for NRTTYPE=2 was removed by this change, once IBM documented what's really there! 25Apr02: Variable NRTDTYPE was removed by this change; it is now a reserved field, but that removal was not noted.
JCLTEST6 because of one error in spelling, but also because some VMACTMV2 MXG support for new products that did not exist before, Feb 12, 2002 now require SAS V8.2 or later: Mar 29, 2002 -Landmark TMVS. MXG support for new release was added to 19.19 on the last day, only QA'd under SAS V8.2, and the unacceptable-to-SAS-V6-nine-byte-character-variable-name of SYSFIL003 (temporary, and not KEPT!) was not detected (until you ran JCLTEST6 under SAS V6!). Deleted one byte.
documentation only; all require SAS V8 for execution: -TYPEWWW WebLog requires SAS V8 because web data is long strings of variable length text that requires V8.2's support for stored character variables length of 32K. By using COMPRESS=YES, you don't waste any DASD, but can have the entire string in one variable. Both LENGTH and $VARYING4096 text caused error messages. -TYPEAIX code requires V8.2 for $VARYING4096 statement. -TYPETMTC code requires V8.2 for $256 length variables, and PDJULI6. informat; that informat was added in the SAS Y2K release 6.09E (TS-470) for the IBM mainframe, and in 6.12 for all other platforms. Thanks to Freddie Arie, TXU, USA. Thanks to Jim Horne, Lowe's Companies, USA. Change 20.001 Never Used. LASTCHANGE: Version 20. =========================member=CHANGE19================================ /* COPYRIGHT (C) 1984-2002 MERRILL CONSULTANTS DALLAS TEXAS USA */
MXG Version 19.11 was dated Feb 4, 2002, thru Change 19.288. MXG Version 19.10 was dated Jan 28, 2002, thru Change 19.282. MXG Version 19.09 was dated Jan 21, 2002, thru Change 19.267. MXG Version 19.08 was dated Dec 20, 2001, thru Change 19.247. MXG Version 19.07 was dated Nov 3, 2001, thru Change 19.218. First MXG Version 19.06 was dated Oct 31, 2001, thru Change 19.214. MXG Version 19.05 was dated Oct 24, 2001, thru Change 19.207. MXG Version 19.04 was dated Oct 5, 2001, thru Change 19.189. First MXG Version 19.04 was dated Oct 1, 2001, thru Change 19.183. MXG Version 19.03 was dated Jul 30, 2001, thru Change 19.151. First MXG Version 19.03 was dated Jul 26, 2001, thru Change 19.148. MXG Version 19.02 was dated Jun 1, 2001, thru Change 19.098. First MXG Version 19.02 was dated May 27, 2001, thru Change 19.097. MXG Version 19.01 was dated Apr 4, 2001, thru Change 19.060. First MXG Version 19.01 was dated Apr 3, 2001, thru Change 19.057. MXG Version 18.18 was dated Feb 12, 2001, thru Change 18.360. MXG Newsletter THIRTY-EIGHT is dated Feb 12, 2001. 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 19.19 is the 2002 Annual Version. II. Incompatibilities and Installation of MXG 19.19. III. Online Documentation of MXG Software. IV. Changes Log ======================================================================= I. MXG Software Version 19.19 dated Feb 14, 2001, is available. Major enhancements added in MXG 19.19: Support CICS/TS 2.2 CICSTRAN (INCOMPATIBLE). Support for TYPE94 APAR OW52989, adds 8-way AX0 controlers. Support for OS/400 Release 5.1.0 Collection Services, in TYPEQACS. New UTILEXCL program for CICS EXCLUDEd fields automatically creates an IMACEXCL member to read your records, without any EDITing, but this major enhancement should be used by ALL sites that read SMF 110 records, even if you do not EXCLUDE fields. UTILEXCL creates an IMACEXCL member with these performance enhancements: - a single INPUT statement (more efficient than conditionals) - eliminates unnecessary arithmetic (avoids missing values) - KEEPs only the variables that exist in your records; all the EXCLUDED fields are dropped, and all of the extra variables that are in the CICSTRAN KEEP= list for new/old versions that do not (yet) exist in your data are also not kept. See text of Change 19.293 and examples in member UTILEXCL. User contributed code to read the output of the unix sar command. ASMVTOC enhanced to select/exclude VOLSER and UCBs above the line.
Datetime values are now automatically converted from GMT fo LOCAL Landmark CICS values are NOT changed, but now could be. See Change 19.288. TIMEBILD/TIMETABL/VMXGTIME supports LOCAL and GMT Time Zone deltas and has identified all MXG datetime variables that contain GMT (few) in the text of Change 19.286. If you have SYSTEMs on different time zones that needs to be shifted to a common zone, of if you have GMT values to change to Local, this massive change will let you do all of the above. And if you do nothing, it does nothing; the VMXGTIME() statements do nothing until TIMEBILD has been invoked for a specific job to change datetimes. UGMTCHEK Utility will check for datetime variables still on GMT
MXG changes LENGTH DEFAULT=4 to =5 on EBCDIC, to =6 on ASCII, to eliminate any truncation of PIB4-input numeric variables, and the stored length of MGBYTES-Format'd PIB4 variables was reduced from 8 to 5/6 to eliminate wasted space. &MXGLEN/&MXGBYLN macro vars can be %LET if you need to restore original defaults; only known exposure is if you use PROC APEND, but did not specify FORCE. No size increase with compress; benchmarks/text in Change 19.272. Initiator Number and Name variables added to PDB.JOBS and TYPE30_1 but missing until you install the IEFU84 SMF Exit Assembly code that moves those fields into type 30 subtype 1. Change 22.136.
Support for IBM AIX Performance Toolbox, PTX V2. You can change the time zone of all SMF datetime variables, by SYSTEM and TimeRange, to put all of your systems on their own time zones (EST/PST/GMT) to the common time zone of the floor of the data center, so you can compare RMF, response, etc., when your SYSTEMS are on different time zones. This is in the VMXGTIME, TIMEBILD, and TIMETABL members. ML-20 ASMTAPES, wrong DDNAME in MXGTMNT SMF if tape on 4-digit. Select step records, then corresponding 14 15 & 64s - see ANAL30. Select SORTs with concat SYSIN, then matching 14 15 - see ANAL16. Support for WebLogs: IIS, WebSphere, CLF, Cookies+. Major enhancements added in MXG 19.08: MXG 19.04-19.07: TYPE73 PCHANBY/PNCHANBY zero, ONLINE wrong. Support for Crypto (for SSL) RMF 70 Subtype 2 APAR OW49808. Support for IBM CICS/TS 2.2 Statistics Record TCBs Support for IDMS Log Statistics Records. Support for Landmark's TMON for TCP/IP v1.1. Support for RSD Folders ASTRE Auditing User SMF record. MXG Software (all versions) supports euro symbol. New HSM variables, start/end timestamps for HSMFSRST events. Sample MQ Series reports were enhanced. Enhanced support for NPM subtypes 18x/19x. ANALDB2R PMACCnn reports caused ERRORS and ABENDS. ASUMUOW Doc updated: which _K macro to use for what data. %GLOBAL macro variables no longer %LET to null value.
were introduced by MXG 19.05 and not completely fixed by MXG 19.06 changes. IBM's unexpected insertion of segments for spare CPUs in type 70 records (APAR OW49536) precipitated Change 19.189 to fix, and that worked fine with 2064 CPUs, but failed with 9672 data. The next fix took care of 9672s, but that fix created too large values for LPnDUR, causing bad percentages, but now only on 2064s. And then a user pointed out that Dedicated CPUs were not quite correctly summed in ASUM70PR logic. Another user had mis-matched values for LPAR busy of the same LPAR from three different systems with MXG 18.18, because he had Dedicated/Wait Complete CPUs, and (after hours of looking at his data, I re-found my) Change 17.203 that created PDB.ASUMCEC to solve the problem with missing values and Dedicated/Wait Complete processors. (That the values were not missing in his 18.18 data was itself an error also now corrected). And Change 19.201 was needed to correct variable SHIFT in ASUM70PR and ASUMCEC.
Support for NTSMF SMS Objects. "Support" for DB2 QLES section added to DB2STATS.
Support Windows 2000, SP2 for Exchange 2000, SQLSERVER, objects. Support for Serena's Ultimizer user SMF record Support for SMF type 82 crypto facility record. New RMFINTRV vars PARTISHN TOTSHARE LPARSHAR CECSER Revised to invoke VMXG70PR to match RMFINTRV interval Major enhancements added in MXG 19.04: Support for z/OS Version 1 Release 2, most new stuff (COMPATIBLE): Existing important SMF and RMF records have been updated, but some new data records, SMF 109, SMF 119 are not yet written. See Change 19.176. (SMF 119 support was added in MXG 19.09). Support for CICS/TS 2.2 Subtype 1 CICSTRAN (COMPATIBLE, unless you have tailored MXG process any optional "user" segments in your SMF 110 Subtype 1 Performance record (how to tell?: if you have any tailored IMACICxx members in your USERID.SOURCLIB). This support does NOT yet support the Subtype 2 Statistics 110. See Change 19.181. Support for IMS 6.1 Fast Path records (INCOMPAT) Support for CISCO Works Blue ISM user SMF record st 01/05/06/66. Support for WAS/390 4.0 EE Websphere SMF 120; won't fail, but this support requires SAS V8.2+ for some character variables to be valid; IBM introduced "Unicode" UCS/DBCS data in SMF 120's. New SPINSORT member to sort SPIN if MXG moves from MVS to ASCII. Documentation of the IHDRxxxx "INFILE" header exits. Support for NTSMF V 2.4.2.11 & Windows 2000 changes. Major enhancements added in MXG 19.03: Support for TPF releases PUT08, PUT10, PUT12 (INCOMPATIBLE). Support for z/VM 3.1 and VM/ESA 2.4 on z900 CPUs. Revisions to ASMIMSL5 (5.1) and ASMIMSL6 (6.1 and 7.1) IMS log. Enhanced ASUMCACH, from 74s: DASD Cache and DASD I/O. New TYPE42XV dataset for XRC Volume segments. Correction for TNG STARTIME, two-digit base-36, etc. Read same MXG dataset from many DDnames/libraries with VGETDDS
PDB.ASUMUOW now contains USERCHAR from CICSTRAN. Support for BMC Mainview Batch Optimizer, BMO SMF. Support for DCOLLECT APAR OW48529, new value. Support for HMF Subtypes 29, 30, and 31. Support for IBM changes to Websphere SMF 120 record. Support for SMF 102 IFCID 096 was corrected. Support for objects NETWORKINTERFACE and PAGINGFILE. ANALUSS example sums CPU time from USS/OMVS task's type 30s. ASMIMSLn deletes IMS 01 records with recovery bit. CICSTRAN STRTTIME/ENDTIME did not include Leap seconds. JCL example to use BatchPipes with SAS - big savings! KEEPALL=YES is now specified in ASUMs to save CPU. SAS V8.2 WARNING: OPTION BLKSIZE(2311) NOT SUPPORTED. Spurious SAS NOTE: "might be uninitialized". TYPE73 records different for SMF73CMG=1 and SMF73CMG=2. Major enhancements added in MXG 19.01: z900 2064s and ICFs without OW48190 have wrong CPU count. - causes CPU busy values to be wrong, too. Change 19.015 DB2ACCT Parallel Transactions are double accounted. - See 19.027. IBM now "rolls up" child records into duplicate. Duplicate observations created in MQMMSGDM dataset. - See Change 19.054. MXG 18.18 error had two outputs. Support for APAR OW46268 TYPE74 USS Kernel in place. Support for APAR OW46622 for Temporal Affinity. Support for CICS TCP/IP EZA01 optional variables. Support for IMS Version 7.1 Log Records - no changes. Support for Omegamon/IMS V500 - no changes. Support for Tandem G06/G07/G08 CPU & DISK records. Support for Landmark's The Monitor for IMS records. Support for TLMS Release 5.5 (COMPATIBLE). Support for CA/TNG new, post-9907 V6, format (INCOMPAT). CICS CPU time captured is now documented in ADOC110. Protection for invalid ALOCTIME (before INITTIME). CHAIN logic in IMF IMS trans corrects negatives. See member NEWSLTRS or the Newsletters frame at www.mxg.com for current MXG Technical Notes that used to be in CHANGES. MXG 19.19 has been tested with SAS V8.2 and SAS V6.09 on OS/390, and with SAS V8.2 on Windows 98 and 2000 and Linux RH 7.2, but should run without error under V8.2 on every possible SAS platform! 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 z/OS 1.1 on 2064s Mar 30, 2001 19.01 z/OS 1.1 with correct MSU Mar 30, 2001 19.02 z/OS 1.2 Oct 31, 2001 19.04 z/OS 1.1,1.2 APARs to 78 Oct 31, 2001 19.05 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 CICS-TS for Z/OS Version 2.2 Oct 31, 2001 19.04 CICSTRAN subtype 1 support only 19.04 CICSTRAN subtype 2 completed 19.05 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 MQ Series 5.2 Dec 16, 2000 18.10 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 NPM 2.6 Nov ??, 2001 19.06 RMDS 2.1, 2.2 Dec 12, 1995 12.12 RMDS 2.3 Jan 31, 2002 19.11 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 Jun 1, 1998 16.08 VM/ESA 2.4 Mar 1, 2001 19.03 z/VM 3.1 Mar 1, 2001 19.03 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 AS400 4.5.0 Jul 27, 2000 18.07 Availability dates for non-IBM products and MXG version required: Yüklə 28,67 Mb. Dostları ilə paylaş:
|