* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
Sep 15, 2016 Thanks to Robert Chavez, Florida Power and Light, USA. Change 34.210 Some USS RACF Event values (28 thru 58 decimal) were not FORMATS decoded in MG080EV and $MGSMFID formats. Sep 15, 2016 Thanks to MP Welch, Bank of America, USA. Change 34.209 "DB2 is filling my SMF, how do I find out who/why" may be DB2COUNT answered with DB2COUNT program that reads SMF 101 records Sep 13, 2016 creating a stripped down PDB.DB2ACCT with the identity variables and PROC FREQs to provide counts of who/why and then ANALDB2T reports on the top resource consumers.
VMAC74 but they contained bytes. Now they are in MB Per Second: Sep 11, 2016 R749PCIDMAR/MAW R749FPGCOBS/DCBS R749PCIBYTR/BYTT R749FPGBYTS. And R749FPGBYTR Average Request is now KB. -Variable R749FPGBPRT is now equated to R7491BPC for the Buffer Pool utilization. Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
VMXGRMFI or even TWOHOUR could produce incorrect results with no Sep 14, 2016 error messages. The value of SHIFT could be incorrect, which could cause the date to be one day wrong. Only user-created invocation of VMXGRMFI are exposed; none of the MXG-supplied VMXGRMFI members have large intervals. -The exposure is when the requested INTERVAL spanned a shift boundary or did not align perfectly with the shift times; to get FOURHOUR FOURHOUR summary you must have SHIFT boundaries of at 0/4/8/12/16/20. -Using INTERVAL=SHIFT produced wrong results if your interval spans a shift boundary, but it is likely that what you really wanted was by DATE and SHIFT, so VMXGRMFI has new INTERVAL=DATESHIFT/WEEKSHIFT/MONTHSHIFT/ MONTHSHIFT/QUARTERSHIFT/SEMIANNSHIFT/ANNUALSHIFT. These new options set the INTERVAL=DATE/WEEK/etc., and add variable SHIFT to the end of the SUMBY list. In addition, new &RMFIBY macro variable with default RMFIBY=SYSPLEX SYSTEM SYSNAME STARTIME is created to allow more extensive tailoring if needed. If you use this interval structure (xxxxSHIFT) you must also use the same RMFIBY to put the resulting data through TRENDing to preserver the SHIFT value. -SHIFT added to the RMFWKLRV dataset. -SHIFT is blank for INTERVAL= that span shifts (DATE, etc) since there is no value possible with multiple shifts. -Two PROC SORTs were replaced by MEANS with CLASS.. -If Reporting Classes are used for Workload Definitions, the WKLDDESC='REPORTING CLASS' value is set for that variable because they don't have WLM WORKLOAD values. -Messages that SRV was found in TYPE72GO input are now always printed; this is NOT due to MXG but is a fall-thru service class used by IBM when your WLM rules failed to classify work, and should never exist. Thanks to Andre Gustavo Moretto, IBM Global at Delta, USA.
VMAC80A Without change, dataset TYPE80TS had zero observations. Sep 7, 2016 -Support for Top Secret R16. Added RACFVRSN='10'x test on Oct 5, 2016 Oct 5. Nov 5, 2016 -Format $MG080TS created to map Resource Code to Class by FORMATS reading the RDT.TXT table. A program to re-create that format is in comments at the end of this VMAC80A. Thanks to Carl D. Ellis, Wells Fargo, USA. Change 34.205 SMF 6 UNDECODED KEYS and INPUT EXCEEDED STOPOVER error IMAC6ESS because MXG only expected 4 USERLIB segments. ESSULIB5/6 VMAC6 are now input and kept and more than 6 now protected. Sep 6, 2016 Thanks to Sabrina Mandelatz, ProvinzialRheinlandVersicherung, GERMANY
VMXGRMFI -TRND70PR incorrectly used variable name DATETIME when it TRND70PR should have used STARTIME in the SUMBY list, which worked Sep 2, 2016 accidentally. Oct 2, 2016 -STARTIME removed from ID statement Oct 2. Thanks to Andre G. Moretto, Delta Air Lines, USA. Change 34.203 Cosmetic. All "CICS EXCLUDED FIELDS FOUND" messages now VMAC110 contain the READTIME value of that APPLID, which is when Sep 2, 2016 the CICS Dictionary Record is written, so you know what SMF data to select for UTILEXCL Change 34.202 Support for Connect Direct Simultaneous Session CDHW SMF EXCDHWSS creates new dataset IMACCDHW DDDDDD DATASET DESCRIPTION TYPECDHW CDHWSS CDHWSSES CD SIMULTANEOUS SESSIONS TYPSCDHW VMACCDHW
VMXGINIT Aug 29, 2016 Thanks to Scott Wiig, USBank, USA. Thanks to David Magoon, USBank, USA. Change 34.201 Support for CDI-NDM Version 5.2 (INCOMPATIBLE). VMACNDM Incomplete, not moved to 34.07, no data yet. Aug 29, 2016 Thanks to Michael Oujesky, DTCC, USA. Change 34.200 -SMF 115 dataset MQMLOG is enhanced with new variables VMAC115 QWHSDURN='INTERVAL*DURATION' VMACDB2H PCTLOGBY='PERCENT*LOG*BUSY' Aug 24, 2016 QWHSTIME='MQ*INTERNAL*START*DATETIME' Sep 13, 2016 -Sep 13: Protection for old versions with QWHSLEN=36 added Sep 16, 2016 and missing values calculations eliminated. Sep 22, 2016 -Sep 16: Variables added to MQMLOG dataset: Sep 24, 2016 QJSTSLPTU ='PHYSICAL*WRITER*SLEEP*DURATION' Oct 11, 2016 QJSTIOSQU1='SSQ*IO TIME*1ST HALF' QJSTIOSQU2='SSQ*IO TIME*2ND HALF' -Sep 22: QJST busy time is now created and calculated as QJSTBUSY=100*(QWHSDURN-QJSTSLPTU)/QWHSDURN; -Sep 24: GMT115TM is now correctly calculated and used to shift the QJSTIOMAXxxxx datetimestamps to LOCAL zone. -Oct 11: Labels improved for vars QJSTBUSY, QJSTSLPTU.
Thanks to Joseph J. Faska, DTCC, USA Change 34.199 -RMF III dataset ZRBDVT variable DVTLCUNR was always zero VMACRMFV and DVTSAMPP was trashed, due to mis-alignment in MXG. Aug 24, 2016 -Variable DVTSSID='SUBCHANNEL*SET' is now INPUT and KEPT. Aug 30, 2016 -Variable GEIAHUIC is now INPUT as Floating Point. -Variable GEIFLG1 is now INPUT and KEPT.
ADOCRMFV and TOTIME= parameters using the current Time of Day ASMRMFV (TOD) timestamp. Aug 18, 2016 -The TOD value as shown in the ASMRMFV RMFV001I log Aug 20, 2016 message and obtained as execution begins is the basis for Relative Time calculations. -Relative Times are specified as either hour or minute offsets from the current TOD. The default is hours if the unit is not explicitly coded. -Improved handling of midnight crossover condition when Relative Time offset exceeds current TOD Time. -All of the following formats are supported for FROMTIME= Relative Times: FROMTIME=*- FROMTIME=- FROMTIME=*- FROMTIME=*-0 FROMTIME=-0 FROMTIME=*-00 FROMTIME=-00 FROMTIME=*-0H FROMTIME=-0H FROMTIME=*-00H FROMTIME=-00H FROMTIME=*-0M FROMTIME=-0M FROMTIME=*-00M FROMTIME=-00M FROMTIME=*-000M FROMTIME=-000M FROMTIME=*-0000M FROMTIME=-0000M h is hours (0-9) hh is hours (00-24) m is minutes (0-9) mm is minutes (00-99) mmm is minutes (000-999) mmmm is minutes (0000-1440) -The maximum hour offset supported is 24 hours. The maximum minute offset supported is 1440 minutes. -'H' suffix is optional for hour offsets. 'M' suffix is required for minute offsets. -The default offset is 0 hours for these formats: FROMTIME=* FROMTIME=*- FROMTIME=- -The following forms for FROMTIME= all result in the current TOD being used as a data selection start time:
FROMTIME=*- FROMTIME=- FROMTIME=*- FROMTIME=*-0 FROMTIME=-0 FROMTIME=*-00 FROMTIME=-00 FROMTIME=*-0H FROMTIME=-0H FROMTIME=*-00H FROMTIME=-00H FROMTIME=*-0M FROMTIME=-0M FROMTIME=*-00M FROMTIME=-00M FROMTIME=*-000M FROMTIME=-000M FROMTIME=*-0000M FROMTIME=-0000M -These forms are of no practical use when FROMDATE=* (current date) is also coded because the selection start time will result in little if any data being actually output. -The use of Relative Time with FROMTIME= does not change the FROMDATE= value whether defaulted or coded. These two parameters remain independent. -The Relative Time process for FROMTIME= follows these steps:
-1. The hour or minute time offset requested is deducted from the time portion of the current TOD clock value. -2. If the result of the time offset deduction is negative and the active FROMDATE= value also the current date, then the FROMTIME= value is forced to 00:00:00.000000 (midnight). -3. If the result of the offset deduction is negative and the active FROMDATE= value is NOT the current date, then the portion of hours or minutes that exceeds the elapsed time for the current date crosses midnight. See example below for more detail. -To summarize the midnight crossing support where '*' represents the current date: FROMTIME= FROMDATE= Time Offset Result --------- ------------- ------------------ * LE Current TOD Midnight cross N/A * GT Current TOD FROMTIME 00:00:00.000000 Not * LE Current TOD Midnight cross N/A Not * GT Current TOD Midnight crossed The midnight cross time is calculated as: Current time - FROMTIME time offset + time in 1 day -4. The FROMTIME= value for an hours offset is truncated to the start of the hour while the FROMTIME= value for a minutes offset is truncated to the start of the minute.
from beginning at an odd time. -To summarize the Relative Time results for FROMTIME=: TIME TRUNCATED OFFSET UNIT FROMTIME= ----------- --------------- Default (Hours) HH:00:00.000000 H (Hours) HH:00:00.000000 M (Minutes) HH:MM:00.000000 -Examples for FROMTIME= Relative Time usage follow. For these examples assume the current TOD is: DATE=2016.251 01SEP2016 THU TIME=09:26:56.776233 -Example 1: FROMDATE=* FROMTIME=*-3 is a 3 hour TOD Relative Time offset for the current day results in: FROM DATE=2016.251 01SEP2016 THU TIME=06:00:00.000000 TO DATE=2042.259 16SEP2042 TUE TIME=23:59:59.999999 Note that a pure offset of 3 hours only would have resulted in a FROMTIME= of 06:26:56.776233 which is an awkward time stamp for the start of data selection. So the start of the hour is provided. -Example 2: FROMDATE=* FROMTIME=*-10 is a 10 hour TOD Relative Time offset and results in: FROM DATE=2016.251 01SEP2016 THU TIME=00:00:00.000000 TO DATE=2042.259 16SEP2042 TUE TIME=23:59:59.999999 since the Relative Time offset extends beyond midnight into the prior day and FROMDATE= is the current date, the FROMTIME= was forced to midnight. -Example 3: FROMDATE=*-1 FROMTIME=*-10 is a 3 hour current TOD Relative Time offset with a FROMDATE= of yesterday and results in: FROM DATE=2016.250 31AUG2016 WED TIME=23:00:00.000000 TO DATE=2042.259 16SEP2042 TUE TIME=23:59:59.999999 since FROMDATE= is NOT the current date, the FROMTIME= offset is allowed to cross midnight by 1 hour in this example. To achieve the cross midnight time behavior FROMDATE= must NOT be the current date. -To use the midnight crossing feature effectively a user must anticipate a midnight crossover based on the size of the Relative Time FROMTIME= offset being used and when ASMRMFV is going to be run. Usually FROMDATE=*-1 is coded rather than FROMDATE=* if the midnight time crossover is expected. -However, any FROMDATE= value that is not the current date may be used and the midnight crossing will still occur. -Example 4: FROMDATE=* FROMTIME=*-30M is a 30 minute current TOD Relative Time offset and results in: FROM DATE=2016.251 01SEP2016 THU TIME=08:56:00.000000 TO DATE=2042.259 16SEP2042 TUE TIME=23:59:59.999999 -Example 5: FROMDATE=* FROMTIME=30M is a parameter error because at least the '-' character must follow FROMTIME= to indicate a Relative Time. ASMRMFV will abend. -All of the following formats are supported for TOTIME= Relative Times: TOTIME=*
TOTIME=*- TOTIME=- TOTIME=*-h TOTIME=-h TOTIME=*-hh TOTIME=-hh TOTIME=*-hH TOTIME=-hH TOTIME=*-hhH TOTIME=-hhH TOTIME=*-mM TOTIME=-mM TOTIME=*-mmM TOTIME=-mmM TOTIME=*-mmmM TOTIME=-mmmM TOTIME=*-mmmmM TOTIME=-mmmmM -The meanings for h, hh, m, mm, mmm, mmmm, H, and M are the same as for the FROMTIME= parameter. -Hour and minute offset limits are the same as for FROMTIME= Relative Times. -'H' suffix is optional for hour offsets 'M' suffix is required for minute offsets -The default offset is 0 hours for these formats: TOTIME=* TOTIME=*- TOTIME=- -The following forms for TOTIME= all result in the current TOD being used as a data selection end time: TOTIME=*- TOTIME=- TOTIME=*- TOTIME=*-0 TOTIME=-0 TOTIME=*-00 TOTIME=-00 TOTIME=*-0H TOTIME=-0H TOTIME=*-00H TOTIME=-00H TOTIME=*-0M TOTIME=-0M TOTIME=*-00M TOTIME=-00M TOTIME=*-000M TOTIME=-000M TOTIME=*-0000M TOTIME=-0000M -However, when TODATE=* is also used it is unnecessary to code these forms because the default TOTIME= is: DATE=2042.259 16SEP2042 TUE TIME=23:59:59.999999 -The use of Relative Time with TOTIME= does not change the TODATE= value whether defaulted or coded. These two parameters remain independent. -The Relative Time process for TOTIME= follows these steps:
-1. The hour or minute time offset requested is deducted from the time portion of the current TOD clock value. -2. If the result of the offset deduction is negative and the active TODATE= value is also the current date, then the TOTIME= value is forced to 00:00:59.999999. -3. If the result of the offset deduction is negative and the active TODATE= value is NOT the current date, then the portion of hours or minutes that exceeds the elapsed time for the current date crosses midnight. See example below for more detail. -To summarize the midnight crossing support where '*' represents the current date: TOTIME= TODATE= Time Offset Result --------- ------------- ------------------ * LE Current TOD Midnight cross N/A * GT Current TOD TOTIME 00:00:59.999999 Not * LE Current TOD Midnight cross N/A Not * GT Current TOD Midnight crossed The midnight cross time is calculated as: Current time - TOTIME time offset + time in 1 day -4. The TOTIME= value for an hours offset is truncated to the start of the hour while the TOTIME= value for a minutes offset is truncated to the start of the minute depending on the time offset unit. In either case 00:00:59.999999 is added to the result. -TOTIME= values are set with 59.999999 seconds as the last part of the time stamp so that any data time stamped within the minute is sure to be selected. TOTIME= in ASMRMFV has always been inclusive of the entire end minute. -5. However, if the time offset is zero then the final time value is only adjusted to the end of the minute whether the time offset unit is in hours or minutes. -To summarize the adjustment with non-zero TOTIME= offsets:
TIME FINAL OFFSET UNIT TOTIME= ----------- --------------- Default (Hours) HH:00:59.999999 H (Hours) HH:00:59.999999 M (Minutes) HH:MM:59.999999 -To summarize the adjustment with a zero TOTIME= offset:
TIME FINAL OFFSET UNIT TOTIME= ----------- --------------- Default (Hours) HH:MM:59.999999 H (Hours) HH:MM:59.999999 M (Minutes) HH:MM:59.999999 -Examples for TOTIME= Relative Time usage follow. For these examples assume the current TOD is: DATE=2016.251 01SEP2016 THU TIME=09:26:56.776233 -Example 1: TODATE=* TOTIME=*-3 is a 3 hour current TOD Relative Time offset and results in:
FROM DATE=2000.001 01JAN2000 SAT TIME=00:00:00.000000 TO DATE=2016.251 01SEP2016 THU TIME=06:00:59.999999 -Example 2: TODATE=* TOTIME=*-10 is a 10 hour current TOD Relative Time offset and results in: FROM DATE=2000.001 01JAN2000 SAT TIME=00:00:00.000000 TO DATE=2016.251 01SEP2016 THU TIME=00:00:59.999999 since the Relative Time offset extends beyond midnight into the prior day and TODATE= is the current date, then the TOTIME= was forced to midnight + 00:00:59.999999 . -Example 3: TODATE=*-1 TOTIME=*-10 is a 10 hour current TOD Relative Time offset with a TODATE= of yesterday and results in: FROM DATE=2000.001 01JAN2000 SAT TIME=00:00:00.000000 TO DATE=2016.250 31AUG2016 WED TIME=23:00:59.999999 since TODATE= is NOT the current date, the TOTIME= offset is allowed to cross midnight by 1 hour in this example. To achieve the cross midnight time behavior TODATE= must NOT be the current date. -To use the midnight crossing feature effectively a user must anticipate a midnight crossover based on the size of the Relative Time TOTIME= offset being used and when ASMRMFV is going to be run. Usually TODATE=*-1 is coded rather than TODATE=* if the midnight time crossover is expected. -However, any TODATE= value that is not the current date may be used and the midnight crossing will still occur. -Example 4: TODATE=* TOTIME=*-30M is a 30 minute current TOD Relative Time offset and results in: FROM DATE=2000.001 01JAN2000 SAT TIME=00:00:00.000000 TO DATE=2016.251 01SEP2016 THU TIME=08:56:59.999999 -Example 5: TODATE=* TOTIME=30M is a parameter error because at least the '-' character must follow TOTIME= to indicate a Relative Time. ASMRMFV will abend. -Documentation Section 5 "Input Data Selection Parameters" is updated to explain use of Relative Times for FROMTIME= and TOTIME= parameters. -The Relative Time feature is not supported by earlier ASMRMFV versions prior to MXG Change 34.198. If specified a parameter error will be flagged. Change 34.197 More Support for BE93 Version 6.1.0 (INCOMPATIBLE) due to VMACBETA changed BETAFLAG that contains '81'x, but the MXG test Aug 19, 2016 for the extended header existence tested for '80'x, and there were new fields inserted in the subtype=1 record causing misalignment and invalid values in BETA1 dataset. Thanks to Sabrina Mandelatz, Provinzial Rheinland Versicher, GERMANY Change 34.196 -SMF 78 ST3 INPUT STATEMENT EXCEEDED when APAR OA44525 VMAC78 zHPF Extended Distance II is installed, MXG 33.07-34.05, Aug 18, 2016 because MXG Change 33.156 for that APAR incorrectly had INPUT R783TMWM/R783TRDM in the DCS segment for TYPE78CF, but that APAR had added those fields in the ASS segment. MXG properly INPUTs them and keeps them in TYPE78CU instead of TYPE78CF. The STOPOVER ABEND that results can be circumvented adding MACRO STOPOVER MISSOVER % statement at the top of your //SYSIN, and/or you can request just the VMAC78 member from support@mxg.com -Added May 2017: This change caused a massive increase in the number of observations in TYPE78CF; prior code read only output the first CU (8 obs/record) but there are 356 obs typically in each record. -Unrelated, APAR OA49415 added new fields now in TYPE78CU: R783AMGC='ALIAS*MGMT*GROUP*NUMBER*PHYSICAL CU' R783AMGS='ALIAS*MGMT*GROUP*NUMBER*THIS LCU' Thanks to Gadi Ben-Avi, MALAM, ISREAL. Change 34.195 TMON/CICS new variables TASZIPTM and TASELGTM created and VMACTMO2 kept in MONITASK dataset, and TASCPUTM is corrected to Aug 15, 2016 contain ONLY the CP CPU time (previously it had the sum of CP and zIIP time). And, only for TMON 3.4, TASCPOT/TASCPUT were not divided by 4096.
EXTY99SL new datasets: EXTY99ST DDDDDD DATASET DESCRIPTION EXTY99PT TY99SL TYPE99SL SOFTWARE LICENSING EXTY99PI TY99ST TYPE99ST SOFTWARE LICENSING TABLE EXTY99ZE TY99PT TYPE99PT CP PRIORITY TABLE EXTY99PS TY99PI TYPE99PI ZAAP PRIORITY TABLE VMAC99 TY99ZE TYPE99ZE ZIIP ENTITLEMENT VMXGINIT TY99PS TYPE99PS ZIIP PRIORITY TABLE Aug 13, 2016 The new TYPE99SL dataset has the new Hardware Absolute Group Capping metrics added by APAR OA47752. -Variable S99BUNUS in TYPE99BG can now be negative MSU when capped. Thanks to Scott Wiig, USBank, USA. Thanks to Tony P. Steward, CSC, ENGLAND. Change 34.193 HSM SMF VSR records with '62'x instead of the "S" in VSR VMACHSM test field printed "INVALID HSM RECORD" messages and the Aug 12, 2016 (six out of 100) records were skipped. Now, if DSRVSR Jan 3, 2017 is NOT DSR but starts with a V, the record will be read as a VSR record, while IBM HSM Support investigates. -Turns out this had nothing to do with HSM, but was an error that touched man SMF records, if you used LOGGER and had a MAXBUFSIZE that was NOT 65532. APAR OA51823. Thanks to Scott Wiig, USBank, USA.
VMACRMFV to aid in processing data from multiple timezones. It is Aug 11, 2016 INPUT from each SSH record and retained for all of the following records in that interval. (Only the first SSH record is output in ZRBSSH by logic in member EXZRBSSH). Thanks to MP Welch, Bank of America, USA.
ADOCRMFV III SPG (Storage Group and Volume Data) table and other ASMRMFV usability improvements. VMACRMFV -These filters are intended for building ad hoc MXG RMF Aug 11, 2016 III PDBs for studies to avoid the overhead of generating a full SPG table based PDB. They control which SPG table entries are output to the RMFBSAM file. -Please see the new documentation Section 28 "Collection of DASD Usage with RMF Monitor III" in the ADOCRMFV member or ASMRMFV source member for the requirements and setup of DASD usage measurement in the SPG table. There are multiple Storage Group name entries in the SPG each with many Volume Data entries when collection is active. -Four new filters are added to support SPG entry selection from this table to the RMFBSAM output file. These Yüklə 28,67 Mb. Dostları ilə paylaş:
|