* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
TYPEHSM 17.019 HSM _DIFFHSM macro relocated into VMACHSM. TYPEHSM 17.021 HSM Julian dates printed as 2E6, format now 7. TYPEICE 17.048 Support for IXFP/ICEBERG Subtype 8 and fix for st 6. TYPEICE 17.346 INVALID DATA FOR IOSSTIME, Icebert IXFP subtype 8. TYPEIDAP 17.100 Support for i-data afp-software SMF record. TYPEIISL 17.321 Support for IIS Log.
TYPEIMSA 17.290 More IMS Log revisions correct negative RESPNSTM. TYPEIPAC 17.234 Support for Mobius View Direct 6.1.2 (INFOPAC). TYPEITRF 17.336 Variables IMSVERS,IMSRELEASE,SMBCLASS numeric now. TYPELDMS 17.371 Support for Software Innovation's LDMS product. TYPEMIM 17.152 Support for MIM user record enhanced, new dataset. TYPEMRKV 17.099 Support for Lexmark MarkVision Job Statistics TYPENDM 17.155 Support for Connect Direct R 3.2 'CT' record. TYPENOAM 17.122 Support for STK's NearOAM V2.2 (COMPATIBLE). TYPENSPY 17.154 Zero obs in NSPYTIC3 (again, due to Change 16.147). TYPENSPY 17.367 NETSPY NSPYAPPL dataset had missing response times. TYPENTSM 17.055 Support for NTSMF new Quota Server object. TYPENTSM 17.101 Support NTSMF Version 2.3 (COMPAT), 21 new objects. TYPENTSM 17.165 Protection for Win 2000 Beta 3. IIS, Web changes. TYPENTSM 17.209 Support for Lotus Notes, SMPTDS/SMTPRS objects. TYPENTSM 17.335 Support for Windows 2000 Build 2195 NTSMF data. TYPEORAC 17.308 Support for SQL*NET NIV adds IPADDR/PORTNR to ORACLE. TYPEPMTR 17.297 Support for unix PerfMeter Freeware Monitor records. TYPEQAPM 17.107 Support for OS/400 V4.3.0, no change, is in 16.16. TYPEQAPM 17.235 Support for OS/400 Release 4.4.0 (LRECLs INCOMPAT) TYPERACF 17.305 Support for RACF Unload IRRDBU00 Started Task subtype TYPESARR 17.306 Support for CA View Metrics SARSMFUX SMF record. TYPESARR 17.309 Support for remaining CA-VIEW Metrics validated. TYPESFTA 17.092 Support for SOFTAUDIT 6.1.2 (COMPATIBLE). TYPESFTA 17.123 Support for SoftAudit Version 7.1 (COMPATIBLE). TYPESRMH 17.085 Support for RACAL IT Security's SRM product for HSM. TYPESTC 17.040 STC SILO SMF record sometimes short. TYPESTC 17.195 Support for STK's VTCS 2.2.0 INCOMPATIBLE VSM SMF. TYPESTC 17.230 Variables STC07FPS/TPS now match STK utility report. TYPESTC 17.313 Variables STC11CI/CE/TOL were blank. TYPESYNC 17.145 SYNCSORT variables COREREQ/COREUSED now 8-byte store. TYPESYNC 17.199 Support for 32 (up from 16) sorworks for SYNCSORT. TYPESYNC 17.350 Flags CONTIGn,CACHFWn fixed, DYNALOn,UNOPENn added. TYPETAND 17.037 Support for TANDEM F40, G04 and G05 INCOMPATIBLE. TYPETAND 17.115 TANDEM G05 and later TANDDISK corrected. TYPETCP 17.034 Unexpected TCP/IP command of STOU protected. TYPETCP 17.349 TELNET LOGF Time field is Duration, not datetime! TYPETELE 17.091 Support for TELEVIEW 4.3 (INCOMPATIBLE). TYPETELE 17.246 Support for TeleView 4.3B subtype 3 record. TYPETMDB 17.280 Support for Landmark DB2 Monitor V 3.2 (INCOMPAT). TYPETMNT 17.216 ASMTAPES needed 'ES6' at ASM for Y2K, this protects. TYPETMO2 17.169 Landmark TARSPTM contains sum of all conversations. TYPETMS5 17.021 TMS Julian dates printed as 2E6, format now 7. TYPETMS5 17.151 Undocumented DENX='DE'x TMS records now supported. TYPETMS5 17.352 Year 2000. Variable OUTDATE was still 0cyyddd. TYPETMV2 17.259 Support for TMON/MVS V2 PTF TD01655 (COMPAT). TYPETMV2 17.333 Support for additional Landmark TMVS subtypes. TYPETPF 17.200 Support for IBM's TPF Operating System records. TYPETPX 17.036 TPX Start Up record subtype 1 not properly decoded. TYPETRMS 17.284 Support for TRMS Version 51A08 (COMPATIBLE). TYPEUNIC 17.002 TYPEUNIC support for CA UniCenter is for Open VMS. TYPEZARA 17.344 Year 2000. Support for ZARA Release 1.3 (INCOMPAT). UTANDSTR 17.241 Tandem Utility to read "Unstructured" with new LRECLs UTILBLDP 17.054 Revised and documented utility to modify BUILDPDB. UTILRMFI 17.271 UTILRMFI to show IMACWORK definitions CPU sources. VMAC102 17.253 DB2 trace SQL text variables use &SASCHRLN length. VMAC110 17.220 SMF type 110 subtype 0 JCRLL=0 error. VMAC28 17.018 NPM 2.4, NPMINSES/NPMEVSAL datasets trashed. VMAC80A 17.316 WARNING: BIT MASK TOO LONG corrected. VMACDB2 17.300 Negative QXSELECT because DB2 overflowed counter! VMACIMSA 17.011 MXG ASMIMSLG/L5/L6, STRTTIME is missing due to typo VMACIMSA 17.228 SAP IMS 'AE'x log record was NOT Y2K Ready. VMACTMDB 17.319 Landmark DB2 Version 3.0 INPUT STATEMENT EXCEEDED.
VMXGINIT 17.251 USER= option protected, &SASCHRLN= created VMXGRMFI 17.142 Enhanced RMFINTRV permits over 100 workloads. VMXGRMFI 17.388 Added DROPPGN=,DROPSRV= for easier RMFINTRV tailoring VMXGSUM 17.193 Dashed-variable-list now correctly supported. VMXGSUM 17.255 New stats, INHERIT exploitation under SAS V8. VMXGSUM 17.265 VMXGSUM revisions now implemented in MXG 17.08. VMXGVTOF 17.341 Year 2000. CREATED,EXPIRES,LASTUSE wrong. WEEKBLDT 17.029 Text in col 72 cause unexpected failure. XMXGSUM 17.370 Test version of VMXGSUM using SAS View to save DASD+. YEAR2000 17.363 Year 2000. Julian 0cyyddd values convert to yyyyddd.
ANALRMFR MYTIME parameters for summarization tailoring. All of Feb 6, 2000 the ANALRMFR reports will eventually hav these options.
VMXGCICI DATETIME, which is archaic and STARTIME should be used Feb 6, 2000 in your reports, but now they will still work.
EXINMVCL creates two datasets: EXINMVSR INMVCLNT - Infomover Client Record Subtype 1 IMACINMV INMVSRVR - Infomover Server Record Subtype 2 TYPEINMV These records look much like FTP records, but do not TYPSINMV contain IP addresses, but do have additional statistics. VMACINMV However, the start and end time variables INFSTART/END VMXGINIT are bad, containing INFEND= '38970868'x which should be Feb 6, 2000 close to the record's SMFTIME of '005F7F11'x. Feb 7, 2000 EMC has opened tracking number 2951232 to resolve, but was unaware of the error. Thanks to Charles Piggott, SAS Europe, GERMANY. Thanks to Mr. Ragaglia, ITS - FIAT, ITALY.
ASUMHSM to the VMXGSUM invocation in ASUMHSM, but was overlooked Feb 2, 2000 until now. And work datasets HSMINTVL/HSMSTAT are now deleted at the end of execution of ASMHSM. Thanks to Chris Weston, SAS Institute ITSV, USA.
ANALBATW lines 77, 78, and 170; those characters should each be Jan 31, 2000 an exclamation point, since a pair of exclamation points are used for character string concatenation (instead of long vertical bars, precisely because exclamation points are correctly translated by Rhumba, but long vertical bars are not, and I missed that error when I edited this contribution that had gone thru Rhumba enroute to MXG). Thanks to Raff Rushton, Kaiser Permanente, USA.
ANALRMFR created by ANALRMFR. New REPORT=CACHE argument will Jan 31, 2000 create the report from TYPE74CA Cache DASD records. Thanks to Jiann-Shiun Huang, CIGNA, USA. Change 17.392 MXG 17.01-17.11, on ASCII (PC or Workstations) only. To AUTOEXEC make AUTOEXEC and CONFIGxx members consistent, I added CONFIG OPTIONS S=72 S2=72 into the AUTOEXEC member in MXG 17.01, CONFIGV7 but only today did Chuck discover that those options have CONFIGV8 entirely different meanings to SAS under MVS than under Jan 31, 2000 ASCII! Originally they were needed to prevent SAS from reading source statement columns 73-80, because that's where MVS fixed length files are numbered, and under MVS with fixed length input, options S=72/S2=72 do set the MAXIMUM column to be read. However, under PC/unix, with variable length -SYSIN input, SAS documents that they instead set the MINIMUM column to be read, causing SAS to skip input columns 1-71! When PC SAS read that OPTIONS statement in AUTOEXEC.SAS, it began ignoring columns 1-71 in remaining lines, and never read nor ran the %VMXGINIT statement that followed that OPTIONS statement! Fortunately, those options are now deleted from AUTOEXEC (and for consistency, also from the CONFIGxx members), because MXG Software has been unnumbered since 1992. P.S. I keep several AUTOEXEC.xxx members in the SAS root directory and copy the one I want (kinda like JCL) into the AUTOEXEC.SAS member and then start SAS. However, you can also change the autoexec using c:\sas\sas.exe -config 'c:\mxg\sourclib\config.sas' -autoexec 'c:\mxg\sourclib\autoexec.sas' either in batch execution or in separate shortcuts for your differing file allocations, etc. Making MXG.SOURCLIB VB on MVS reduced it from 150 cyl to 95 cylinders, reduced BUILDPDB EXCPs for compile from 13,326 to 12,886, and CPU time from 45 to 43 sec. It doesn't hardly seem worthwhile! Change 18.147 reinstated S=72,S2=72 in CONFIGV8. 29JUN00. But S=72,S2=72 should NOT be in your AUTOEXEC.SAS file. Thanks to Chuck Hopf, MBNA, USA. Change 17.391 -CICINTRV dataset creation logic was wrong, causing the CICINTRV non-INT event records (REQ/USS/EOD) to be put in the VMXGCICI wrong interval. But IBM caused STARTIME to be wrong in VMXGDUR INT interval records, because DURATM was found wrong: VMXGSUM CICDS Interval records with DURATM=03:00:00 and the Jan 30, 2000 COLLTIME=06:00:00 (so then STARTIME=03:00:00), but CICSSTCK=03:48:00 when this region started. The interval record has SMFSTINO=1, but that interval number is reset at midnight! Since the CICDS record has the dispatcher durations, adding DSGTWT=DSGTDT showed the true duration of this interval was 02:12:00 and the IBM DURATION of 3 hours was wrong! MXG uses COLLTIME to group records. The COLLTIME in the INT records is the end-of-interval value and is the same in all INT records for that interval (e.g. 03:00:00), which VMXGCICI floored correctly to 03:00:00 for summary. However, because the COLLTIME in the EOD, REQ and USS records is a distinct event time (e.g. 03:05:01.99 for a file close), it is not the end of interval, so VMXGCICI incorrectly floored that COLLTIME back to the 03:00:00 end time of the prior interval. This logic error was corrected by adding the INTERVAL value to the COLLTIME for the non-INT records and then flooring that sum back to the end of this interval. This works for timed intervals, but INTERVAL=SHIFT is not supported at this time, as there is no obvious way to determine the end of shift. Call if wanted.
DURATDS from the dispatcher record, if one is found, and the STARTIME will be exact if the COLLTIME is exact and the DURATDS is within 30 seconds of exact. If there were no CICDS records for an interval both the STARTIME and DURATM will be set missing and COLLTIME will be the end of interval. -Variable SMFSTRQT is now kept in PDB.CICINTRV to identify the source (EOD/INT/REQ/USS). -New INTERVAL=EOD option will combine all of the records for a region's execution together and give you total resources for each execution. -New INTERVAL=THREEHR option is an attempt to match IBM's default interval, and works fine as long as all regions create interval records. -But you can still get strange results if you request CICINTRV to be summarized at an INTERVAL that is smaller that your CICS interval, or if a region writes EOD,REQ and USS but doesn't write interval records: a region started at 01:00, wrote three USS CICFCR close records at 05:05:, and then wrote an EOD record at shutdown at 12:00. CICINTRV with hourly default created one obs for the 05:00-06:00 event, with only the FCR counts, and then the EOD record created an overlaping 01:00-12:00 observation with all other measurements. Thanks to Normand Poitras, ISM, CANADA. Change 17.390 The default value for &SASCHRLN was changed back to 100 VMXGINIT from 200 so those SQL text variables under SAS V6 are the Jan 28, 2000 original length and agree with labels. See Change 17.253. Thanks to Jarl L. Bruvoll, VPS, NORWAY. Change 17.389 Support for HP's Measureware V11.0 for HPUX adds several VMACMWUX fields (incompatibly, since they were inserted in the Jan 28, 2000 middle of the records). Thanks to Tony P. Steward, Post Office, ENGLAND. Change 17.388 Additional arguments were added for better tailoring, and VMXGRMFI additional new variables are now kept in both RMFINTRV Jan 27, 2000 and TRNDRMFI datasets. -New OPERANDS: If you specified IMACWORK=NO and USEREPRT=YES, you could not drop unwanted Control Performance Groups or Service Classes; now you have these new operands: DROPPGN= A list of performance groups numbers, which could be either Control or Report Performance groups, that are to be deleted. DROPSRV= A list of service class names, which could be either Service or Reporting Class names, that that are to be deleted. In case you really need to add special logic as each of the individual TYPE7xxx datasets are brought in, these new macro variables permit insertion of any SAS code: INCODE70= INCODE71= INCODE72= INCODE73= INCODE74= INCODE75= INCODE78= -Migration age was not being tracked by RMFINTRV so the MIGAGEMX, MIGAGEMN, and MIGAGEAV variables were added, and if it makes sense to track migration age, it should make sense to also add the HIUIC values. RMFINTRV new variables: HIUICMN HIUICMX MIGAGEMN MIGAGEMX MIGAGEAV IORATE70 TRNDRMFI new variables: HIUICMN HIUICMX MIGAGEMN MIGAGEMX MIGAGEAV IORATE70 PMGIEXAU -Note that the actual values many variables in RMFINTRV & TRNDRMFI datasets that came from TYPE71 with labels that indicate they are average values are actually the maximum value of the average value of each of the individual RMF interval values. These variables are: FIXEDAV CSLPFXAV LPAFXAV LSQAFXAV PRVFXAV SQAFXAV FIXLOAV PCTLSWAP PVTAFCAV CSTORE ESTORE Thanks to Normand Poitras, ISM, CANADA. Thanks to Raymond Schwartz, First Data, USA. Change 17.387 The _STY94 macro contained PROC DELETE instead of invoke VMAC94 of %VMXGDEL(DDDDDD=TY94), so you could not change the PDB Jan 26, 2000 ddname and sort into work. With this correction, the MXG syntax: %INCLUDE SOURCLIB(TYPE94); %LET PTY94=WORK; _STY94;
will sort WORK.TYPE94 into WORK.TYPE94. Note that this syntax is general, and works with all TYPExxxx members. Thanks to Joseph M. Marchesani, Equitable, USA.
VMACNTSM extraneous trash and hex characters that should have been Jan 26, 2000 errored by the SAS compiler, but weren't detected until execution of their data records, causing unrelated error message INVALID HEXADECIMAL CONSTANT STRING CONNXAFA=.... Thanks to Bob Gauthier, Albertsons, Inc, USA Change 17.385 Support for OS/390 Release 2.9. BUIL3005 TYPE30: BUILD005 - New SMF30WMI variable 'Y' identifies jobs executing in EXTY30MR a WLM managed batch initiator. EXTY9207 - New SMF30MSI variable 'Y' if remote system data is EXTY94 incomplete. I don't know what this really means, but FORMATS suspect it means a permanent data loss. IMAC97 - New triplet for the Multisystem Enclave Remote Data, TYPE97 with a separate section for each system on which remote TYPS97 enclaves of this job were executed, contains: VMAC30 RMSU_SEC - CPU SU_SEC OF THIS REMOTE SYSTEM VMAC7072 MRENSYST - SYSTEM ID OF THIS REMOTE SYSTEM VMAC97 CPUMRDTM - CPU TIME FOR DEPENDENT REMOTE ENCLAVES VMXGINIT CPUMRITM - CPU TIME FOR INDEPENDENT REMOTE ENCLAVES. Jan 26, 2000 These variables are output in the new TYPE30MR dataset with an observation for each segment in this job, but the CPUMRDTM and CPUMRITM are summed across all of the remote segments and the sum is kept in TYPE30_V, _4, and TYPE30_5 datasets, as well as being kept in the PDB.STEPS and PDB.JOBS built by BUILDPDB. If your remote systems are of different speeds, you may want to normalize these remote CPU times before they are output; the exit member EXTY30MR allows you to normalize the new CPUMRDTM and CPUMRITM if needed. TYPE72/TYPE72GO - Three new Active durations for enclaves were added: to the TYPE72 and TYPE72GO datasets: TYPE72 TYPE72GO Description SMF72IEA R723CIEA INDEP*ENCLAVES*ORIGINATED*ACTIVETM SMF72XEA R723CXEA EXPORTED*ENCLAVES*TOTAL*ACTIVETM SMF72FEA R723CFEA FOREIGN*ENCLAVES*TOTAL*ACTIVETM TYPE92
TYPE9207 dataset with 33 variables. TYPE97
- New SMF type 97 for FOREIGN ENCLAVE CPU TIME creates dataset TYPE97 with an observation for every system that exported Enclaves to this system containing the Dependent and Independent Enclave CPU time consumed by Foreign Enclaves on this system.
EXTY1083 added GMT interval start/end times, system, sysplex and IMAC108 level to the product section, which are now added to the VMAC108 existing subtype 1 datasets (with a heuristic algorithm VMXGINIT to convert GMT to local until IBM adds the GMT Offset). Jan 26, 2000 The new subtype 3 Monitoring and Tuning data record now creates new dataset TYPE1083 with interval activity and buffer pool statistics. Problems with subtype 3 data: - Five counters in Release 5.02 are accumulated: DOMTDBCI (DBCACHE Initial DB Opens) and DOMTDBCO (DBCACHE OVERCROWDING REJECTIONS) DOMTDBHI (DBCACHE Hits) DOMTDBPR (DATABASE BUFFERPOOL READS) DOMTDBPW (DATABASE BUFFERPOOL WRITES) which was not IBM's intention, and those counters will be fixed in Release 5.03 later this year. The MXG _STY1083 SORT macro deaccumulates those variables only if the record is from Release 5.02, but you will need to add _STY1083 in your EXPDBOUT member if you add SMF 108 record processing to you BUILDPDB. - These MXG subtype 3 variables are set by environmental server variables, rather than being measurements: DOMMXUS /*MAXIMUM*NUMBER*OF USERS*/ DOMTLMCS /*LIMIT FOR*CONCURRENT*TRANSACTIONS*/ DOMTMXCS /*MAXIMUM*CONCURRENT*SESSIONS*/ DOMTTMOT /*DURATION*IN*TIMEOUT*/ DOMTMXCU /*MAXIMUM*CONCURRENT*UPDATE*TASKS*/ DOMTMXRE /*MAXIMUM*CONCURRENT*REPLICATORS*/ DOMTSATH /*SERVER*AVAILABILITY*THRESHOLD*/ If you don't change the corresponding environmental variable at your installation, a default value is put in the SMF record. For the 2nd-4th fields, default values are meaningless: FFFFFFFF FFFF000 F900, (so variables DOMTLMCS, DOMTMXCS and DOMTTMOT are set missing if they contain those values). Thanks to Tom Wieland, Phoenix Home Life, USA. Change 17.383 Member IMACJBCK ("Job Check" exit) is now included in VMAC83 these members that input JOB and READTIME. The IMACJBCK VMAC92 exit lets you select SMF records for specific JOBs. Four VMACHIPR other members, VMACSTC, VMACSUIN, VMACTCP, and VMACWSF Jan 24, 2000 do contain job name, but they do not have the READTIME so without both JOB and READTIME (the "job log"), they are not really written on behalf of a job execution, and so they don't include IMACJBCK. Thanks to Chuck Hopf, MBNA, USA.
VMACDB2 are now added into DB2TCBTM variable in DB2ACCT, as they Jan 24, 2000 are not already captured in DB2TCBTM. Thanks to Brandon Persinger, The Gap, USA. Change 17.381 Revised utility program to print MXG Newsletters from the PRINTNL member NEWSLTRS or CHANGESS, under either MVS or ASCII. Jan 24, 2000 To print Newsletters using MS Word: Open NEWSLTRS.SAS as a new document. Adjust the page setup: Select portrait Set top.bottom margins to .6 inches. EDIT/REPLACE ALL _PAGE_ with a "manual page break", by select "more" on the replace panel then "special" to get to this option. EDIT/SELECT ALL change font to COURIER NEW 9 point PRINT
AAAAAAAA Jan 20, 1999, which was not Y2K Ready. MXG 17.10 dated Jan 24, 2000 Jan 24, 2000 corrected that cosmetic error, since that is only a display string and is not a SAS date value. Thanks to Freddie Arie, Lone Star Gas, USA. Change 17.379 Documentation. All ADOCxxxx members were examined and ADOCall revised to be consistent (i.e., force ZDATE to always be Jan 24, 2000 the last listed variable for each dataset) so that we can programatically compare the variables in member DOCVER with each ADOC and update the ADOC with new or changed variables while still keeping the original ADOC text. Thanks to Freddie Arie, Lone Star Gas, USA.
VMAC74 to "INPUT STATEMENT EXCEEDED" because only 12 of the 18 Jan 24, 2000 structures had complete data in the RMF record. Whenever the total size of the structure Request Data and Cache Data sections is greater than 32760, IBM creates multiple "broken" records from the "large" record, but the 74.4 "broken" records, unlike the 74.1 and 74.2, are invalid.
Request Data sections and the associated 134 Cache Data sections, and then writing a second record with the other 6 structure's Request Data sections and the associated 2 Cache Data sections, RMF wrote a first record containing all 18 structure Request Data sections and the 134 Cache Data sections for structures 1-12, and then RMF wrote a Yüklə 28,67 Mb. Dostları ilə paylaş:
|