* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
Sep 21, 1994 is invoked with zero arguments, and may be fixed in SAS future SAS maintenance (MXG Newsletter 26 said it was fixed in TS410, but it wasn't and may not be fixed in TS420 maintenance), but it is circumvented by changing: SETSSI AF000000 to SETSSI AF010000 For current status, see SAS usage note V6-SYS.SYS-09293. Thanks to Dr. Alexander Raeder, Karstadt AG, GERMANY. Thanks to Harmuth Beckmann, Karstadt AG, GERMANY. Change 12.014 NDM type FP causes INPUT STATEMENT EXCEEDED error. Find VMACNDM INPUT +8 Apr 18, 1994 NDMSCC $CHAR4. /*CMD*COMPLETION*CODE*/ and remove the "+8" from the INPUT line. Thanks to Chuck Hopf, Primerica, USA.
BUIL3001 (see Change 11.351) had two problems: BUIL3518 - If you have added TYPE77 processing to your BUILDPDB, BUIL3606 "ERROR: OPEN OF FILE WORK.TYPE77.DATA FAILED, ANOTHER Apr 18, 1994 COPY OF THE FILE IS OPEN." occurs. You must "unchange" added TYPE77 processing by tailoring your site's PDB. your tailoring in members EXPDBINC,EXPDBVAR,EXPDBCDE and EXPDBOUT, removing the _VAR77, _CDE77, VMAC77, etc. I'm sorry for this aggravation to those of you who had enhanced their PDB, but I had to add TYPE77 to the PDB so that ANALRMFR reports would not fail! - JES3 PDB was not fully tested, and the changes for JES3 were incomplete, causing "DATASET TYPE77 NOT FOUND". In member BUIL3001, add VMAC77 to the INCLUDE list. In members BUIL3518 and BUIL3606, insert _VAR77 after _VAR75, and insert _CDE77 after _CDE75. -Revised Oct 19, 1994: The actual change also relocated the _CDE26J3 invocation in BUILD3606 and BUIL3518 to be after the _CDE30 invocation, so that the length of the ACCOUNTn variables is controlled by IMACACCT, but the text did not indicate this change was also made. Thanks to Jens Schlatter, Independent Consultant, GERMANY. Thanks to Kenneth D. Jones, SHL Systemhouse, CANADA.
ANALSMF and cylinders for CISIZE=26624. Since that is clearly an Apr 15, 1994 irrational size for 3380s, no real harm was done, but the "ELSE IF CISIZE=22528 OR CISIZE=26624 THEN DO;" block was expanded into separate DO groups, one for each CISIZE and TRK3380=CEIL(CINUM/1); is calculated for 26624. Thanks to George Janvrin, ITT Life Insurance Corporation.
VMACCTLD because the semi-colon after the INPUT of JTYPE should Apr 14, 1994 have been an at-sign-semicolon. Thanks to Ms. TAN Siew Peng, United Overseas Bank, SINGAPORE. Change 12.010 Zero or too few observations in dataset NSPYLANS. The EXNSPYLS MXG logic (in the "Exit" member EXNSPYLS) that OUTPUTs Apr 13, 1994 only if there was activity recorded, did not test all of the resource variables, and caused valid observations to be not output. These variables must be added to the list of variables in the SUM() function: OF LLFRABK1-LLFRABK5,OF LLSERAL0-LLSERAL8, OF LLSERRS0-LLSERRS8,LSTSNOFB,LSTSNOFN, LLBYTEIN,LLBYTEOU,LLFRAMIN,LLFRAMOU,LSTFSIFB,LSTFSIFN, LSTFSOFB,LSTFSOFN,LSTMCIFB,LSTMCIFN,LSTMCOFB,LSTMCOFN, LSTOHIFB,LSTOHIFN,LSTOHOFB,LSOTHOFN,LSTSNIFB,LSTSNIFN Yes, it really is worth taking the sum of all of those variables and only outputting when something is non-zero; you will waste lots of DASD space if you output every segment in every record, but you can see for yourself by removing the IF SUM(...) test completely and comparing with the above enhanced test criteria. Note that other LANSPY datasets are also controlled in their Exit members; see Change 9.165 in CHANGESS. Thanks to Alan Wick, Chevron, USA. Change 12.009 IMS Log processing is incorrect. For multiple trans per TYPEIMSA program schedule, the one occurrence of NSMGPROC should Apr 13, 1994 have been spelled NMSGPROC. The earlier text of this change is revised; there are no outstanding problems with IMS Log processing except for the spelling error. See the IMS Technical Notes, above (or in Newsletter 26). Thanks to Cary Jones, Phillip Morris, USA.
VMACTPX TPX records; that version number was not expected. Insert Apr 13, 1994 ELSE IF TPXVER='202 ' THEN TPXVER=' 2.0'; after the line ELSE IF TPXVER='200 ' THEN TPXVER=' 2.0'; Variable TPXSNAME (Session Name) was also added to the TPXAPLON dataset, and processing the 08 record no longer tests for TPXVER but instead uses length of segment to determine what data is present in each segment. Thanks to Rod Fernandes, Albert Heijn B.V., HOLLAND.
VMACLMS in error, causing true LMS records to be flagged and then Apr 13, 1994 deleted. The test IF ITISLMS NE 'LMS ' THEN DO; must be changed to IF ITISLMS NE: 'LMS' THEN DO; because LMS2 is now stored instead of LMS in that 4-byte field. (This was reported earlier and should have been fixed in MXG 11.11, but I failed to make the change!). Thanks to Doug Mayward, Walsh America, USA. Thanks to Rod Fernandes, Albert Heijn B.V., HOLLAND.
VMAC71 and 79 datasets (but was correct in type 70 and 72). The VMAC73 correct equation for the GMT offset must be: VMAC74 GMTOFFxx=100*FLOOR((STARTIME+DURATM-SYNCTIME+10)/100); VMAC75 (the +10 was missing). VMAC76
VMAC77 VMAC78
VMAC79 Apr 12, 1994 Thanks to Mike Skopec, Platinum Technology, USA.
ANALCISH report transactions column restarts, and report programs Apr 9, 1994 column newcopy were wrong. Change all three occurrences of T4=T5+... to T4=T4+.... ANALCISH can also fail with syntax errors, if there are too many observations for the LSRPOOL SUMMARY, FILES, or LSRPOOL FILE reports. Those reports will be redesigned in a future change; you can circumvent the error by commenting out the %CICSTAT2 invocation for those three reports:
%CICSTAT2(CICLSRR,LSR,LSR); %CICSTAT2(CICFCR,FCR,FCR); %CICSTAT2(CICLSRFR,LSF,LSF); Thanks to John Vasilakos, New York Life Insurance, USA. Thanks to Kusol Voratanitkitkul, Blue Cross Blue Shield Ill, USA
DAILYDSN migrated datasets are incorrectly reported as level 2 if Apr 5, 1994 this error is not corrected. Thanks to Steve Talley, U.S. Army Personnel Info Sys Command, USA. Change 12.003 ASTEX can create three SMF records; the comments now show IMACDMON how to define _DMONID if you create three different IDs: Mar 29, 1994 MACRO _DMONID 231 OR ID=232 OR ID=233 % Thanks to Dr. Alexander Raeder, Karstadt AG, GERMANY. Thanks to Harmuth Beckmann, Karstadt AG, GERMANY.
JCLTEST6 required by this INCOMPATIBLE CHANGE. See the complete VMACOPC documentation and JCL example in member VMACOPC. The text Mar 29, 1994 of this change was rewritten May 17, 1994 Apr 9, 1994 -Type 24 physically split records are now supported, but May 17, 1994 two new DDNAMEs are required in your JCL, and DSN=OPCTEMP must have been previously allocated and cataloged: //OPCTEMPW DD DSN=OPCTEMP,DISP=SHR //OPCTEMPR DD DSN=OPCTEMP,DISP=SHR I reconstruct those split records by writing them to the OPCTEMPW DDNAME and then read the reconstructed records from the OPCTEMPR DDNAME after the OPCLOG has been read. New MT0 record type "G" caused INVALID MT0 RECORD error. -Record type used to be an EBCDIC number, but now can be a character value; MXG's 11.11 fix to support the new type "G" was incomplete: after the @; after the INPUT of MT0TYPE, insert line IF MT0TYPE=. THEN INPUT @47+OFFSMF MT0TYPE &PIB.1. @; -Dataset OPC29 did not have all its observations: the semi-colon ";" that is after the INPUT of EXRSTPNR must be changed to an at-sign-semi-colon "@;". Thanks to Randy Shumate, Mead Data Central, USA. Thanks to Waldemar Schneider, SAS Europe, GERMANY.
ANALBLSR OR OPEN='OUTPUT' should read OR OPEN='OUTPUT' THEN ANALDSET LSRSTAT='N'; LSRSTAT='N'; Mar 29, 1994 for ANALDSET to execute without error. However, if you Apr 8, 1994 use ANALBLSR, it will fail because all of the variables that are required by ANALBLSR were not kept in ANALDSET. (The wrong ANALDSET member was moved after testing!). To run ANALBLSR, you must first make these changes to ANALDSET (you can also request a replacement ANALDSET on a 3-1/2 "stiffie" PC diskette): - add COMPONT to KEEP= for TYPE64.TYPE64 - add EXCPDASD EXCPTAPE IOTMDASD IOTMTAPE to KEEP= for TYPE30.TYPE30_4 - insert these lines after BUFNO=BUFDRNO; IF COMPONT=:'INDEX' AND BUFDRNO=0 AND ACBBUFNI GT 0 THEN BUFNO=ACBBUFNI; ELSE IF COMPONT=:'DATA' AND BUFDRNO=0 AND ACBBUFND GT 0 THEN BUFNO=ACBBUFND; - add (IN=INTYP64) after SORT64.TYPE64 in the SET statement following DATA ADDPROG.ADDPROG; - add EXCPDASZ EXCPTAPZ IOTMDASZ IOTMTAPZ to the RETAIN list following IF INSTP THEN DO; - insert these four lines after TYPETASZ=TYPETASK; EXCPDASZ=EXCPDASD; EXCPTAPZ=EXCPTAPE; IOTMDASZ=IOTMDASD; IOTMTAPZ=IOTMTAPE; - insert these four lines after TYPETASK=TYPETASZ; EXCPDASD=EXCPDASZ; EXCPTAPE=EXCPTAPZ; IOTMDASD=IOTMDASZ; IOTMTAPE=IOTMTAPZ; - add EXCPDASZ EXCPTAPZ IOTMDASZ IOTMTAPZ to the DROP statement before PROC SORT DATA=DSETOPEN.DSETOPEN.... Thanks to Freddie Arie, Lone Star Gas, TEXAS. Thanks to Neil Ervin, Huntington Service Company, USA. LASTCHANGE: Version 12 =========================member=CHANGE11================================ /* COPYRIGHT (C) 1984-1994 MERRILL CONSULTANTS DALLAS TEXAS USA */ This is Production MXG Version 11.11, dated Mar 26, 1994. MXG Production 11.11 was dated Mar 26, 1994, thru Change 11.361 MXG Newsletter TWENTY-FIVE, Mar 26, 1994, thru Change 11.347 Early PreRelease 11.11 was dated Mar 9, 1994, thru Change 11.338 MXG PreRelease 11.10 was dated Feb 14, 1994, thru Change 11.316 MXG PreRelease 11.09A was dated Jan 10, 1994, thru Change 11.290 MXG PreRelease 11.09 was dated Dec 17, 1993, thru Change 11.266 Early PreRelease 11.08 was dated Nov 1, 1993, thru Change 11.238 MXG PreRelease 11.07 was dated Oct 4, 1993, thru Change 11.203 Early PreRelease 11.07 was dated Oct 1, 1993, thru Change 11.192 MXG PreRelease 11.06 was dated Sep 1, 1993, thru Change 11.164. MXG PreRelease 11.05 was dated Aug 10, 1993, thru Change 11.150. MXG PreRelease 11.04 was dated Aug 10, 1993, thru Change 11.149. MXG Newsletter TWENTY-FOUR, Aug 2, 1993, thru Change 11.140. MXG PreRelease 11.03 was dated Jul 26, 1993, thru Change 11.140. MXG PreRelease 11.02 was dated Jul 6, 1993, thru Change 11.126. MXG PreRelease 11.01 was dated May 20, 1993, thru Change 11.084. Early PreRelease 11.01 was dated May 15, 1993, thru Change 11.068. Prior Production 10.10 was dated Mar 15, 1993. Member CHANGES repeats sections I, VIII, and IX of MXG Newsletter 25, but you MUST also read MXG Newsletter 25 in member NEWSLTRS for major technical discussions that are not repeated herein.
I. MXG Software Production Version 11.11, dated March 26, 1994 VIII. Incompatibilities and Installation of MXG 11.11. IX. Documentation of MXG Software. X. Changes Log
is now supported, and still exposure. See Change 11.356. MXG Tape Mount and Allocation Monitor now works at 2 out of 3 sites. See Change 11.358. Problem with zeroes in Cache RMF Reporter Records (Newsletter 25 MVS Techical Note) is a fixed problem, but maybe not just due to RMF. I missed phone call with all the details! Fax if you need update. I. MXG Software Production Version 11.11, dated March 26, 1994, was shipped with MXG Newsletter TWENTY-FIVE.
Landmark's CICS/ESA Version 1.1. LEGENT's TPX Release 3.5. Software AG's COM-PLETE Release 4.5 Sterling's NDM, now Connect Direct 1.7.01.
many strange errors! (If you are still stuck at SAS 6.06, see Change 11.187 and use CONFIG06). Member CONFIG executes %VMXGINIT with INITSTMT='%INCLUDE SOURCLIB(VMXGINIT); %VMXGINIT;' to initialize the internal macro variables introduced in Change 11.150.
ASUMDBDS ASUMDB2A ASUMDOS ASUMHPCS ASUM70PR DAILYDSN GRAFDB2 GRAFLPAR TRNDDB2A or if you use %VMXGSUM in your own report/summarization programs, then you MUST read the incompatibility details in Section VIII and in Change 11.309 and you will need to re-tailor your changes. - MXG 11.11 requires SAS 6.08 at maintenance TS407 plus Zap Z6088203 Previously, I also said Z6086442 was required, but SAS Technical Support corrected me; Z6086442 is already included in TS407.
should be installed immediately as it provides these major enhancements: These major enhancements were added in MXG 11.11 dated Mar 26, 1994 Support for STK's ICEBERG device user SMF record. Support for Boole & Babbage CICS/Manager Type 110 Statistics records. Support for Candle's Omegamon II for SMS user SMF record Support for ISOGON's SoftAudit product's externalized files. CICS/ESA Shutdown Statistics Report (DFHSTUP) now produced by MXG. Sterling's NDM, now Connect Direct 1.7.01 incompatible changes. Partial support for LEGENT's MIM Release 4.0. Enhancements and corrections to ANALDB2R DB2PM-like reports. Enhancements to VMXGSUM summarization routine. Feedback that ASMIMSLG does not fail with IMS 4.1 log records. These major enhancements were added in MXG 11.10 dated Feb 14, 1994 Support for IBM's OPC/ESA Release 2.1. Support for LEGENT's NETSPY Release 4.4. Support for CA's ACF2 Releases 6.0 and 6.1. Support for Candle's Deltamon SMF record. Performance improvements for VMXGSUM (used in most ANALxxxx members). The ANALSMF "Simulator" analyzes SMF VSAM CI Size impact on your site. These major enhancements were added in MXG 11.09A dated Jan 10, 1994 Support for Landmark CICS/ESA Version 1.1 (incompatible) records. Summarization of Amdahl's APAF in ASUMAPAF. Support for ZARA Release 1.1. Corrections to ANALDB2R reports. Performance enhancements in VMXGSUM execution.
Support for NPM Version 2.1.0. Support for AS/400 Version 2.3 Performance Data. Support for Memorex Telex LMS Version 2.17 Support for BatchPipes/MVS type 91 SMF record. Support for Mobius' INFOPAC-RDS user SMF record. Support for Integris UniKix records (both ASCII and Binary format). Support for Novell Network Navigator User SMF record. Support for Softwork's Performance Solution I/O Plus & Hiperload SMF. Support for NETWISE RPC EXEC type 33 SMF record. Performance enhancement of VMXGSUM algorithm Utility to count type 110 records by application. These major enhancements were added in MXG 11.08 dated Nov 1, 1993 Support for Amdahl APAF Version 2.1 Support for FOCUS MSO Release 6.8. Support for IBM's ADSM subtype 14 type 42 SMF record. CICS "Requested Reset Statistics" now processed into PDB.CICRRTRV. These major enhancements were added in MXG 11.07 dated Oct 4, 1993 Support for DFSMSrmm (Removable Media Manager) two SMF records. Support for DFSMSrmm Extract Files created by IBMs EDGHSKP utility. Support for AS/400 Release 2.2, all records, labels, formats, etc. Support for SAP's IMS log record type 'AE' for SAP IMS Accounting. Support for AICorp Central Server SMF record. Support for Type 42 Subtype 4 Concurrent Copy & Extended Sequential. Support for Sterling's NDM, Network Data Mover SMF record. Support for 4th Dimension's CONTROL-D Release 3.0.0 SMF record. Support for NETVIEW APAR OY66237 change to TYPE37 SMF record. Graphics enhancements for consistency, better pictures, in GRAFxxxx. These major enhancements were added in MXG 11.06 dated Sep 1, 1993 Support for TCP/IP 2.2.1 APAR PN40511 (API Calls, FTP/TELNET Client) Support for ASTEX Release 1.7 SMF record Support for Software AG's COM-PLETE Release 4.54 SMF record Support for Laser Access Corp's Optical Disk System's 3 SMF records Support for LEGENT's SAR product User SMF record.
MXG 11.04 was a checkpoint version before Change 11.150. These major enhancements were added in MXG 11.04 dated Aug 20, 1993 Support for LEGENT's SAR product's User SMF record. Support for Laser Access's Optical Disk System User SMF records. Final (?) correction to ASUM70PR.
OMEGAMON/CICS VSAM,DLI,IDMS,ADABAS,SUPRA,DATACOM SPE QOC0553 These major enhancements were added in MXG 11.02 dated Jul 6, 1993 Support for VM/ESA Release 2.1. Support for Top Secret Release 4.3. Support for NPM APAR OY54370. Support for RMF APAR OY64585. Support for SAP Releases 4.3.J and 5.0. Support for DOS/VSE POWER 5.1. Support for OMEGAMON 2.60 Audit Record changes. Support for APPC Deaccumulation APAR OY63634. These major enhancements were added in MXG 11.01 dated May 20, 1993 Support for ZARA, The Tape Media Manager from Altai. Support for SYNCSORT Release 3.5 SMF record. Support for HMF, Host Monitoring Facility user SMF record. Support for Corporate TIE user SMF record. Support for STOPX37 Release 3.5 mis-documentation. Enhanced ANALRMFR for RMF look-a-like reports from MXG. Validation of Candle's ITRF (Omegamon/IMS Version 110). Validation and correction of SMSDATA operand of DCOLLECT Each of those enhancements are described in the Change Log, below. Table of availability dates for the IBM products and MXG version: Availability MXG Version Product Name Date Required RMF 4.1.2 (for MVS/ESA 3.1.3) Sep 7, 1990. 8.8 RMF 4.2 (for MVS/ESA 4.1) Oct 26, 1990. 8.8 MVS/ESA 4.1 Oct 26, 1990. 8.8 MVS/ESA 4.2 Mar 29, 1991. 9.9 RMF 4.2.1 (for MVS/ESA 4.2) Mar 29, 1991. 9.9 MVS/ESA 4.2.2 Aug 1991. 9.9 RMF 4.2.2 (for MVS/ESA 4.2.2 Aug 1991. 9.9 MVS/ESA 4.3 Mar 23 1993. 10.10 RMF 4.3.0 (for MVS/ESA 4.3) Mar 23 1993. 10.10 MVS/ESA 5.1.0 ??Summer 1994?? 12.?? CICS/ESA 3.2 Jun 28, 1991. 9.9 CICS/ESA 3.3 Mar 28, 1992. 10.01 DB2 2.2.0 1990 8.8 DB2 2.3.0 Oct 28, 1991. 10.01 DB2 3.1.0 Dec 17, 1993. 11.09 VM/ESA 1.1.1 Dec 27, 1991. 10.1 VM/ESA 2.0 Dec 23, 1992. 10.4 VM/ESA 2.1 Jun 27, 1993. 11.02 These products still had open problems or were potentially incorrect when MXG 11.11 was built. Contact Merrill for current status. TYPEZRB - RMF III VSAM file for MVS/ESA 4.2 and 4.3 is not correct. Huron - Huron SMF record is not supported yet; no sample data SMF data was provided, and the printed DSECTs were massive and needed in machine readable form. Planned for 2nd quarter.
instead, they want you to use the output of their extract program, which means double processing and kludgy coding. Nothing planned until LEGENT supplies needed formats. NDM - Connect/Direct has only been validated for some records. See Change 11.326. VIII. Incompatibilities and Installation of MXG 11.11. 1. Incompatibilities a. MXG's summarization member, %VMXGSUM was changed incompatibly, but it should affect only the very small number of (sophisticated) users who have tailored MXG summarization/trending members:
ASUMDBDS ASUMDB2A ASUMDOS ASUMHPCS ASUM70PR DAILYDSN GRAFDB2 GRAFLPAR TRNDDB2A or if you use %VMXGSUM in your own report/summarization programs, then you MUST read the details in Change 11.309 and you will need to re-tailor your changes. The incompatibility is somewhat obscure; to reduce CPU time and to minimize temporary DASD space used during summarization, %VMXGSUM now determines which variables are needed, and keeps only the needed variables from the input data set. The problem arises only if you use the INCODE= parameter (it lets you insert SAS code into the summarization logic, and is used in those nine members), and even then, only if you reference variables in your INCODE= logic that are not going to be kept in the output summarized dataset. In that rare case, you must list those un-kept variables in the new KEEPIN= parm. The above members in MXG 11.11 contain the needed KEEPIN= statement. (If you overlook this note, you still should detect the problem in your testing, because you will normally see UNINITIALIZED VARIABLE messages on the SAS log to alert you to your error!)
in your JCL, either with the MXGSAS JCL Procedure, or on your EXEC: // EXEC SAS,CONFIG='MXG.V1111.SOURCLIB(CONFIG)' You will get many, strange syntax errors (ERROR 180 or 200) if you do not use the MXG 11.11 CONFIG member.
earlier, AND you have tailored your MXG installation (with EX... or IMAC.... members), you must read the MXG 10.10 compatibility section in member CHANGESS; find the text "member=CHANGE10" and read on! c. MXG Version 11.11 requires SAS Version 6.08 at maintenance TS407, plus SAS Zaps Z6088203 and Z6086442 for MVS and CMS. For WINDOWS, Yüklə 28,67 Mb. Dostları ilə paylaş:
|