* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
were no errors in the other MXG-build RMF III datasets. -Unrelated, new variable INFILENX contains the DSNAME or ASCII filename of the input RMFBSAM file being read. -Macro variable &VMXGJFCB is created to extract the JFCB when TYPERMFV is executed on z/OS and to specify the RECFM=S370VBS and LRECL=3270 when executed on ASCII so those DCB attributes are not required on the FILENAME. Thanks to James Sterling, DST Systems, USA.
VMACTPMX subtype 5 record added new fields to the SLMSLPER dataset Oct 16, 2012 with SLM Job statistics, and corrected the input and the format for some duration variables that were resolved to seconds (TIME8. instead of my TIME12.2). Thanks to Ken Deering, MVS Solutions, Inc, USA. Change 30.215 z/VM BROKEN CONTROL record error only when MONWRITE input VMACVMXA files were concatenated (but not always!) due to logic Oct 16, 2012 error in MTREPR record's SKIP bytes handling. Thanks to David Campbell, SunTrust, USA. Thanks to Shannon Collinson, SunTrust, USA.
VMXGFIND (e.g., all observations with JESNR=12345) selected all of Oct 11, 2012 the desired observations, but the name of the dataset in title of each output were off by one dataset - the first didn't have a dataset name, and the name in the second title was the name of the first dataset, etc., due to a mislocated RUN; statement.
VMAC110 by incorrectly inserted code, which also corrupted the Oct 10, 2012 CICLDG statistics dataset. Thanks to Leonard DiCristofano, Anixter Inc, USA Change 30.212 Support for APAR OA37016 for zEC12 CRYPTO EXPRESS4S adds FORMATS a new value 10 for Crypto Processor Type CEX4C, which is VMAC7072 added to be decoded by the existing $MGRMFCX format, and, Oct 11, 2012 unrelated, two instances of 'F5'x were changed to dashes. -New variable R7023MSK='VALIDITY*BIT*MASK' is created in dataset TYPE7002. Change 30.211 Change 30.113 accidentally removed the de-accumulation of VMACDB2 DB2STATS variable QISTCOLS in MXG 30.04, when three other Oct 9, 2012 QISTxxxx variables were correctly removed. QISTCOLS is now again de-accumulated. Thanks to Glenn Bowman, Wakefern, USA.
EX102366 The CHAR(decimal) function in DB2 V10 returns different FORMATS data than the same function in DB2 V9, and the IFCID=366 IMAC102 records identify SQL source code that MUST be changed to VMAC102 support the new format. The BIF INCOMPATIBLE option will VMXGINIT restore the CHAR function to its V9 behavior while your READDB2 SQL guru's change their code for DB2 V10. Oct 10, 2012 -READDB2's previous max IFCID of 350 raised now to 450. Thanks to Tony Anderson, Blue Cross Blue Shield of Alabama, USA. Thanks to David McGrady, Blue Cross Blue Shield of Alabama, USA. Change 30.209 Support for APAR OA37826 adds Channel Path Types CIB and EXTY74HO CFP Coupling Facility data in new TYPE74HO dataset with FORMATS both Local and Remote Channel Path Data for CIB & CFP. VMAC74 -New Data Set TYPE74HO: VMXGINIT R744HAID='HOST*CHANNEL*ADAPTER*ID' Oct 7, 2012 R744HAPN='HOST*CHANNEL*ADAPTER*PORT' R744HCHF='R744HCHF*STATUS*FLAGS' R744HCPI='CHANNEL*PATH*IDENTIFIER' R744HFLA='R744HFLA*VALIDITY*BIT*MASK' R744HLAT='CHANNEL*PATH*LATENCY*TIME' R744HOPM='CHANNEL*PATH*OPERATION*MODE' R744HPCP='PHYSICAL*CHANNEL*ID*PCHID' R744HSAP='FOUR*I/O PROCESSOR*ACCESSIBLE' R744HTAP='CHANNEL*PATH*TYPE*ACRONYM' Change 30.208 Support for APAR OA37803 which adds Warning Track VMAC7072 Interrupt Facility. Oct 6, 2012 -TYPE70EC and TYPE70PR new variables: SMF70WTI='DURATION*LP WAS YIELDED*DUE TO WTI' SMF70WTS='WTI-S*RETURNED*WITHIN*GRACE*PERIOD' SMF70WTU='WTI-S*UNABLE*TO RETURN*IN GRACE' Change 30.207 Support for APAR OA39993 which adds Interrupt Delay Time VMAC74 Facility duration. VMAC79 -TYPE74 new variable: Oct 6, 2012 SMF74IDT='INTERRUPT*DELAY*TIME*DURATION' Jan 3, 2012 AVG74IDT='AVERAGE*INTERRUPT*DELAY*TIME*MILLISEC' -TYPE79 new variable: SMF79IDT='Interrupt*Delay*Time*Duration'
VMAC71 (SCM) and Pageable Large Pages on EC12 (zEC12) Server, VMAC75 which are also called "FLASH MEMORY". VMAC78 -TYPE71 new variables: Oct 6, 2012 SMF71ASM='MIN*AVAILABLE*NOT USED*SCM BLOCKS' Nov 13, 2012 SMF71ASV='AVG*AVAILABLE*NOT USED*SCM BLOCKS' Dec 25, 2012 SMF71ASX='MAX*AVAILABLE*NOT USED*SCM BLOCKS' SMF71BSA='AVG*BAD*SCM BLOCKS' SMF71BSM='MIN*BAD*SCM BLOCKS' SMF71BSX='MAX*BAD*SCM BLOCKS' SMF71C1A='AVG*HIGH VIRTUAL*COMMON*MEM PAGES' SMF71C1M='MIN*HIGH VIRTUAL*COMMON*MEM PAGES' SMF71C1X='MAX*HIGH VIRTUAL*COMMON*MEM PAGES' SMF71C4A='AVG*HIGH VIRTUAL*COMMON*ON SCM' SMF71C4M='MIN*HIGH VIRTUAL*COMMON*ON SCM' SMF71C4X='MAX*HIGH VIRTUAL*COMMON*ON SCM' SMF71L1A='AVG*1MB FRAMES*CANBE*USED*FIXED MEMOBJ' SMF71L1M='MIN*1MB FRAMES*CANBE*USED*FIXED MEMOBJ' SMF71L1X='MAX*1MB FRAMES*CANBE*USED*FIXED MEMOBJ' SMF71L2A='AVG*1MB FRAMES*NOT USED*IN LFAREA' SMF71L2M='MIN*1MB FRAMES*NOT USED*IN LFAREA' SMF71L2X='MAX*1MB FRAMES*NOT USED*IN LFAREA' SMF71L3A='AVG*1MB FRAMES*IN USE*IN LFAREA*BY FMEMOBJ' SMF71L3M='MIN*1MB FRAMES*IN USE*IN LFAREA*BY FMEMOBJ' SMF71L3X='MAX*1MB FRAMES*IN USE*IN LFAREA*BY FMEMOBJ' SMF71L4A='AVG*1MB FRAMES*CANBE*USED*PAGEABLE/DREF' SMF71L4M='MIN*1MB FRAMES*CANBE*USED*PAGEABLE/DREF' SMF71L4X='MAX*1MB FRAMES*CANBE*USED*PAGEABLE/DREF' SMF71L5A='AVG*1MB FRAMES*NOT USED*PAGEABLE/DREF' SMF71L5M='MIN*1MB FRAMES*NOT USED*PAGEABLE/DREF' SMF71L5X='MAX*1MB FRAMES*NOT USED*PAGEABLE/DREF' SMF71L6A='AVG*1MB FRAMES*USED BY*PAGEABLE/DREF' SMF71L6M='MIN*1MB FRAMES*USED BY*PAGEABLE/DREF' SMF71L6X='MAX*1MB FRAMES*USED BY*PAGEABLE/DREF' SMF71S1A='AVG*HIGH VIRTUAL*SHARED*MEM PAGES' SMF71S1M='MIN*HIGH VIRTUAL*SHARED*MEM PAGES' SMF71S1X='MAX*HIGH VIRTUAL*SHARED*MEM PAGES' SMF71S5A='AVG*AUX SLOTS*HIGH*SHARED MEM ON DASD' SMF71S5M='MIN*AUX SLOTS*HIGH*SHARED MEM ON DASD' SMF71S5X='MAX*AUX SLOTS*HIGH*SHARED MEM ON DASD' SMF71S6A='AVG*HIGH VIRTUAL*SHARED MEM*ON SCM' SMF71S6M='MIN*HIGH VIRTUAL*SHARED MEM*ON SCM' SMF71S6X='MAX*HIGH VIRTUAL*SHARED MEM*ON SCM' SMF71TSA='AVG*4K SCM*BLOCKS AVAIL*TO ASM' SMF71TSM='MIN*4K SCM*BLOCKS AVAIL*TO ASM' SMF71TSX='MAX*4K SCM*BLOCKS AVAIL*TO ASM' SMF71USA='AVG*SCM BLOCKS*IN USE' SMF71USM='MIN*SCM BLOCKS*IN USE' SMF71USX='MAX*SCM BLOCKS*IN USE' -TYPE75 new flag variables are created for bits, but only SCMPGTYP was added by this APAR - the other bits had not been previously decoded into flag variables: MULTEXPO='MULTIPLE*EXPOSURE*DEVICE?' DEVALTCU='DEVICE HAS*ALTERNATE*CONTROL*UNIT' DEVVALID='DEVMODEL*IS VALID?' SCMPGTYP='PAGE*SPACE*TYPE IS*SCM?' Nov 13: The four variables were added to the KEEP list. -TYPE78PA dataset, new variables added Dec 25: R782FIFRMIN ='MIN FRAMES*CAN BE USED*FIXED*MEMOBJ' R782FIFRNTME='TIME STAMP*OF MIN*FIXED*MEMOBJ' R782FIFRMAX ='MAX FRAMES*CAN BE USED*FIXED*MEMOBJ' R782FIFRXTME='TIME STAMP*OF MAX*FIXED*MEMOBJ' R782FIFRAVG ='AVG FRAMES*CAN BE USED*FIXED*MEMOBJ' R782PAFRMIN ='MIN FRAMES*ARE USED*PAXED*MEMOBJ' R782PAFRNTME='TIME STAMP*OF MIN*PGBL/DREF*MEMOBJ' R782PAFRMAX ='MAX FRAMES*ARE USED*PGBL/DREF*MEMOBJ' R782PAFRXTME='TIME STAMP*OF MAX*PGBL/DREF*MEMOBJ' R782PAFRAVG ='AVG FRAMES*ARE USED*PGBL/DREF*MEMOBJ' -TYPE78PA dataset, these new AVG value variables should have been created, instead of their TOTL value variables, but their TOTL variables are still kept, to be safe. SHBYAVG ='AVG*SHARED*ABOVE 2GB' TOBYAVG ='AVG*ABOVE 2GB' COBYAVG ='AVG*64BIT COMMON 2GB' COMOAVG ='AVG*64BIT*COMMON' LGMOAVG ='AVG*LARGE*MEMOBJ' SHBYAVG ='AVG*SHARED*ABOVE 2GB' SHMOAVG ='AVG*SHARED*ABOVE 2GB' TOBYAVG ='AVG*ABOVE 2GB' TOFRAVG ='AVG*1MB*FRAMES' TOMOAVG ='AVG*64 BIT PRIVATE' -The APAR lists 79.11 as changed, but the APAR did not provide any details at that time. This text will be revised when the APAR text has been updated by IBM. Change 30.205 Variable ACTVOL is added to TMS.TMS dataset: TYPETMS5 ACTVOL ='ACTUAL*PHYSICAL*WHERE*VIRTUAL*OFFLOADED' VMACTMS5 The '20'x bit in FLAG5 is also set when ACTVOL is Oct 6, 2012 populated, but as that is redundant I did not create a new variable for that bit. Thanks to DJ Chen, Florida Department of Corrections, USA. Change 30.204 Support for APAR OA38980 adds new variable to DCOLCLUS: VMACDCOL DCAZFS ='ZFS*DATA*SET?' Oct 6, 2012 and two new variables to DCOLVOLS dataset: DCVFCYLS='FREE*CYLINDERS*ON VOLUME' DCVFTRKS='FREE*TRACKS*ON*VOLUME' Thanks to Michael R. Mayne, Huntsville Hospital System, USA. Change 30.203 Support for JES3 Main Device Scheduler IAT5210 & IAT5918 ASMTAPEE mount messages adds these new variables to PDB.ASUMTAPE ASUMTAPE FIRST5210='FIRST*JES3*IAT5210*DATETIME' VMACTMNT LAST5210='LAST*JES3*IAT5210*RECORD' Oct 8, 2012 NR5210 ='NUMBER*OF JES3*IAT5210*MESSAGES' Nov 30, 2012 VOLF5210='FIRST*JES3*IAT5210*VOLSER' Apr 10, 2013 VOLL5210='LAST*JES3*IAT5210*VOLSER' FIRST5918='FIRST*JES3*IAT5918*DATETIME' LAST5918='LAST*JES3*IAT5918*RECORD' NR5918 ='NUMBER*OF JES3*IAT5918*MESSAGES' to measure the delay from JES3 MDS Mount/Allocate and the dismount event for those pre-execution JES3 tape mounts. The MXGTMNT monitor itself never sees those mounts, which occur prior to the job's execution on z/OS, but the above SYSLOG messages, plus the TYPE21 dismount records provide improved tracking of JES3 mount events. -ASMTAPEE was updated to create SMF subtype 8 records for these messages in this enhancement, which is ML-50. -Only data from the first and last of these JES3 messages are kept in PDB.ASUMTAPE, but you can create subtype 9 records for each of these records if you need to see all of them, using the //MXGMSGID DD documented in ASMTAPEE. -Debugging PROC PRINTs in ASUMTAPE were removed Nov 30. -Added April 2013: INCOMPATIBLE: SORT ORDER OF PDB.ASUMTAPE was changed from BY DEVNR EVENTIME to BY JESNR DEVNR EVENTIME which could cause WEEKBLD/MONTHBLD to NOTSORTED fail, but only if your WEEKBLD/MONTHBLD is prior to Change 29.008, 20.01 which made the NOBY option the default to eliminate all BY statements in those programs). Just remove the BY statement in your tailored WEEKBLD/MONTHBLD. Thanks to Jim Dammeyer, State Farm Mutual Auto Insurance, USA. Thanks to Doug Medland, IBM Canada, CANADA. Thanks to Paul Williams, The Capital Group, USA. Change 30.202 -RMF III Enhancements and Fixes ASMRMFV -Fix for invalid I/O error with messages RMFV033E and Oct 3, 2012 RMFV007S and subsequent U0998 Abend. There is a time Oct 6, 2012 window where RMF III has opened a VSAM data set but not yet written the first sample set. In this situation the number of sample sets is zero, but ASMRMFV did not correctly handle the condition and attempted to read a non-existent sample set causing the error. In this condition the first and last sample timestamps are zero indicating a date of 1900.001. ASMRMFV will now correctly issue message RMFV014I as it does for all date/time selection mismatch conditions and proceed without error to the next RMF III data set. -A new parameter SIZE (alias SZ) is added. This option provides all the features of the existing NONE option that suppresses all output but in addition avoids reading any RMF III tables as input (except the DSH table). The purpose of SIZE is to provide both RMF III index and disk space usage to allow optimum sizing of RMF III VSAM data sets. Options INDEXES and SPACE are forced when SIZE is coded. The I/O activity and reporting with SIZE is much less compared to use of NONE. NONE was intended to also provide a table contents inventory and so may still be useful in some scenarios. -The entire DSH table of 32756 bytes is now output not just the 256 byte header. There is just one DSH record for each RMF III VSAM data set. -The Create Date is now added to message RMFV008I for non-VSAM data sets. The JFCB (Job File Control Block) that is the source of this data always has the current date for all VSAM files and so Create Date is suppressed for them. -A new message RMFV034I will be produced to show the date and time of the LAST CLOSE for each RMF III VSAM file. Although the source field DSIGTODC in the DSH table is documented as "Time data set was created", it is clear from the begin and end sample time stamps that this date stamp is always later than end sample time stamp and so is consistent with a file being closed, not one that was just created. -The SAMPLES FILTERED count in message RMFV103I could be incorrect when an entire data set was filtered by date and time selection. -Prologue documentation in the ASMRMFV source has been updated to provide detail on the NONE and SIZE parameters. -Oct 6: Cosmetic: Message RMFV034I shows OPEN timestamp in the local time zone, and imbedded blanks in 9 other date and time fields. Thanks to Rodger Foreman, Trans Union, USA Thanks to Susan Graham, CapGemini, USA
VMAC113 for debugging (IF SYSTEM='MVSA' ...) was not removed, but Oct 4, 2012 they were also not kept until now! Oct 9. 2012 -Oct 9: Change 30.129 text is now available. Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY
VMACDB2 value in new variable QWHCCTKN when the CTKN offset was VMACDB2H non-zero. QWHCCTKN is an IP address in this format with Oct 2, 2012 an IP address, Port Number, and a timestamp: 162.123.25.218.44485.120605112901 -------------- ----- ------------ | | | | | |-- Unique field ( timestamp real | | | |-- Port address | |- Requester IP Address -Only QWHCATYP=8 (REMOTE UOW) obs have QWHCCTKN in several test SMF files, and many of those =8 observations do not have a value, so MXG's incorrect value in QWHCCV does not appear to have been pervasive. -Previously, there was no "truncated offset" field for QWHCCV, the Correlation ID, and when IBM added the truncated offset field for QWHCCTKN, I misread the DSECT and thought that offset was for the Correlation ID so I INPUTed the new field at that offset into QWHCCV. I now realize that that INPUT was for the new Correlation TOKEN field, QWHCCTKN, which is now correctly INPUTed and KEPT. -Now that QWHCCV has no truncated offset, it's length is restored to $12 instead of $128. Thanks to Sieghart Seith, FIDUCIA IT AG, GERMANY. ====== Changes thru 30.199 were in MXG 30.07 dated Oct 2, 2012========= Change 30.199 DO NOT USE MXG 30.07 DATED OCT 1 OR EARLIER. THOSE WERE EXTY70PR TEST ITERATIONS THAT UNFORTUNATELY HAD A SERIOUS ERROR Oct 2, 2012 AND CREATED ZERO OBSERVATIONS IN TYPE70PR DATASET AND WAY TOO MANY OBS IN TYPE70SP, DUE TO MY ERROR IN MY QA. The EXTY70PR member OUTPUT to _WTY70SP incorrectly; that should have been (AND IS NOW) OUTPUT to _WTY70PR. ====== Changes thru 30.198 were in MXG 30.07 dated Oct 1, 2012========= Change 30.198 These labels for these variable in VMACNMON are VMACNMON misleading and incorrect: they indicate "percentages" Oct 1, 2012 APCPUUSER='PCPU_ALL*USER*PERCENT' APCPUSYS ='PCPU_ALL*SYSTEM*PERCENT' APCPUWAIT='PCPU_ALL*WAIT*PERCENT' APCPUIDLE='PCPU_ALL*IDLE*PERCENT' APCPUBUSY='PCPU_ALL*BUSY' but they are PHYSICAL CP counts: Their labels are now corrected to: APCPUUSER='PHYSICAL*CP*USER' APCPUSYS ='PHYSICAL*CP*SYSTEM' APCPUWAIT='PHYSICAL*CP*WAIT' APCPUIDLE='PHYSICAL*CP*IDLE' APCPUBUSY='PHYSICAL*CP*ENTITLED' Thanks to Lennon L. Marchang, Coca-Cola Company, USA
UTILEXCL USERU and USERDATU. UTILEXCL must be executed to create VMAC110 the IMACEXCL to input those fields, and the four IMACICxx IMACICUR members must be copied into your "USERID.SOURLIB" and the IMACICUT comment block therein removed. IMACICUU
IMACICUV Sep 25, 2012 Thanks to Alex B. Nielsen, KMD, DENMARK. Thanks to Noach Holger, KMD, DENMARK. Change 30.196 Variable QW0247DA was truncated to 8 bytes because it was VMAC102 assigned $HEX16. format and only the first 200 bytes were Sep 24, 2012 input with $VARYING200., but actual data length can be up to 4096, so the INPUT and FORMAT were revised. Thanks to Matthew Chappell, Dept. of Transport Main Roads, Australia
VMACDB2 macro defined in VMACDB2, with CORRNAME=SUBSTR(QHWCCV) so Sep 24, 2012 its length was $12 when QWHCCV is $12. But Change 30.032 (incorrectly!) increased QWHCCV to $128, causing CORRNAME to increase, which then could print warning messages about MULTIPLE LENGTHs. Adding a LENGTH CORRNAME $8; statement to the MACRO _DB2CORR definition in VMACDB2 corrected. However, you should copy that definition into your IMACKEEP member so the same definition is always used at your site, and because some sites have needed to tailor the actual substringing. -Change 30.200 restored QWHCCV to the correct $12 length. Thanks to Alyona Bertneski, JP Morgan, USA.
VMACDB2 INVALID THIRD ARGUMENT for SUBSTR(QMDAACCT,BEG,LENACCT1) Sep 21, 2012 because the QMDAACCT INPUT was $VARYING200. LENACCT1 so the length of QMDAACCT was restricted by the $VARYING200. Thanks to Stephen Donahue, Fidelity Investments, USA.
ASMTAPEE and SYSLOG monitor program has been enhanced. The ML-49 Sep 20, 2012 level removes the requirement of having the tape UCBs PINNed. This eliminates the previous requirement that your operators had to stop and restart the monitor when your tape drive configuration changed, and it eliminates the need for documenting that procedure for operators. The new monitor will now detect that a configuration change has been successfully completed and determine whether or not a tape device was involved. If so, the monitor will automatically suspend processing, rescan the tape device's UCBs, and restart monitoring without user intervention. Old and new levels of MXGTMNT can exist on multiple z/OS systems that share tape devices. Systems with ML-49 will automatically detect the change, systems with prior versions will still need operator intervention when the tape device configuration is changed.
VMACVMXA variables PCTSYST PCTIDLE PCTINTR PCTSOFT PCTIOWT were Sep 19, 2012 all incorrect, because the right-hand variable for each Sep 20, 2012 of those percent calculations was NICEMODE instead of the individual xxxxMODE variable. -Variables PCTUSER/PCTNICE/USERMODE/NICEMODE were reversed in the INPUT statement so they too were wrong. -New PCTSTOL/STOLEMODE is created with the time when the z/VM Hypervisor had stolen the clock ticks. Thanks to Scott Barry, SBBWorks Inc, USA. Change 30.191 JOB to create/update the MXG FORMAT library when you use BLDFORMT CONFIMXG configuration with // EXEC SAS93, needed because Sep 18, 2012 CONFIMXG sets DISP=SHR for LIBNAME LIBRARY: //S1 EXEC SAS93,CONFIG='MXG.SOURCLIB(CONFIMXG)' //MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR //SYSIN DD * LIBNAME LIBRARY CLEAR; LIBNAME LIBRARY "&MXGFORMT" DISP=OLD; %INCLUDE SOURCLIB(FORMATS);
VMACVMXA the length of STSI in VXMTRTOP was increased from 40 to Sep 17, 2012 at least 152 and MXG had $VARYING40., now $VARYING255.
VMXGSUM avoid APPARENT INVOCATION OF CMPRES MACRO messages (z/OS) Sep 17, 2012 but unfortunately Change 30.158 (MXG 30.06) slipped its use back in VMXGSUM, so this change was going to just remove it and live with lots of blank in the error text we were compressing. However, we have discovered that the %CMPRES macro can be replaced using %SYSFUNC: %LET MESSAGE=%SYSFUNC(COMPBL(&MESSAGE)); which eliminated the reference to SASAUTOS. However, the actual cause of this error is that your MXG was incorrectly installed; either your JCL or your CONFIG options are preventing MXG from accessing that macro from the SAS-provided SASAUTOS library. Change 28.128 lists the many ways to correct this install error, but you MUST correct your JCL/CONFIG, as many other MXG programs depend on SASAUTOS. VMXGSUM is protected ONLY because %CMPRES again was not required and could be removed, and because VMXGSUM is used in BUILDPDB and ASUMxxxx members that build PDBs.
FORMATS variables in those existing datasets. VMAC119 -Oct 1: some datetime variables were not length 8. Sep 16, 2012 Oct 1, 2012 Thanks to Randy Shumate, Reed Elsevier Technical Services, USA. Thanks to Tom Erwin, Reed Elsevier Technical Services, USA.
VMACCMF they were ten times too large in CMF06GDA dataset. Sep 15, 2012 Thanks to Alfred Sau, TJX, USA. Thanks to Kevin Luey, TJX, USA.
ANALDB2R -MXGACC01 is an interval summary report with your choice Sep 15, 2012 of selection criteria that provides total and average Sep 17, 2012 values for the important CPU and suspend and get-page variables for the buffer pools with average and max Yüklə 28,67 Mb. Dostları ilə paylaş:
|