* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
END;
ELSE IF MAXFREEB GT 0 THEN DO; FBQ_PCT =100*FREEBUFQ/MAXFREEB; FBH_PCT =100*FREEBUFH/MAXFREEB; FBL_PCT =100*FREEBUFL/MAXFREEB; END; BUF_UTIL=100 - FBL_PCT; See further corrections in Change 13.021. Thanks to Roger Zimmerman, Kemper Service Company, USA. Thanks to Mr. Dechamps, R & V Versicherung, GERMANY.
ANALTALO of SYSTEM should be removed from ANALTALO - the analysis Mar 24, 1995 of tape allocation is across all systems, and variable SYSTEM is not kept in either ASUMTALO or TRNDTALO. This error was only in the MXG 12.12A revision. Thanks to Freddie Arie, Lone Star Gas, TEXAS. Change 13.005 For 3990-6 in Basic Mode, variables CSCONF,CSAVAIL, VMACACHE CSPINNED,CSOFFL,CNCONF,and CNPINNED were 1024 times too Mar 23, 1995 large; MXG converted K-bytes to bytes, but the conversion only applies of the controller is in Enhanced Mode. Put a DO group around the six lines containing "1024*": IF CSSTAT='....1111'B THEN DO; .... END; to convert only for Enhanced Mode. Thanks to Jim Ritter, Blue Cross and Blue Shield of Oregon, USA. Change 13.004 MVS/ESA 5.1 TYPE74ST Structures dataset "INVALID DATA FOR VMAC74 R744SATM ..." error message, plus missing observations. Mar 23, 1995 -The first structure was reread each time, and the 2nd-nth text revised structures were not output, because the second occurrence May 3, 1995 of "INPUT @SMF744SO " should have been just "INPUT " (note, this is the INPUT statement just after the DO _I_=1 TO SMF744SN; statement). Note that this change will increase the count of obs that are created in dataset TYPE74ST. -Variables R744SATM,R744SASQ,R744SSTM,R744SSSQ,R744SQTM, R744SQSQ,R744SDTM, and R744SDSQ were documented by IBM as floating point, but they are actually binary numbers; the eight INPUT statements for these variables with &RB.8.6 must be changed to &PIB.8.6 Thanks to Scott Coryell, FBS Business Technology Center, USA. Thanks to Steve Smith, BGS Systems, USA. Thanks to Dr. Alexander Raeder, Karstadt AG, GERMANY. Thanks to Harmuth Beckmann, Karstadt, AG, Germany Change 13.003 If you changed the duration of RMFINTRV (by tailoring the ANALPGNS _DURSET macro defined in member IMACRMFI) this report did Mar 23, 1995 not work, because it merges TYPE72 and RMFINTRV. Now, ANALPGNS uses _DURSET to force the STARTIME of the TYPE72 data to match the STARTIME of RMFINTRV before the merge. To make the correction, replace the line reading: PROC MEANS NOPRINT DATA=PDB.TYPE72; with these six lines: %INCLUDE SOURCLIB(IMACRMFI); DATA TYPE72; SET PDB.TYPE72; _DURSET
DROP DATE HOUR MINUTE; PROC SORT DATA=TYPE72 %VMXGFOR ; BY SYSTEM STARTIME PERFGRP; PROC MEANS NOPRINT DATA=TYPE72; Thanks to Carol King-Baer, Vanderbuilt University Medical Ctr, USA.
VMAC1415 all striped, multi-volume, and IAM datasets, when it was Mar 23, 1995 supposed to be set only for PDS datasets. The correction is to change the ELSE DO; immediately preceding the DSNAME='UNKNOWN...' statement to read: ELSE IF DSORG='PO' THEN DO; Thanks to Jim Zwier, Smith Barney, USA.
ANALINIT REPORT2. In UCICSCNT, variable BYTES is now formatted UCICSCNT with MGBYTES (so 2.793E8 prints ast "266MB"). Mar 19, 1995 Thanks to Norbert Korsche, OMV, AUSTRIA.
(but were not printed in MXG Newsletter TWENTY-SEVEN) LASTCHANGE: Version 13 =========================member=CHANGE12================================ /* COPYRIGHT (C) 1984-1995 MERRILL CONSULTANTS DALLAS TEXAS USA */ This is MXG Version 12.12A, dated Mar 20, 1995, thru 12.328. MXG Version 12.12A is dated Mar 20, 1995, thru Change 12.328 MXG Version 12.12 was dated Mar 1, 1995, thru Change 12.314 MXG Newsletter TWENTY-SEVEN, Mar 1, 1995, thru Change 12.306 MXG Version 12.07 was dated Feb 6, 1995, thru Change 12.290 MXG Version 12.06 was dated Jan 9, 1995, thru Change 12.240 MXG Version 12.05 was dated Nov 20, 1994, thru Change 12.218 MXG Version 12.04A was dated Oct 23, 1994, thru Change 12.192 MXG Version 12.04 was dated Sep 30, 1994, thru Change 12.169 MXG Version 12.03A was dated Aug 17, 1994, thru Change 12.140 MXG Newsletter TWENTY-SIX, Aug 4, 1994, thru Change 12.128 MXG Version 12.03 was dated Aug 4, 1994, thru Change 12.128 MXG Version 12.02 was dated Jul 4, 1994, thru Change 12.084 MXG Version 12.01A was dated Jun 15, 1994, thru Change 12.056 MXG Version 12.01 was dated Jun 1, 1994, thru Change 12.047 MXG Version 11.11 was dated Mar 26, 1994, thru Change 11.361 MXG Newsletter TWENTY-FIVE, Mar 26, 1994, thru Change 11.347 See member NEWSLTRS for text of Newsletter TWENTY-SEVEN of 1Mar95. Contents: I. MXG Software Version 12.12A, dated Mar 20, 1995. III. MVS Technical Notes not printed in Newsletter TWENTY-SEVEN. VIII. Incompatibilities and Installation of MXG 12.12A. 1. Members IMAC7072 IMAC74 IMACDB2 IMACPDB IMACWORK IMACTMNT MONTHBLD WEEKBLD IMACCICS TYPEQAPM changed. 2. Installation instructions. IX. Online Documentation of MXG Software. X. Changes Log I. MXG Software Version 12.12A, dated Mar 20, 1995, contains these major enhancements: Major enhancements added in MXG 12.12A dated Mar 20, 1995: Twelve MXG 12.12 members had errors that are now fixed: ANALCNCR ANALDB2C ANALDB2R ANALPATH ANALTALO IMACICSA TRNDTALO VMAC80A VMAC110 VMACILKA TYPEMON8 TYPETMON Support for Memorex/Telex LMS Version 3.1 (INCOMPATIBLE). Major enhancements added in MXG 12.12 dated Mar 1, 1995: Support for OS/400 AS/400 Version 3.1.0 INCOMPATIBLE. Support for PR/SM APAR OW078986 adds "MVS Wait" to "LPAR Waits" Support for Type 99 Subtype 1 added. Support for CICSAO availability measurement SMF written by CICSAC. Support for Mitchem's ACC/SRS user SMF record. Support for LEGENT SAR Cross Memory Session Logoff user SMF record. Support for Network Systems DXE channel RDS user SMF. Support for Velocity Software XAMAP Version 2.2. Support for CICSAO user SMF record for CICS availability. Support for Boole & Babbage IMF Version 3.1 (for IMS 5.0). Support for VAX/VMS Accounting and Performance data. Amdahl's MDF now populates TYPE70PR/ASUM70PR with valid CPU time. Candle's ITRF product-error corrections have been validated. RACF TYPE80A enhanced to decode RACF commands of interest. REXX program to convert DB2 GTF records to SMF format for MXG. ANALPGNS reports CPU utilization by Performance Group. ANALDB2R Support for DB2 Version 3.1 DB2PM-like reports. ANALMTP Analysis of Tape Mounts Concurrently Waiting. ANALRMFR enhanced, selection by storage class, device, LCU added. XMXGSUM replacement for VMXGSUM is ready for full use. Major enhancements added in MXG 12.07 dated Feb 6, 1995: Support for TCP/IP Version 3.1 (incompatible). Support for RMDS Version 2.1 (incompatible). Support for TPX 4.0 (compatible with one line edit). Support for RMF Monitor III ("ZRB") for MVS/ESA 4.3 - partial. Support for Xerox Print Service Manager XPSM SMF record. Support for BGS's BEST/1 I/O Monitor SMF record. Support for Boole & Babbage CMF VSAM MRR records. %ANALCNCR algorithm for concurrency analysis (inits, tapes, etc.) Circumvention for CACHE90 zero observations with RAMAC devices. New TYPE72DL dataset for MVS/ESA 5.1 Goal Mode Major enhancements added in MXG 12.06 dated Jan 9, 1995: Support for NETSPY 4.5. Compatible except for LU6.2 NSPYAPPL data. Support for Innovation Processing's IAM user SMF record. VM/ESA 2.2 Scheduler records supported. Invalid DB2 type 101 SMF record workaround (fix is APAR PN63234). Revised ANALPATH reporting for MVS I/O Path analysis. Final (?) enhancements for VMXGSUM parsing of all dataset options. Major enhancements added in MXG 12.05 dated Nov 20, 1994: Support for MQM 1.1.2 Performance Statistics type 115 SMF record. Support for MQM 1.1.2 Accounting type 116 SMF record. Support for Omegamon for CICS V100 and V300 SMF. Support for Landmark Monitor for MVS Release 1.3 enhanced. Support for InfoAccess Release 5.1 user SMF record. Support for HSM APAR OW05988, adds CPU time to FSR! Support for Sterling Software's ASM V3.0.0 type 39 records. Support for CA/SQL user SMF record (same as IDMS records). Support for S/390 Parallel Query Server SPQS SMF 123 started. Correction for NPM 2.2 NPMVSaaa datasets. CICS Utility UTILCICS now identifies type 110s from Omegamon. New dataset PDB.TYPE72SC for Goal Mode Server data. Type 42 technical note, removal of GMT offset calculation.
Correction to MXG 12.04-only errors: Type 28 Input Statement EXCEEDED error message. MXG Tape Unload caused return code 4, extra members unloaded. UTILCICS failed with syntax error Correction to SAP Accounting under IMS. Correction to NETSPY Token-Ring TIC-UTIL in NSPYTR - was too large. Correction to TYPE42 STARTIME/ENDTIME - may be on GMT clock. Technical note on Memory measurement in MVS Technical Notes.
Support for CICS/ESA 4.1.0 (compatible) adds important new measures. Support for NPM 2.2 (compatible, but new subtypes). Support for LEGENT's TSO/MON 6.1 (compatible). Support for Landmark TMON Monitor for CICS/ESA 1.3 (incompatible). Support for Landmark TMON Monitor for DB2. Support for STK ICEBERG SMF record subtype 5. Support for CA's TELEVIEW user SMF record. Support for APARs OW00484/UW06888/others corrupt TYPE1415 variables. DB2STATS variables QB3Taaaa/QB4Taaaa corrected. TYPE37 Short LAND segment INPUT STATEMENT EXCEEDED corrected.
Support for TLMS Release 5.4 (incompatible). Support for BETA93 1.6.1 validated (it was incomplete in MXG 12.03). Further DB2 3.1 corrections in TYPEDB2 and TYPE102 support. Major enhancements added in MXG 12.03 dated Aug 4, 1994: Support for MVS/ESA 5.1 Type 99 Subtype 2 record. Support for LEGENT's ASTEX Release 2.0. Support for UniKix Release 4.1 Binary File Support for EMPACT's HIPER-CACHE Version 1.1.1. Support for SMF Type 50 VTAM Tuning APAR OW04453. Support for RSD's WSF Release 3.5.1. Support for Omegamon II for SMS V100/V110. Support for BETA93 user SMF record. MXG Tape Mount and Tape Allocation Monitor errors now works! Correction for NPM Release 2.0 subtypes 214 thru 219. Additional DB2 3.1 Trace IFCIDs supported. Analysis ANALDB2C matches CICSTRAN observations with DB2ACCT. Major enhancements added in MXG 12.02 dated Jul 4, 1994: MXG Tape Mount and Allocation Monitor was revised, new reports. Support for IBM's CRR 1.6 (3990-3 and 3990-6) (incompatible). Support for DFSMS 1.2 changes to DCOLLECT (compatible). Support for MEMO subtype 6 record. Support for TCP/IP APAR PN34837 new field (compatible). Support for MVS APAR OW00884/UW06821 - (no impact, see MVS Notes). Support for IMS 4.1 Log Records (see IMS Technical Notes)
Support for Measured Usage SMF Record 89 and changes to type 30. DB2 Version 3.1 Buffer Pool statistics were incorrect in MXG 11.11. OPC Version 1.2.0 had INPUT STATEMENT EXCEEDED error with MXG 11.11, but change 12.002 corrects, plus adds support for split records! Problem with Cache RMF Reporter Records discussed in Newsletter 25 are actually fixed by MVS APAR OW01787. ANALDSET/ANALBLSR routines were corrected in Change 12.001. All of these enhancements are described in the Change Log, below.
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 Jun 24 1994 12.02 MVS/ESA 5.2.0 ??? ?? ???? 13.?? 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. 12.04 CICS/ESA ?.? ??? ??, ????. 13.?? CRR 1.6 Jun 24, 1994. 12.02 DB2 2.2.0 1990 8.8 DB2 2.3.0 Oct 28, 1991. 10.01 DB2 3.1.0 Dec 17, 1993. 12.04 DB2 4.1.0 ??? ??, ????. 13.?? DFSMS/MVS 1.1 Mar 13, 1993. 11.11 DFSMS/MVS 1.2 Jun 24, 1994. 12.02 NPM 2.0 Dec 17, 1993. 12.03 NPM 2.2 Aug 29, 1994. 12.05 VM/ESA 1.1.1 Dec 27, 1991. 10.01 VM/ESA 2.0 Dec 23, 1992. 10.04 VM/ESA 2.1 Jun 27, 1993. 12.02 VM/ESA 2.2 ??? ??, 1994. 12.06
Product Name Date Required Landmark The Monitor for CICS/ESA 1.3 12.12 The Monitor for MVS/ESA 1.3 12.05 Candle
OMEGAMON for CICS V300 User SMF Record 12.05 Boole & Babbage IMF 3.1 (for IMS 5.1) 12.12 III. MVS Technical Notes not printed in Newsletter TWENTY-SEVEN. 1. APAR OW06770 and QW09814 (PTFs UW10049 and UW14370) correct type 72 wrong values in MVS/ESA 5.1 fields SMF72ACT SMF72SER SMF72MTS SMF72ITS SMF72CTS SMF72TAT and SMF72STS. Bad values occurred in any interval in which a CICS region was FORCED or a batch job terminated at end of memory. The bad values were all '7FFFFFFF'x, which in MXG (being read as PIB4.) is 2,147,483,647! 2. Boole & Babbage CMF 5.1 creates RMF records with incorrect STARTIME when SYNC is specified, which causes MXG's RMFINTRV dataset to see incorrect uncaptured CPU times. Boole's fix is BPM5061. Another symptom is a difference of 1 second between the STARTIME in the type 70 and the STARTIME in the type 71 records.
must refit your tailoring, starting with the new IMAC member): IMAC7072 IMAC74 IMACDB2 IMACPDB IMACWORK IMACTMNT MONTHBLD WEEKBLD IMACCICS b- The JCL for processing the OPC log requires two new DDNAMES so that the OPC spanned records can be reconstructed and read by MXG. See comments in member VMACOPC. Member JCLTEST6 was changed also.
added. See Change 12.292 d- ASUMTALO was incompatibly changed in MXG 12.12, so early users of the Tape Mount and Allocation Monitor analysis will need to rebuild PDB.ASUMTALO (by %INCLUDE SOURCLIB(ASUMTALO) against each PDB that they want to include), so that TRNDTALO will trend tape allocation. e- These products were incompatibly changed by their vendor, and they require MXG 12.12 (or at least the MXG 12.xx indicated): MVS/ESA 5.1 (Goal Mode) Change 12.034 MXG 12.02 OS/400 Version 3.1.0 Change 12.292 MXG 12.12 TCP/IP Version 3.1 Change 12.257 MXG 12.12 RMDS Version 2.1 Change 12.264 MXG 12.12 Omegamon for VTAM V160 Change 12.186 MXG 12.04A Landmark CICS Version 1.3 Change 12.151 MXG 12.12 Landmark MVS Version 1.3 Change 12.191 MXG 12.05 APAF 2.2 Change 12.138 MXG 12.12 TLMS Release 5.4 Change 12.136 MXG 12.03A Cache RMF Reporter 1.6 Change 12.070 MXG 12.12 2. Installation and re-installation procedures are described in detail; in member INSTALL (which also lists common Error/Warning messages a new user might encounter), and sample JCL is in member JCLINSTL: Summary:
a. Install member MXGSAS as JCL Procedure MXGSAS in your PROCLIB. b. Allocate a 90-cyl PDS: MXG.V1212.MXG.SOURCLIB, and use IEBUPDTE to read the MXG tape to create the 2500+ member Source Library. c. Allocate a 1-cyl PDS: MXG.V1212.USERID.SOURCLIB for your site "Installation Tailoring" Source Library. Installation specific tailoring (like telling MXG your shift hours, which performance groups are TSO, CICS, etc.) is done by copying and modifying MXG source members into V1212.USERID.SOURCLIB. d. Allocate a 1-cyl SAS Data Library: MXG.V1212.MXG.FORMATS and execute SAS to create the library of Formats required by MXG. e. If this is the initial install of MXG, tailor these members into your MXG.V1212.USERID.SOURCLIB tailoring library: IMACACCT (Account Length), IMACSHFT (Shift Definitions), IMACWORK (Performance Group to Workload mapping), and IMACSPIN (for BUILDPDB). Each IMAC member is self-documenting, and IMACAAAA is the index of all of the IMACs. You should at least scan IMACAAAA to see the acronyms MXG uses for the many products MXG supports. e. If re-installing MXG, copy your existing USERID.SOURCLIB library members into the MXG.V1212.USERID.SOURCLIB. Then, compare the members in your USERID.SOURCLIB with the list of members that were incompatibly changed (above, in this section) in this MXG. If any of the incompatibly changed members exist in your dataset MXG.V1212.USERID.SOURCLIB, then you must reinstall your site's tailoring for that IMAC, starting with the IMAC member from the MXG 12.12 Source Library. f. EDIT and submit member JCLTEST6 to verify that your tailoring did not create any errors. g. EDIT and submit JCLPDB6 to create a Daily PDB for testing. Or use the TYPE.... members to process specific data sources, use the ANAL.... members for report examples, the GRAF.... members for SAS/GRAPH reports.
parallel testing is complete and are ready to implement MXG 12.12 in production, rename your three current MXG Production Libraries (MXG.MXG.SOURCLIB, MXG.USERID.SOURCLIB, and MXG.MXG.FORMATS) to (MXG.BACK.MXG.SOURCLIB, MXG.BACK.USERID.SOURCLIB, MXG.BACK.MXG....) and rename the MXG.V1212.x.y libraries to their Production names! Again, detailed installation instructions are in member INSTALL Always read comments in the CHANGES member for compatibility issues, as well as for any last minute changes. Whenever you install changes or test a new version of MXG (or even your own reports), be extra careful to look on the SAS log for any real error conditions. Search for all occurrences of "ERROR:", "ERROR :", " NOT " "UNINITIALIZED", "TRUNCATED", "NEVER BEEN", "NOT FOUND", "CONVERT", "APPARENT", and "NOT CATLGD", as they usually indicate a serious error. A PROC PRINT and a PROC MEANS of each new MXG-built SAS dataset can help you to understand their contents, and should be used to examine any unusually large, negative, or suspicious values. Print all variables in the dataset, and read the variable's descriptions in its ADOC member.
MXG Guide, and the 1987 MXG Supplement) are contained in the MXG Source Library, as are all MXG Technical Newsletters and all MXG Changes, so all MXG documentation is actually online in the software itself; even the Installation Instructions are online, in members INSTALL/JCLINSTL!
to which the text from newsletters and changes has been added. Some of these chapters are still rough; while some of the chapters have actually been completely revised, many of these ACHAPxxx are little more than a concatenation of the two original chapters, often without the figures or tables. The revision is work still in progress! Members ADOCxxxx are what were in Chapter FORTY, and should be the first place you look for information about MXG variables and/or datasets. The ADOCxxxx members alphabetically describe each dataset and all variables that are created by product xxxx, the instructions on how to enable that product, bibliography of the vendor documentation, sample PROC PRINT and PROC MEANS of real data, references to MXG reports that use these data, and the MXG member names that you use to process that product. While this too is work in progress, the most heavily used data sources, especially the common SMF records, have been revised and are up to date.
you know the xxxx suffix for a product, you then know the names of all of the MXG members for that product, because of MXG naming conventions:
that name the dataset(s) created from product xxxx. ADOCxxxx - "Chapter FORTY" style dataset and variable documentation of all datasets created from product xxxx, with sample output. VMACxxxx - The "real" source code member, often extensively commented. TYPExxxx - Standalone member to test or process product xxxx records. ASUMxxxx - Summarization example (only for some products) TRNDxxxx - Trending example (only for some products) ANALxxxx - Reporting/analysis example (only for some products) GRAFxxxx - SAS/GRAPH report example (only for some products) EXyyyzzz - OUTPUT exit for tailoring of each MXG dataset, not used by most MXG sites, but powerful if needed. There can be more than one dataset created from one product. The yyyzzz suffix of the EXyyyzzz member name is the same as the suffix of "_L" and "_K" macros defined in the IMACxxxx for its product. See Using the MXG Exit Facilities in ACHAP33. Member IMACAAAA is an index of all IMACs, and is the best place to begin to find what xxxx suffix Merrill chose for which product! You can often find additional documentation by searching members NEWSLTRS or CHANGESS for the xxxx suffix. Member CHANGES identifies this Version and Release of MXG Software, and describes all changes made in this Release, plus new technical notes. Member CHANGESS contains each of the CHANGES members from each version of MXG, so this member contains ALL changes ever made to MXG Software. Since each MXG change lists the names of the members that were added or altered, names the new product/version supported by a change, or lists Yüklə 28,67 Mb. Dostları ilə paylaş:
|