* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
ANALDB2R 13.079 DB2 Statistics Summary PMSTA01, Audit report fixes. ANALDB2R 13.106 Statistics Report correction, FORMAT NOT FOUND. ANALDB2R 13.118 Final (?) corrections to Statistics and Audit Reports ANALDB2R 13.159 More Statistics Report errors, but at field level. ANALDB2R 13.191 $DB2DBID FORMAT NOT FOUND may still occur in 13.05. ANALDB2R 13.278 Enhancements only! No errors reported! ANALHSM 13.307 Analysis of HSM SMF record HSMFSRST data. ANALPATH 12.325 Cross-System DASD Reports cols ran together. ANALPATH 13.207 INVALID ARGUMENT error in report program. ANALPGNS 13.003 Failed if you changed RMFINTRV duration in IMACRMFI. ANALRMFR 13.134 Data/time selection crossing midnight failed. ANALTALO 12.327 VARIABLE NOT FOUND error. ANALTALO 13.006 Variable SYSTEM NOT FOUND in MXG 12.12A. ANALTAPE 13.037 All-systems report was missing. ANALTAPE 13.286 ERROR:KEYWORD PARAMETER in MXG 13.06-13.07 only. ASMIMSLG 13.265 IMS 5.1 changes, untested. ASMRMFV 13.027 0C4 ABEND if no enqueue table, additional records. ASMTAPES 13.135 MAINTLEV 4 of MXG Tape Mount and Allocation Monitor ASMTAPES 13.163 MAINTLEV 5 of MXG Tape Mount and Allocation Monitor ASMTAPES 13.187 MAINTLEV 6 of MXG Tape Mount and Allocation Monitor ASMTAPES 13.282 MAINTLEV 7 of MXG Tape Mount and Allocation Monitor. ASMVTOC 13.331 Support for 4-digit UCBs. ASMVVDS 13.330 Support for 4-digit UCBs. ASUMCICS 13.268 Default summarization now includes USER. BUILDPDB 13.320 CODEPASS=2 now set only for MVS execution. CICINTRZ 13.281 Replacement for CICINTRV available for testing. DIFFDB2 13.212 Removed DB2STAT2 from DIFFDB2 create of DB2STATS. DIFFDB2 13.269 Variables QBSTHPL/QBSTVPL removed from DIF(). FORMATS 13.061 All MXG formats for hex values use OTHER= syntax. FORMATS 13.127 MXG FORMATS member incompatible with SAS Version 5. FORMATS 13.319 OTHER= syntax now works under MVS or ASCII. GRAFLPAR 13.060 MXG 13.01 only. NAME uninitialized error. IMACFILE 13.109 Select CICS records by APPLID/SUBTYPE example. IMACICSA 12.324 SAP Journal data times formatted correctly. IMACICSA 13.077 CICS SAP variable STCTIMTR may be wrong. IMACICSA 13.199 SAP variable STICODE changed from Numeric to Char. IMACPDB 13.271 SYSNAME and SYSPLEX added to PDB.JOBS/STEPS/PRINT. IMACSPCK 13.241 New BUILDPDB/BUILDPD3 exit for SPIN override. IMACZDAT 13.237 ZDATE creation now localized, for ease in reruns. JCLDAYDS 12.316 DCOLLECT output LRECL=644 instead of LRECL=264. JCLPDB6 13.018 Member ASUMDB2S does not exist error. MONTHBLD 13.015 SORT error building monthly TYPE72, wrong BY list. REXXDB2 13.284 REXX program to convert DB2 GTF records corrected. RMFINTRV 13.213 TSOxxxxx response variables FORMAT now 7.3. SASAFIX1 13.239 S370FRBn informat replacement .DLL for ASCII SAS. TRNDDB2S 13.031 Variables QTPUBD and QTXAIRL incorrect spellings. TRNDTALO 12.327 Syntax error due to missing comma. TYPEACF2 13.112 ACF2 subtype "L" logic (ACF2JR dataset) redesigned. TYPEACHE 13.005 CRR 1.6 with 3990-6 in Basic Move, values wrong. TYPEAUTO 13.091 Support for LEGENT's AUTOMATE SMF record. TYPEAUTO 13.102 Corrections to initial support for AUTOMATE. TYPEAXC 13.149 Support for Kodak AXCIS Optical Disk SMF records. TYPEBETA 13.322 Support for BETA 93 Release 1.06.50 INCOMPATIBLE. TYPECACH 13.103 Support for 4-digit UCB in Cache RMF Reporter data. TYPECACH 13.262 DEVPLX (duplex volume) address wrong, IBM worrying. TYPECOMP 13.222 Support for COM-PLETE Version 4.6 SMF record. TYPECTLG 13.325 Support for MVS Catalog Records exported by IDCAMS. TYPEDB2 13.212 Dataset DB2STAT2 was incomplete. TYPEDB2 13.244 Support for DB2 4.1.0 type 100 and 101 records. TYPEDCOL 13.105 INPUT STATEMENT EXCEEDED with SMS 1.2 DCOLLECT. TYPEDCOL 13.295 Support for DFSMS/MVS 1.3 DCOLLECT records (COMPAT). TYPEDCOL 13.332 Support for 4-digit UCBs. TYPEDOS 13.328 Support for DOS/VSE POWER 5.2 Accounting Records. TYPEEDGS 13.124 IBM RMM SMF record INVALID DATA FOR MDUCDATE. TYPEEPMV 13.170 Support for OMEGAMON/MVS Version 300 (INCOMPAT). TYPEEPMV 13.201 Support for Omegamon for MVS/ESA V400 adds variables. TYPEEREP 13.164 Support for EREP/SYS1.LOGREC records. TYPEEREP 13.208 EREP gets INVALID DATA FOR DTL, additional support. TYPEEREP 13.270 INPUT STATEMENT EXCEEDED error corrected. TYPEFRYE 13.317 Support for Frye Systems LAN measures for Netware. TYPEHIPR 13.120 Support for Boole & Babbage HiperCache V1.4.3. TYPEHMF 13.038 Support for HMF subtypes 4 and 5. TYPEHMF 13.165 Deaccumulation of HMF records. TYPEHPAI 13.010 Support for HP-PCS data from AI UNIX. TYPEHPSU 13.010 Support for HP-PCS data from SUN UNIX. TYPEHPUX 13.010 Support for HP-PCS data from HPUX UNIX. TYPEHSM 13.131 Corrections to HSM FSR segment in SMF record. TYPEHSM 13.218 Support for HSM ABARS ABACKUP/ARECOVER FSR segment. TYPEHSM 13.259 HSM ABARS record now validated. TYPEHURN 13.085 Support for Antares' HURON ObjectStar SMF record. TYPEHURN 13.243 Zero obs in HURN49 dataset. TYPEICE 13.026 ICEBERG subtype 5 extents and TOIOTIME wrong. TYPEIDMS 13.223 Support for IDMS 12.01 Maint 9506 (INCOMPATIBLE). TYPEIDMS 13.267 Support for IDMS 12.01 INVALID DATA FOR PMHSDATE. TYPEILKA 13.130 Internet addresses were not converted to num-point. TYPEIMSA 13.013 IMS DEDB and MSDB counts from fastpath type 59. TYPELMS 12.326 Support for Memorex/Telex LMS Version 3.1 (INCOMPAT). TYPEMON8 12.315 NO MATCHING DO/SELECT error, 'TD' record support. TYPENAF 13.094 NAFLOGOF dataset variables incorrect. TYPENAF 13.133 Candle's Supersession Release 147 PTF QLV1372 TYPENDM 13.070 Variable NDMDSDSN (Source DSN) added to NDMCT. TYPENDM 13.146 Connect Direct (formerly NDM) minor corrections. TYPENSPY 13.021 NETSPY Type N subtype 06/07 support incorrect. TYPENSPY 13.022 Support for NETSPY Release 4.6 (compatible). TYPENSPY 13.059 INPUT STATEMENT EXCEEDED for NETSPY type X record. TYPENTCP 13.144 Support for NetCompress SMF records. TYPEOMCI 13.173 INPUT STATEMENT EXCEEDED RECORD Subtype 200.4. TYPEOPC 13.092 Support for OPC Release 3.0 (INCOMPATIBLE). TYPEPKMN 13.145 Support for Packet/Main SMF records. TYPEQAPM 13.051 Support for OS/400 Version 3.1.0 wrong in MXG 12.12. TYPEQAPM 13.071 OS/400 Version 3.1, DSARM/DSTYPE reversed. TYPERACF 13.030 Support for IBM's IRRDBU00 RACF Database Unload. TYPERMDS 13.260 INVALID ARGUMENT TO MDY in RMDS 1.4 records. TYPESAMS 13.080 Support for Sterling SAMS Storage Automation SMF. TYPESAVR 13.252 New fields added, ZAP required to populate. TYPESFTA 13.219 Support for ISOGON Soft Audit Version 4.1. TYPESOLV 13.028 Support for Sterling SOLVE NCL CPU-time accounting. TYPETAND 13.221 Support for TANDEM D20 MEASURE CPU, DISK and PROCESS. TYPETAND 13.283 Support for TANDEM D20 D30 and D40 releases. TYPETCP 13.008 Support for TCP/IP APAR PN69321-PN69322. TYPETMDB 13.223 Support for Landmark TMON for DB2 Version 2. TYPETMNT 13.135 PROGRAM=IEFIIC records are again deleted by TYPETMNT. TYPETMON 12.320 Landmark Version 1.3 variables were not INPUT. TYPETMON 13.204 TYPETMON (TMON CICS 1.3) INCOMPATIBLY CHANGED BY MXG. TYPETMS5 13.083 Support for TMS (CA-1) Release 5.1 (compatible). TYPETMS5 13.123 New variables from 5.1 added to final datasets. TYPETMS5 13.308 BUFNO=220 on //TMC DD reduces 15 minute run to 4! TYPETMVS 13.170 Support for new TMON/MVS subtypes. TYPETSOM 13.143 TSO/MON 6.1 only, TRIVTM,NTRIVTM,LONGTM too small. TYPETUX 13.288 Support for Landmark TMON for UNIX. TYPETUX 13.302 Corrections and Enhancements for Landmark TMON/UNIX. TYPEVM 13.287 Support for VM/ESA SQL/DS Remote User Account Record. TYPEVMXA 13.126 Sterling's VM/Monitor MONWRITE records cause error. TYPEVMXA 13.137 Support for MICS VM Data Transmission Program output. TYPEVMXA 13.168 Correction to Change 13.126, applies to IBM too. TYPEVMXA 13.318 Alternative VXBYUSER using VXUSELOF vice VXUSEINT. TYPEWYLA 13.075 Support for ACS Wylbur Accounting SMF record. TYPE102 13.009 T102S145 QWn145OB values wrong. TYPE102 13.192 IFCID 21 or 44 INVALID SECOND ARGUMENT error message. TYPE110 12.321 CICS Statistics CICDS and CICEODRV datasets wrong. TYPE110 13.057 CICSLSRR variables A08BKCTD/A08BKDTD incorrect. TYPE110 13.261 Support for SAP 5.0 INCOMPATIBLE type 110 journal. TYPE110 13.291 CICSTRAN (MXG 13.07-13.08 only) ENDTIME/ELAPSTM bad. TYPE110 13.292 CICS/ESA 3.3 UNEXPECTED STATISTICS with STILEN=0. TYPE110 13.296 CICS/ESA 4.1 TRANTYPE was moved by IBM, now correct. TYPE116 13.049 Zero observations in dataset TYPE116. TYPE1415 13.002 DSNAME='UNKNOWN...' set incorrectly for multi-vol. TYPE1415 13.064 Multi-UCB type 1415 SMS fields wrong. TYPE16 13.093 Support for DFSORT Release 13 (INCOMPATIBLE). TYPE24 13.066 Fields added by MVS/ESA 5.2 TYPE26J2 13.263 JESNR may show only four digits; IBM lied in ESA 5.2 TYPE28 13.072 Support for NPM Version 2.2 APAR OW08641. TYPE30 13.065 Negative value for EXECTM due to IBM leapseconds. TYPE30 13.066 Fields added by MVS/ESA 5.2 TYPE30 13.073 ABEND value may be wrong in TYPE30_5. TYPE32 13.084 Support for APARs OW10393 and OW12856. TYPE42 13.066 Fields added by MVS/ESA 5.2 TYPE42 13.217 Support for APAR OW14717 and OW16039 SMF type 42. TYPE42 13.311 Support for DFSMS/MVS 1.3 VSAM RLS new subtypes. TYPE50 13.188 Variable WRBUFUSE added to dataset TYPE50. TYPE6 13.056 4-Digit remote support incomplete. TYPE6 13.309 INPUT STATEMENT EXCEEDED for PSF type 6 with BINS. TYPE64 13.312 Support for DFSMS/MVS 1.3 VSAM RLS new variables. TYPE72GO 13.236 Delay percentages calculation was incorrect. TYPE74 13.004 MVS/ESAs 5.1 TYPE74ST dataset had duplicate/missing. TYPE74 13.035 Support for APAR OW04653 added to TYPE74ST dataset. TYPE80A 12.323 Invalid SUBSTR function, STOPOVER error corrected. TYPE80A 13.254 Support for TOPSECRET 4.4/5.0 (INCOMPATIBLE) records. TYPE91 13.189 INVALID DATA FOR AFSTTIME in SMF type 91 fixed. TYPE92 13.155 Support for OpenMVS File System I/O SMF type 92. TYPE92 13.313 Support for MVS/ESA 5.2.2 Open Edition INCOMPATIBLE. VMACEXC2 13.329 Supression of excess INVALID DEVICE messages VMAC102 13.273 Support for DB2 4.1 IFCIDs 221, 222, and 231. VMAC110S 13.323 CICS 2.1 and SAP journal segments intermixed fix. VMXGDUR 13.305 Rename internal variables DATE HOUR DAY DAYM etc. VMXGHSM 13.108 Dataset DGN corrected for multiple dump copies. VMXGINIT 13.033 New macro variable, &MXGDEBUG is now GLOBALed. VMXGSUM 13.152 VMXGSUM incompatible for user-written invocations. VMXGSUM 13.276 "XMXGSUM" architecture now replaces VMXGSUM. XMXGSUM 13.097 Final validation enhancements. YEAR2000 13.110 MXG Position Paper on support for the Year2000. YEAR2000 13.158 Phase one support for the Year2000.
VMACDCOL the format for variable DCVDVNUM be changed from HEX3 to Jan 19, 1996 HEX4. Thanks to Astrid Fridtun, Statens datasentral, NORWAY. Change 13.331 Although DCOLLECT should be used instead of this old MXG ASMVTOC Assembly routine, the program has been enhanced to handle VMXGVTOC 4-digit UCB addresses, and VMXGVTOC has been modified to Jan 18, 1996 look for the 4-digit address at the end of the record created by ASMVTOC. Thanks to Astrid Fridtun, Statens datasentral, NORWAY. Change 13.330 Although DCOLLECT should be used instead of this old MXG ASMVVDS Assembly routine, the program has been enhanced to handle Jan 18, 1996 4-digit UCB addresses. The TYPEVVDS program was already written to support 4-digit addresses, so it was okay! Thanks to Astrid Fridtun, Statens datasentral, NORWAY.
VMACEXC2 DD segment with non-zero EXCPCNT that has DEVCLASS=00, Jan 18, 1996 DEVTYPE=00, and DEVNR=00, because MXG does not know what to do with EXCPCNT in a DD segment which has no device! However, the message is printed for EACH DD, filling the SAS log with these messages from an MVS 3.1.3 system. No other site has encountered the problem, and the site is investigating to determine what is unique there, but to prevent filling the log, the PUT statement is now limited to the first ten occurrences. The existing EXC2ERR1=1; statement was changed to EXC2ERR1+1; to make it a counter and a new line inserted between that statement and the PUT statement reading IF EXC2ERR1 LE 10 THEN so that the message is supressed after ten occurrences. Thanks to Warick Smith, Sun Alliance & Royal Insurance, AUSTRALIA.
IMACDOS again changed the records INCOMPATIBLY, so you must EDIT TYPEDOS member IMACDOS to specify OFFSET=0 and INPUT @43 RECID. Jan 17, 1996 to process POWER 5.2 records. -Additionally, the choice between "American" MMDDYY dates and "European" DDMMYY dates was externalized into member IMACDOS (previously, you had to actually change the code in member TYPEDOS for European formats.). If you have a member IMACDOS in your USERID.SOURCLIB, you must replace your existing IMACDOS with IMACDOS from MXG 13.13, or you will get a VARIABLE _MMDDYY IS UNINITIALIZED message. Fortunately, even with that message, if your dates are in American format, MXG 13.13 will still work correctly with your old IMACDOS. If your dates are in European format and you use the old IMACDOS, you will also get messages INVALID ARGUMENT TO FUNCTION MDY and your date values will be missing until you replace your old IMACDOS with the IMACDOS from MXG 13.13 (and tailor it for European). -Finally, MXG code was corrected for the Reader record and variable FROUSRID $EBCDIC8. is now INPUT after LOCLNODE is read in. Without this correction, an INPUT STATEMENT EXCEEDED RECORD LENGTH error occurred if a reader record did not contain a Network Account Number. Thanks to ???, Alenia, ITALY. Change 13.327 The statement %INCLUDE SOURCLIB(IMACZDAT); must be TYPEMON8 %%INCLUDE SOURCLIB(IMACZDAT); because it is TESTUSER inside an old-style macro definition (and TYPEMON8 was Jan 17, 1996 inadvertently removed from TESTUSER, so I missed this!) MXG 13.07 thru MXG 13.09 only. Thanks to Andrew Scales, Nissan UK, ENGLAND. Change 13.326 IDMS Severity Code, TASMSSEV no longer exists in IDMS 12, VMACIDMS and variable TASABMSG was miscalculated. The statement Jan 16, 1996 TASMSSEV=MOD(TASABMSG,10); was replaced with TASMSSEV=0; and the statement TASABMSG=INT(TASABMSG/10); was deleted. Also, variables DBKKYFMT and DBKLTYPE are now formatted as HEX8 and DBKOWNER as $HEX2 so as to be recognized by IDMS-literate database administrators in their tongue! Thanks to Martin Wieland, Neckermann B.V., THE NETHERLANDS. Change 13.325 Support for Catalog Records (Exported with IDCAMS). A EXCTLGC1 separate dataset for each of the 13 Catalog Segments is EXCTLGC2 created for complete decoding of all possible segments EXCTLGC3 (and variable CATRECNR can be used to collect all of the EXCTLGC4 segments from a specific catalog record). In addition, EXCTLGC7 two datasets are created from specific records: EXCTLGC8 CTLGDSN - Non-VSAM Data Set record (sequence of catalog EXCTLGC9 segments C1/01/04/04/...). The first five EXCTLGDS VOLSERs are kept in CTLGDSN. EXCTLGD9 CTLGVSAM - VSAM Cluster record record (sequence of EXCTLGE3 C3/01/C4/01/04/.../C9/01/04/04...). The EXCTLGVS first Data VOLSER and the first Index VOLSER EXCTLG01 are kept in CTLGVSAM. EXCTLG02 This preliminary support code detects and deletes a few EXCTLG03 "strange" records (always at the beginning of the Export EXCTLG04 file), printing messages on the log. After MXG 13.13 is EXCTLG05 built and early users have played with this new support, EXCTLG06 I intend to examine the strange records further. I also IMACCTLG need feedback as to intended use of the catalog records TYPECTLG to enhance contents of the record-level datasets CTLGDSN VMACCTLG and CTLGVSAM (and may need to add a CTLGGDG dataset!). Jan 16, 1996 See documentation in the member on usage. Thanks to Dale Houg, Kraft Foods, USA.
READDB2 were written to //WORK, but then inadvertently deleted! Jan 13, 1996 Now, they will remain in the //WORK file as requested.
VMAC110S be in a subtype=0 type 110 record) are intermixed with Jan 13, 1996 IBM performance records in records with subtype=1, and no one at SAP AG can tell why! (See text of Change 13.261). This problem has only been seen with CICS 2.1 (which is already off IBM support) at one site, and they were smart enough to create logic to deal with that aberration and share it with me, so I have created new member VMAC110S by adding their workaround to the MXG 13.13 VMAC110 code. I do not have test data records but have a hex dump of an example bad record and have validated their logic in that manner. If you still have CICS 2.1 and have SAP writing data to the type 110, you should test this new member and compare the number of observations output in all of the CICxxxxx datasets; if they are the same, you need not use VMAC110S, but if you have the defective records, the normal VMAC110 will throwaway records and you will have fewer observations output (or SAS may loop!). To use the VMAC110S member instead of the normal VMAC110, copy member VMAC110S into your USERID.SOURCLIB library and rename it to VMAC110. Thanks to Paolo Carloni, Agip petroli SPA, ITALY. Change 13.322 Hex dumps of BETA93 release 01.06.50 records have now VMACBETA been reviewed (See Change 13.304) and they show new time Jan 13, 1996 values are misdocumented by the vendor. Some binary are actually HH MM SS in PK1. fields, some HHMMSS are SMFSTAMP8, and one SMFSTAMP8. field is reversed (date first, time 2nd!). This change should complete support for the new release.
DOC ZMACTMVS, and VMAC members 110, 110M, 30, 33, 42, 60, 74, Jan 13, 1996 80A, 84, BETA, CMF, DCOL, HPAI, HPCS, LMS, MEMO, NDM, NSPY, RRTM, SAMS, and TPX. Thanks to Freddie Arie, Lone Star Gas, TEXAS.
BUILDPDB under MVS, because CODEPASS is an MVS-only option, but BUILD001 it causes an ERROR 2-12 INVALID OPTION NAME under ASCII Jan 13, 1996 SAS. (In actuality, CODEPASS=2 is an MVS compiler option that has no measurable effect on BUILDPDB, but if the default CODEPASS=1 is in effect, SAS prints a note on the log suggesting that CODEPASS=2 might reduce run time so I specify CODEPASS=2 mostly to suppress the message, rather than for any performance improvement.)
FORMATS or OTHER=("vertical bar" $HEX2. "vertical bar") cannot Jan 12, 1996 be used on both EBCDIC and ASCII platforms. The left and right brackets do not exist on MVS, and the vertical bar ('4F on MVS) becomes '5D'x on ASCII, which must be changed to '7C'x to work under ASCII. Fortunately, the CHARCODE system option allows a pair of characters to replace right and left brackets, so the syntax of OTHER= ?< $HEX2. ?> can be used, as long as the code is preceded by OPTIONS CHARCODE;, which has now been added in the FORMATS member to allow this part of MXG to execute transparently under either ASCII or MVS. Thanks to Terry Poole, SAS Institute Cary, USA.
VMACVMXA was significantly higher than VMDTTIME, because the data Jan 11, 1996 for the time from end of last interval to logoff was not captured. Initially, Ian's rework of the VXBYUSR code was to use the USEINT data, but he is now convinced that that data is not complete, and he has suggested to IBM to include that CPU time (the time from logon to the first interval) in the USELOF data. Now, however, his rework produces more VMDTTIME from the combined USEACT & USEINT datasets than the sum of PFXUTIME and PFXTMSYS derived from the SYTPRP records! I have implemented Ian's design in new macro _TESTMWX, which you can use in place of the normal TESTMW macro, to see how the CPU times captured in the user records (VMDTTIME) compares at your site. Please let me know your results; this note will be updated based on your feedback of his algorithm. 2016: No feedback was ever received, use _DBYUSR/_DELTALL Thanks to Ian Davis, Worker's Compensation Board of Alberta, CANADA. Change 13.317 Support for FRYE Systems LAN monitor for NETWARE. ADOCFRYE Their monitor stores data into five DbaseIII files. This ASUMFRYE support uses PROC DBF (a part of PROC ACCESS) to convert GRAFFRYA DbaseIII into SAS files, and produces some very nice SAS GRAFFRYT plots from the resultant file. This code can only be IMACFRYE executed on a SAS ASCII platform, as the DBase files can TRNDFRYE not be uploaded to a mainframe, and PROC DBF only exists TYPEFRYE on ASCII systems. The member ADOCTYPE provides early VMACFRYE documentation of the Netware data captured, and also has Jan 11, 1996 three examples of converting DbaseIII into SAS (PROC DBF, PROC ACCESS, and a DATA step). Thanks to Chuck Hopf, MBNA, USA. Change 13.316 Variables WRHITPCT, RDHITPCT, CHITPCT, CACHRATE, DASDRATE FORMATS HITPCT and CIOPCT in datasets TYPE42SR and TYPE42DS and VMAC42 the twelve S42AMxxx variables in TYPE42DS were not set to Jan 11, 1996 a missing value when they could not be calculated or when the fields did not exist, so values from a prior segment in the same record were carried forward incorrectly. An ELSE clause now sets these variables missing when needed. The TYPE42DS records variable INTVCLOS indicates whether the record is for an Interval or Close event, and I had thought the Close record contained total counts for the Yüklə 28,67 Mb. Dostları ilə paylaş:
|