* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
to MXG support for split SMF 70 records. Change 23.321. 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. MXG Definitions with regard to MXG Software Changes: COMPATIBLE A change in a data record which did not alter either the location or the format of all of the previously- kept MXG variables is COMPATIBLE, and you can continue to run the old version of MXG software, which will read the new records without error, but none of any new data fields or any new record subtypes will be created/kept until you install the MXG Version with this change. A change that alters any previously kept variable is INCOMPATIBLE, and requires the new version to be used.
data records, if they are COMPATIBLY changed. EXPLOIT Once you use the new MXG Version to read the changed records, all of the new fields, subtypes, etc, that are described in this change will be created in the MXG datasets, so the new MXG Version EXPLOITS the new data, and you have full support of the new data records.
version to fail, visibly or invisibly, with or without error conditions or messages, and the output datasets may contain wrong values and incomplete observations, and/or observations may have been lost.
to process data records that have been INCOMPATIBLY changed by their vendor. III. Online Documentation of MXG Software. MXG Documentation is now described in member DOCUMENT. See also member INDEX, but it may be overwhelming. IV. Changes Log
impact your site. All changes have been made in this MXG Library. Member CHANGES always identifies the actual version and release of MXG Software that is contained in that library. The CHANGES selection on our homepage at http://www.MXG.com is always the most current information on MXG Software status, and is frequently updated.
also described by a selection on the homepage. Please subscribe. The actual code implementation of some changes in MXG SOURCLIB may be different than described in the change text (which might have printed only the critical part of the correction that need be made by users).
at the beginning of the member for additional documentation, since the documentation of new datasets, variables, validation status, and notes, are often found in comments in the source members. _PAGE_ 8 Alphabetical list of important changes in MXG 23.11 after MXG 22.22: Dataset/ Member Change Description Typos 23.012 MXG 22.22 JCLTEST/MXGSASVn had error-causing typos. ANALFIOE 23.074 FICON Open Exchange analysis includes CMR pend time. ANALPATH 23.078 Path Activity Report includes CMR and OTH pend. ASMHSCEX 23.177 ML-34 MXGTMNT GA, has ASMHSCEX for HSC mounts!! ASMRMFV 23.243 Enhancement to RMF III VSAM Support ASMTAPEE 23.177 ML-34 MXGTMNT GA, has ASMHSCEX for HSC mounts!! ASMTAPEE 23.247 ML-36 is now available of MXGTMNT. ASMTAPEE 23.300 ML-37 MXGTMNT monitor now captures SYSLOG messages ASUM70PR 23.021 LP0xxxxx variables were not populated. ASUM70PR 23.069 Short RMF interval impacts PDB.ASUMCEC. ASUM70PR 23.071 PDB.ASUMCEC contains CEC total IFA CPU time ASUM70PR 23.121 BY VARIABLES NOT SORTED corrected, PROC SORT added. ASUM70PR 23.237 Variables NRIFACPU,NRIFLCPU added to PDB.ASUM70PR/CEC ASUM70PR 23.289 RMF Intervals with DURATM less than one minute fix. ASUM70PR 23.322 Support for 60 LPARs - INCOMPATIBLE ASUMCACH 23.073 MODEL, taken from DEVMODEL, added to BY list. ASUMDB2 23.319 Summary of DB2ACCT detail into interval buckets. ASUMMIPS 23.126 RPRTCLAS added to identify Service/Reporting Classes. ASUMTALO 23.104 Enhancement to summarize by "groups". ASUMTALO 23.201 Condition Code (Return Code) 4 in ASUMTALO eliminated ASUMTAPE 23.253 Initial rewrite of ASUMTAPE for TMNT/21 records only. ASUMTAPE 23.300 Now merges SYSLOG, MXGTMNT, and IBM SMF 21s. ASUMTMNT 23.104 Enhancement to summarize by "groups". ASUMUOW 23.240 IRESPTM and ELAPSTM in PDB.ASUMUOW revised. ASUMUOW 23.251 More robust definition of "TRANNAME" in PDB.ASUMUOW. BUILD005 23.197 Hardcoded "SPIN" DD replaced by &SPINOUT. BUILDPD3 23.282 BUILDPD3 now sets Condition/Return Code of zero. BUILDPDB 23.124 Duplicate SMF 30 interval records duped in SMFINTRV. CONFIGV9 23.061 SEQENGINE=V9SEQ now default in CONFIGV9 for 9.1.3. FORMATS 23.144 "Expanded Length" format values revised logic for S2. GRAFWLM 23.234 CPU Utilization graph by goal importance, Enrico's. IMAC6ESS 23.008 Invalid ESS data caused INPUT STATEMENT EXCEEDED. IMACICDA 23.190 Comments only. IMACICDA is not used with IMACEXCL. INSTREAM 23.298 MXG 23.08 only: INSTREAM DD was required, not now. MACKEEP 23.346 DB2 Tailoring Example to add DB2 102 to PDB. MONTHxxx 23.351 &MXGSYSN macro variable for compatibility. MXGABND 23.184 New %LET MXGABND=nnnn forces ABEND for CICS errors. READDB2 23.249 OBID and DBID are decoded in DB2 102 Trace datasets. READDB2 23.287 Selective creation of DB2 datasets and data now easy. READDB2 23.345 New WANTONLY= enhancement for %READDB2 utility. RMFINTRV 23.071 IFA CPU time added to PDB.RMFINTRV RMFINTRV 23.123 CPUIFATM/IFE and BATIFA,CICSIFA,etc now in RMFINTRV. RMFINTRV 23.265 23.05-23.07. IFA/IFE CPU times zero in RMFINTRV wkld. TESTIBM1 23.281 MXG 23.08 only. ERROR: File WORK.TYPE791.DATA does .. TRNDxxxx 23.293 New &INTTRND can change default INTERVAL=WEEK in TRND TYPE102 23.056 Dataset T102S199 was incorrect; only first seg output TYPE102 23.131 Support for DB2 IFCID=313 creates T102S313 dataset. TYPE102 23.160 Many new variables added to T102S106 dataset. TYPE1023 23.231 Support for DB2 IFCIC 225. TYPE110 23.077 CICS STAT RECORD STID=106 message. TYPE110 23.342 Support for CANDLE UMBRELLA optional CICSTRAN data. TYPE115 23.347 Support for MQ for z/OS Version 6.0 (COMPAT) TYPE116 23.049 MQM variable QWHCCV QWHSSSID renamed. TYPE119 23.146 Support for new FTP Server Security Section in st 70. TYPE120 23.164 Support for PQ96144, SM120JHF/JHT corrected. TYPE22 23.175 Support for subtype 11 I/O Configuration Change TYPE26J2 23.277 New UNSPUNJB, JOEPURGE status variables created. TYPE26J3 23.282 HIPER: 23.02-23.08, JES3 only. No obs in TYPE26J3. TYPE30 23.101 Support for APAR OA10901, SMF30ZNF zAAP noralize fact TYPE30 23.292 Support for APAR OA11675, EXCPTOTL max now 4 gig. TYPE30 23.296 TYPE30_6 RESIDTM/ACTIVETM wrapped after 51 days. TYPE30 23.329 Support for SMF30CEPI field, new CPUCIPTM variable. TYPE30_V 23.334 IMACINTV default now OUTPUTs TYPE30_V/PDB.SMFINTRV. TYPE6 23.091 Printway File Transfer, z/OS 1.6 from VPS corrected. TYPE6 23.120 Support for ESS GEPARMKY=004Dx variable ESSMAIL2. TYPE6 23.159 PSF SMF 6 with SMF6LN6=24 another INPUT EXCEEDED. TYPE6 23.284 Print accounting for "Printway" tcp/ip SMF 6 records. TYPE6156 23.219 ICF Catalog 05 record GATGEN and GATWRAP corrected. TYPE70 23.270 PCTIFBYn variables restored to TYPE70 dataset. TYPE70 23.330 Corrections to Split 70/Over 60 LPAR Change 23.321. TYPE70 23.348 Final "70's Record Rewrite", OS/390 support! TYPE7072 23.013 LPARCPUX kept in TYPE70PR for count of reserved CPs TYPE7072 23.070 Correction for IBM inability to have STARTIME right. TYPE7072 23.083 Variable NRCPUD, CPU segments this MVS, added. TYPE7072 23.186 Support for z9 CPU, new CPUTYPE='2094'x, INCOMPAT. TYPE7072 23.187 Support for APAR OA10346 adds LPAR User Partion ID. TYPE7072 23.306 PARTNCPU final correction for z9 microcode error. TYPE7072 23.321 Support for Split RMF 70 Records: INCOMPATIBLE TYPE7072 23.322 Support for 60 LPARs - INCOMPATIBLE TYPE7072 23.335 Variables SMF70OIL and SMF70SYN now KEPT in TYPE70. TYPE70PR 23.288 BMC SMF 70 from z9 have LPARCPUX=0, counts wrong. TYPE73 23.072 Support for APAR OA09921 IBM TotalStorage DS6000. TYPE74 23.029 AVGxxxMS variables now FORMAT 6.3. TYPE74 23.093 Support for Type 74 subtype 8 corrected. TYPE78SP 23.064 TYPE78SP only had below-16MB subpool variables. TYPE79 23.268 RMF 79 subtype 9 records are now validated/corrected. TYPE80A 23.006 Support for many new RACF events. TYPE80A 23.066 Support for RACF Events 27, 28, 29 for unix. TYPE80A 23.134 Unexpected RACF TOK80LN2=0 record was deleted. TYPE80A 23.135 Support for Top Secret Versions 5.2 and 5.3. TYPE80A 23.275 Support for CA TopSecret 103-105,109,255 SMF80DTPs. TYPE82 23.242 Support for SMF type 82 subtypes 20 and 21 added. TYPE88 23.213 All SMF88xxx datetime variables are now local zone. TYPE89 23.183 Support for APAR OA11036 added MACHTIME to SMF 89. TYPE90A 23.081 WLM Service Policy new name tracked in TYPE9024. TYPE99 23.169 Support for SMF 99 Subtype 2 additional segments. TYPEBE91 23.311 Support for Beta 91 Version 3.1.1.0, INCOMPATIBLE. TYPECMF 23.136 Support for 2180 RAID RANK data in CMF user record. TYPECSF2 23.024 CONTROL-D SF2 records INCOMPATIBLY changed. TYPECYFU 23.020 Support for CyberFusion user SMF record. TYPECYFU 23.139 Support for CyberFusion user SMF record validated. TYPEDB2 23.011 DB2 QWHT/QWHU/QWHD/QWHA could be blank/missing. TYPEDB2 23.082 QWHSLOCN CONTAINS UNICODE TEXT message TYPEDB2 23.098 Support for DB2 V8.1 restructured Package Data. TYPEDB2 23.111 Support for DB2 V8.1 Package Data INCOMPATIBLE. TYPEDB2 23.140 REQUIRED FOR DB2 V8.1 More IBM INCOMPATIBLE CHANGES. TYPEDB2 23.181 DB2ACCTP data was still wrong for DB2 V8.1, fixed. TYPEDB2 23.235 DB2TCBTM in DB2ACCT obs with DB2PARTY='R' was wrong. TYPEDB2 23.280 DB2ACCTP Package Data required fix (final, trunc!). TYPEDB2 23.295 DB2ACCTG dataset didn't contain nine QBGA variables. TYPEENDV 23.236 Support for Endeavor Release 7; no changes. TYPEEREP 23.228 INPUT STATEMENT EXCEEDED for IBM ATL record. TYPEHSM 23.179 All byte-containing HSM variables FORMATed MGBYTES. TYPEIMS 23.099 Support for IMS Version 9.1 was already in MXG 22.22 TYPEIPAC 23.223 Support for Mobiud/IPAC Rel 6.3 INCOMPATIBLE. TYPEIWAY 23.133 Support for Iway Software's IWAY (aka EDA/SQL) SMF. TYPEMGCR 23.200 Support for MegaCryption's user SMF record TYPEMPLX 23.027 Support for IMPLEX Versions 3.1 and 3.3 TYPEMPLX 23.143 IMPLEX subtype 4 revised, validated. TYPEMVCI 23.166 Support for additional CMRFILE fields in CMRDETL. TYPEMWSU 23.254 ADOCMWSU for HP MeasureWare on Sun was updated. TYPENDM 23.001 INPUT STATEMENT EXCEEDED for NDM subtype 'SY'. TYPENDM 23.227 NDMCPUTM in NDMCT is now deaccumulated and correct. TYPENDM 23.291 Support for CDI/NDM subtypes HW and NM. TYPENDM 23.331 Support for NDM/Connect Direct subtype TF, TL, TW. TYPEPRPR 23.142 Support for Oce's Prisma Print log file. TYPEQACS 23.007 CPU variables in QAPMJOBL were incorrect. TYPERMFV 23.080 RMF III data for IFAs added to ZRBASI, ZRBENC TYPESAMS 23.004 Support for SAMS Vantage "LSPACE" record subtype. TYPESAMS 23.172 SAMS POOLS record INCOMPATIBLY CHANGED. TYPESARR 23.196 Support for CA SAR/VIEW R11, INCOMPATIBLY CHANGED. TYPESTC 23.022 Support for VSM subtype 20, problems with ST 4. TYPESTC 23.125 Support for HSC V6 changes to STCLMU subtype 4 SMF. TYPESTC 23.279 Support for STK VTCS 6.0 and 6.1 SMF records (COMPAT) TYPESYNC 23.163 New "SMS" UCB Address caused INVALID ARGUMENT error. TYPESYSI 23.258 Support for CA SYSVIEW IMS user SMF records. TYPESYSV 23.137 Support for CA SYSVIEW CICS data in XPFCMCR,XPFCSDCR. TYPETHST 23.076 BMC THRDHIST file contains invalid package records. TYPETMNT 23.300 New TYPESYMT, TYPESYSL datasets from SYSLOG messages. TYPETMO2 23.100 TMON for CICS/TS V2.3 for CICS/TS 3.1. No Changes. TYPETMS5 23.045 Support for TMS Release 11 - no changes. TYPETMS5 23.229 Support for DEVTYPE='3592' devices in CA-1. TYPETMVS 23.294 TYPETMVS CIJN and other CI variables INCOMPAT. TYPETNG 23.113 Zero observations with a Solaris cube. TYPETNG 23.193 Support for TNG AIX CA PROCESS GROUP (PID) object. TYPETPFC 23.199 Support for TPF Continuous Data Collection TPFCDC. TYPETPFC 23.324 TPF Continuous Data rate variables now calculated. TYPEVM 23.285 Support for VM Account optional YYMMDD date format. TYPEVMXA 23.050 z/VM VXBYUSR CPU and DELTATM corrected. TYPEVMXA 23.060 Support for z/VM 5.1 enhanced: all new data supported TYPEVMXA 23.128 z/VM 5.1 record 1.19 misdocumented, caused ERRORs. TYPEVMXA 23.269 z/VM MONWRITE dataset VXSYTEMP is now validated. TYPEVMXA 23.290 z/VM MONWRITE VXSYTEPM dataset finally correct. TYPEVMXA 23.332 Variables HFLLIST,HFPGACT were accumulated. TYPEWWW 23.026 Zero length URIQVALU caused INVALID ARGUMENT. TYPEWWW 23.233 Enhancement/corrections to Web Log support. TYPExxxx 23.052 New EOdddddd, _Odddddd MXG architecture enhancements. UTILBLDP 23.036 CC=4 with BUILDPDB=NO eliminated, now CC=0. UTILBLDP 23.057 Enhanced; USERADD supports SMF record number. UTILBLDP 23.087 EXPDBOUT= a %INCLUDE failed when output executed. UTILCONT 23.025 Failed if DISP=NEW dataset was contented. UTILEXCL 23.075 CMODNAME=RMI,CMODHEAD=DB2CLOCK didn't generate skip. VGETDDS 23.244 Using VGETDDS to get all DDNAMES can fail. VGETENG 23.298 MXG 23.08 only: FILE INSTREAM IN USE. VGETJESN 23.096 Blank TYPETASK in TYPE30_6 data, STCs, corrected. VMXG70PR 23.276 PDB.ASUMCEC PCTL0OV,LP0MGTTM,LPCT0OV were zero. VMXGDUR 23.239 Support for DURATM keywords TENMIN and FIVEMIN. VMXGFOR 23.127 Semi-colon at end of macro invocation in AUTOCALL. VMXGUOW 23.017 Default IMACUOW in 22.22 caused NO BY error. %VMXGVERS 23.005 New %VMXGVERS member embedded to detect old versions. WEEKBLD 23.246 Support for adding un-sorted datasets to WEEKLY PDB. WEEKxxx 23.015 Sort Order for SMFINTRV must be changed WEEKxxx 23.351 &MXGSYSN macro variable for compatibility.
VMAC120 compatibly added 8-byte fields to replace 4-byte fields Feb 18, 2006 in the Server Activity CSS and Server Interval SIL data. MXG stores the new data into the existing variable names, which were already formatted MGBYTES and thus kept long. Thanks to Victoria Lepak, Aetna, USA. Change 23.357 Macro variable "SYSNAME" is renamed "MXGSYSN" as SAS has DOC recommended (SN-012275) that "SYS" not be used as a macro Feb 18, 2006 variable name's prefix. Only sites with duplicate SYSTEM names in the same SYSPLEX will need to change the default value (blank) to "SYSNAME" as noted in Change 23.351. Those sites could simply put this statement %LET MXGSYSN=SYSNAME; in their IMACKEEP member so their WEEKLY/MONTHLY will use SYSNAME in its BY processing. Thanks to Chuck Hopf, MBNA, USA. Change 23.356 Cosmetic, unless you are running a non-PR/SM system. The VMAC7072 recalculation of CPUUPTM and CPUACTTM used the PR/SM vars Feb 17, 2006 and overwrote the just-finished non-PR/SM calculation. Thanks to Douglas C. Walter, CITIGROUP, USA. Change 23.355 Enhancement to DB2PM-like reports, adds CONNTYPE= option ANALDB2R for selection criteria for Accounting Detail (PMACC02). Feb 17, 2006 For example, CONNTYPE=4, selects only CICS connections. Thanks to John Paul, HighMark, USA. Change 23.354 MXG 23.23 PreRel; variable PARTNCPU, the count of engines VMAC7072 in the box/partition, could be too large, if you have ICF Feb 17, 2006 or IFA engines, in some cases. The test to use SMF70BNP Feb 19, 2006 instead of NRCPSCPU (temp count PHYSICAL CPs) was added to protect sites that won't let an LPAR see its physical segments, was replaced with IF NRCPSCPU GT 0 instead of comparing IF PARTNCPU GT NRCPSCPU. -Feb 19: NRCPSCPU was removed from a DROP statement where it didn't belong, but it is NOT a kept variable. -Apr 7: How do you cause SMF 70s to not have a PHYSICAL LPAR segment, and not report on other LPARs? On the HMC, there is a Global Performance Data Control switch, which controls the amount of data returned by the Diagnose instruction RMF uses to obtain CPU utilization information; if not on, the RMF 70s will contain only information on this SYSTEM, and there will be no PHYSICAL segments. Thanks to Stan Adriaensen, Axa-Tech Belgium GIE, BELGIUM. Thanks to Scott Barry, SBBWorks, USA.
FORMATS data, compatibly, to their user SMF records, and new VMACPRPR values for the existing MGPRPRA format, in this perfectly Feb 17, 2006 written user contribution update. Thanks to Siegfried Trantes, IDG, GERMANY. Thanks to Willi Weinberger, IDG, GERMANY. Change 23.352 Short ML-36 SYSLOG record caused INPUT STATEMENT EXCEEDED VMACTMNT error for the subtype 8 record. ASMTAPEE at ML-38 fixes Feb 16, 2006 the short record, and VMACTMNT now tests SYSLLEN before it inputs the MSGID fields in the captured SYSLOG event. Thanks to Keith McWhorter, Georgia Technology Authority, USA.
MONTHASC BY SYSPLEX SYSTEM SYSNAME STARTIME .... MONTHBL3 by inserting SYSNAME, but if SYSNAME does not exist in an MONTHBLD old PDB, your weekly/monthly/etc combining job fails with MONTHBLS ERROR: BY VARIABLE SYSNAME NOT FOUND ON INPUT DATA ... MONTHDSK While MXG must use SYSNAME in its logic, only sites with VMXGINIT duplicate SYSTEM names actually need SYSNAME in their WEEK70PR BY list for their weekly/monthly jobs, so this change: WEEKBL3 - defines macro variable &MXGSYSN, with blank value WEEKBL3D - uses &MXGSYSN in BY statements for post processing of WEEKBL3T daily/weekly/monthly datasets. WEEKBLD With the blank default, then your weekly/monthly jobs WEEKBLDD will not fail when old/new RMF datasets with/without the WEEKBLDT SYSNAME variable are combined. Feb 15, 2006 If you have duplicate SYSTEM names, then when all of Feb 18, 2006 the input datasets to the week/month merge contain variable SYSNAME, you would then use this statement %LET MXGSYSN=SYSNAME; %INCLUDE SOURCLIB(Weekbld, monthbld, ... etc); Feb 18: The PreRelease use macro variable "SYSNAME" but Change 23.357 changed it to MXGSYSN.
VMAC110 instead of "ATTACHES". Feb 15, 2006 Thanks to Don Deese, (CPExpert), Computer Management Sciences, USA. Change 23.349 The exit _EPDBOUT is again invoked when BUILDPDB=NO; it UTILBLDP had been in MXG 22.22, but was lost along the way. Note, Feb 15, 2006 however, that EXPDBOUT=_EPDBOUT and BUILDPDB=YES can not Feb 16, 2006 be used together, and a new warning message will be print if they are both specified. -Feb 16, 2006: Revised so EXPDBOUT= argument is now always created either when BUILDPDB=YES is used or if EXPDBOUT argument is non-blank. Thanks to Scott Barry, SBBWorks, Inc, USA. Thanks to Robbie A. McCoy, Salt River Project, USA. Change 23.348 Final (?) "70's Record Rewrites" change, for OS/390 R2.1! VMAC7072 The last error in validation was caused by really old RMF VMXG70PR records from OS/390 R2.1 that didn't have SMF70CIN field, VMXGRMFI which caused PARTNCPU to be zero. The revision uses the Feb 14, 2006 value in SMF70BNP when SMF70CIN is not populated. -PROC DELETEs were added for a few WORK datasets that were not deleted after their last use, but now are. Thanks to Dr. Alexander Raeder, AtosOrigin, GERMANY. Change 23.347 Support for Websphere MQ for z/OS Version 6.0 (COMPAT). VMAC115 -Added compatibly, i.e., at end of SMF 115 records: VMAC116 Data Set MQMMSGDM new sets of duration variables: Feb 14, 2006 LMSDEL ='DB2 BLOB*DELETE*REQUESTS' LMSDSCUW='DB2 BLOB DELETE*SQL DELETE*CUM-TM' LMSDSMXW='DB2 BLOB DELETE*SQL DELETE*MAX-TM' LMSDTCUW='DB2 BLOB DELETE*THREAD DELETE*CUM-TM' LMSDTMXW='DB2 BLOB DELETE*THREAD DELETE*MAX-TM' LMSINS ='DB2 BLOB*INSERT*REQUESTS' LMSISCUW='DB2 BLOB WRITE*SQL DELETE*CUM-TM' LMSISMXW='DB2 BLOB WRITE*SQL DELETE*MAX-TM' LMSITCUW='DB2 BLOB WRITE*THREAD DELETE*CUM-TM' LMSITMXW='DB2 BLOB WRITE*THREAD DELETE*MAX-TM' LMSLIS ='DB2 BLOB*LIST*REQUESTS' LMSLSCUW='DB2 BLOB LIST*SQL DELETE*CUM-TM' LMSLSMXW='DB2 BLOB LIST*SQL DELETE*MAX-TM' LMSLTCUW='DB2 BLOB LIST*THREAD DELETE*CUM-TM' LMSLTMXW='DB2 BLOB LIST*THREAD DELETE*MAX-TM' LMSSEL ='DB2 BLOB*READ*REQUESTS' LMSSSCUW='DB2 BLOB READ*SQL DELETE*CUM-TM' LMSSSMXW='DB2 BLOB READ*SQL DELETE*MAX-TM' LMSSTCUW='DB2 BLOB READ*THREAD DELETE*CUM-TM' LMSSTMXW='DB2 BLOB READ*THREAD DELETE*MAX-TM' LMSUPD ='DB2 BLOB*UPDATE*REQUESTS' LMSUSCUW='DB2 BLOB UPDATE*SQL DELETE*CUM-TM' LMSUSMXW='DB2 BLOB UPDATE*SQL DELETE*MAX-TM' LMSUTCUW='DB2 BLOB UPDATE*THREAD DELETE*CUM-TM' LMSUTMXW='DB2 BLOB UPDATE*THREAD DELETE*MAX-TM' A BLOB object is used to access binary large objects (BLOBs), such as sound byte (wav) or image (gif) file, using the DB2Blob interface with Java 2. With the BLOB class, the LOB threshold property specifies the maximum large object (LOB) size (in kilobytes) retrieved as part of a result set. LOBs over that threshold are retrieved in pieces, requiring communications overhead with the server, so they can reduce the frequency of communications, but they also download more LOB data, that unwanted data that was never used. Smaller LOBs may increase the frequency of communications with server, but may move much wasted data. -Added compatibly, i.e., at end of SMF 116 records: Data Set MQMACCTQ: WTASVER ='WTAS*VERSION*NUMBER' WTASDBPT='WTAS*DB2 BYTES*WRITTEN' WTASDBGT='WTAS*DB2 BYTES*READ' Data Set MQMQUEUE: WQFLAGS '=FLAGS' Yüklə 28,67 Mb. Dostları ilə paylaş:
|