* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
The error is in Unicode Service Conversation iconv() calls which is NOT USED IN MXG. but TELNET and many other programs are impacted. Change 33.234 Change 33.155 added R744SNAM to TYPE74HO dataset, which VMAC74 accidentally corrected an unreported error in the NODUP Oct 4, 2015 sort to create PDB.TYPE74HO: false duplicates were being deleted, so the prior PDB.TYPE74HO dataset was incorrect. The number of obs correctly increased with this change. And R744CNAM and R744SNAM are added to the end of the _BTY74HO BY List to formally correct the NODUP sort. Thanks to Paul Volpi, UHC, USA. Change 33.233 Support for APAR OA46136 that adds File Transfer Section VMAC6 with IP Address and Port Number to PSF-created SMF 6. Oct 1, 2015 No change was required; fields automatically INPUT/KEPT when the section exists. Change 33.232 Support for Thruput Manager VARNAME=$ORIGIO NOT FOUND VMACTPMX message creates new ORIGIO='ORIGINAL*INSYSID' variable Sep 30, 2015 in the TYPETPMX dataset. Thanks to Scott Barry, SBBWorks Inc., USA. Change 33.231 Support for JZOS Java Runtime Performance Stats SMF 121 EXTY121 creates three new datasets: EXTY121G dddddd dataset description EXTY121G TY121 TYPE121 JZOS JAVA RUNTIME STATISTICS FORMATS TY121G TYPE121G JZOS JAVA RUNTIME GARBAGE COLLECTION TYPE121 TY121T TYPE121T JZOS JAVA RUNTIME THREADS TYPS121 and new FORMAT $MG121TC for thread category. VMXG121
VMXGINIT Oct 8, 2015 Change 33.230 -Example ANAL1430 selects TYPE1415 (non-VSAM) and TYPE64 ANAL1430 (VSAM) records by DSNAME, then merges BY READTIME JOB to ANAL2642 select the the TYPE30_4 (Step end) for that JOB to get VMAC42 the RACFUSER field that opened that dataset. Sep 30, 2015 HOWEVER, this example in ANAL1430 can ONLY capture those datasets that were CLOSED, and ONLY if that JOB had a step terminate record in the SMF file. -Example ANAL2642 selects TYPE26J2 (Job Purge) by SUBMUSER and selects TYPE42DS (Interval Dataset Activity) by DSN to report each JOB and DSNAME for that SUBMUSER. -Type 42 subtype 6 TYPE42DS dataset has new variables S42READS=SUM(S42AMDRB,S42AMSRB,S42AMZRG,S42DSHRD); S42WRITES=SUM(S42AMDBW,S42AMSWB,S42AMZWB,S42DSHWR); the sum of direct and sequential BLOCKS, directory reads/ writes, and zHPF reads and writes. Thanks to Alyona Bertneski, JPMorgan, USA. Change 33.229 Support for NDM PT records with zIIP CPU times (INCOMPAT) VMACNDM inserted these three new variables in NDMPT dataset: Sep 28, 2015 PTECP0='CPU TIME*SPENT ON*CP' PTECP1='CPU TIME*SPENT ON*ZIIP' PTECP2='ZIIP*QUALIFIED*PART OF*PTECP0' The inserted data caused INPUT STATEMENT EXCEEDED ERROR. The prior PT record format's UNC and UNN variables were cleaned up. Thanks to David Guess, Blue Cross Blue Shield of South Carolina, USA.
VMAC74 record with R749DEVN='Hardware Accelerator' but without Sep 25, 2015 expected Hardware Accelerator and Hardware Compression segments that MXG INPUT because of that DEVN value. The record is valid as it contains zeros in the two triplet's NUMBER OF fields, SMF749FN,SMF7491N, so MXG logic now knows to test those fields prior to the input of the SMF749FO,SMF7491O segments, while the reason for their absence is being investigated. Thanks to David Marone, SGS-BP, ITALY. Change 33.227 Dataset TYPE22PB 'RECONFIGURED PCIE PFIDS' had zero obs VMAC22 due to misalignment in the MXG INPUT statement. See also Sep 23, 2015 Change 33.146. Thanks to Scott Barry, SBBWorks Inc., USA. Change 33.226 Documentation. ERROR: THE GIF DRIVER CAN NOT FIND ANY MXGSAS92 FONTS and PHYSICAL FILE MVS:SYS3.SAS.SASMONO.TTF.. DOES Sep 23, 2015 NOT EXIST occurred on z/OS when the old MXGSAS92 PROC was used for SAS 9.4, instead of using MXGSAS94 PROC. This DD statement was added and is required for SAS 9.4 // DD DSN=&SASHLQ..CONFIG(COMMON),DISP=SHR in the //CONFIG DD concatenation.
ANALCAPD PDB.ASUMCELP dataset with data for each LPAR, rather than Sep 20, 2015 using only the PDB.ASUMCEC summary dataset for the CEC, with new parameters to allow for selection by LPAR and/or to set different cap values for different LPARs: INCODE= a stub of code for selecting data CEC= one or more CEC serials separated by spaces LPAR=one or more LPAR/cap values separated by spaces The plot shows the "Overflow MSU", an estimate of how long it would take at the cap to get the same number of MSUs consumed when the rolling 4 hour avg was over the cap. So the total MSU consumed above the cap based on the rolling average pro-rated across the four hour average keeping the system at the cap until all of the excess MSUs are consumed.
VMACSYNC (which normally is a 3-byte EBCDIC like '181'/'F1F8F1'x) Sep 18, 2015 for a SYNCSORT SORTWK DD segment caused ILLEGAL ARGUMENT message when it was used to create SYNCDV and SYNCUN with SYNCDV=INPUT(SMFWKUDA,HEX6.) syntax, as the HEX6 informat doesn't support the null value. This DD segment also has " 0 " for the value in VOL variable. Null now protected. Thanks to Joseph J. Faska, DTCC, USA. Change 33.223 Short SMF 103 Subtype 13 record caused INPUT STATEMENT VMAC103 EXCEEDED Error. The segment is documented to contain 56 Sep 18, 2015 bytes plus a name field, but the record contains only 48 bytes. Circumvention: Use the Name-Length Field and its location to determine if this is 48 or 56 length. Input normal for 56. For short 48 record, the two 8-byte fields are changed to 4 so the NAME field aligns, causing Bytes and Requests are zero in the short records, but the short record will be output with valid server name. Thanks to Shabida Khan, Royal Bank of Canada, CANADA. Change 33.222 -Major enhancement for character data filtering for RMF ADOCRMFV Monitor III DVT (Device Table) entries and other ASMRMFV improvements. Sep 18, 2015 -These filters are intended for building ad hoc MXG RMF Sep 21, 2015 III PDBs for studies avoiding the overhead of generating a full DVT table based PDB. They control which DVT table entries are output to the RMFBSAM file. -Four filters are added to support DVT entry selection from this table to the RMFBSAM output file. These filters are effective only if the DVT table is selected. They are applied in the order shown when multiple different keywords are used. New Keyword Aliases ------------ -------------------------------------- DVTDEVNUM= DVTDEVNO= DVTDEVNR= DVTDEV= DVTN= DVTVOLSER= DVTVOLI= DVTVOL= DVTSER= DVTV= DVTAND None DVTOR None -TUTORIAL: Ranges of the form keyword=first:last may be used with any of the above keywords except DVTAND and DVTOR. The colon character ':' is required for a range specification. All entries GE the first value and LE the last value are selected for output to the RMFBSAM file. The first value may not exceed the last value or an error is flagged. Ranges may not be wild carded. If wild carded the range value becomes a pattern instead. Single values may be specified for a range simply as keyword=first and in this case the colon ':' is omitted. Patterns may also be used with any of the above keywords except DVTAND and DVTOR and include one or more wild card characters to match the respective DVT data field. Wild Card Matches ---- ------------------------------------------------ * 0 or more characters % 1 Non-blank character + 1 Numeric character (0-9) _ 1 Alphabetic character or _ (a-z, A-Z, _) . 1 National character (@, #, $) ! 1 Special character (not a-z, A-Z, 0-9, @, #, $) ? A blank string if used by itself ? 1 Blank character (X'40') if used with any other characters See Section 25 in the ADOCRMFV member for more details on usage of ranges and patterns. -DVTDEVNUM= (and any of its aliases) selects DVT entries by Device Number. Both ranges and patterns with wild card characters may be specified. Up to 64 ranges and 64 patterns are supported. The default is DVTDEVNUM=ALL. Any valid 4 hex character device number with or without pattern characters in the range of 0000-FFFF may be specified. For ranges the Device Number is treated as a binary number in arithmetic comparisons. For patterns the Device Number is converted to hex characters (0-F) prior to pattern matching. NOTE: Due to the nature of hexadecimal characters not all characters and/or patterns may be used with DVTDEVNUM=. See documentation for details. -Examples for DVTDEVNUM= DVTDEVNUM=0A00 selects the device with address 0A00 only. DVTDEVNUM=0A00:0FFF selects all devices with addresses GE 0A00 and LE 0FFF. DVTDEVNUM=A00:FFF selects the same devices as above with the leading zeros omitted for coding convenience. All leading zeros may be omitted if desired when ranges are used. Leading zeros may NOT be omitted when patterns are used unless they are included in the pattern.
DVTDEVNUM=0*F and DVTDEVNUM=*F produce quite different results.
DVTDEVNUM=B* selects all devices with addresses from B000 through and including BFFF. DVTDEVNUM=10* selects all devices with addresses from 1000 through and including 10FF. DEVDEVNUM=C*FE selects all devices with addresses C0FE, C1FE, C2FE, C3FE, C4FE, C5FE, C6FE, C7FE, C8FE, C9FE, CAFE, CBFE, CCFE, CDFE, CEFE, and CFFE. DEVDEVNUM=C+FE selects all devices with addresses C0FE, C1FE, C2FE, C3FE, C4FE, C5FE, C6FE, C7FE, C8FE, and C9FE as '+' is a digit (0-9) pattern character. DVTDEVNUM=C%FE selects all devices with addresses C0FE, C1FE, C2FE, C3FE, C4FE, C5FE, C6FE, C7FE, C8FE, C9FE, CAFE, CBFE, CCFE, CDFE, CEFE, and CFFE as '%' is a placeholder pattern character. DVTDEVNUM=C_FE selects all devices at addresses CAFE, CBFE, CCFE, CDFE, CEFE, and CFFE as '_' is an alphabetic pattern character. -DVTVOLSER= (and any of its aliases) selects DVT entries by Volume Serial Number. Both ranges and patterns with wild card characters may be specified. Up to 64 ranges and 64 patterns are supported. The default is DVTVOLSER=ALL. Any valid 1-6 character Volume Serial with or without pattern characters may be specified. Per JCL syntax a Volume Serial Number is 1 through 6 alphanumeric, national ($,#,@), or special characters. NOTE: Since just about any keyboard character is valid in a Volume Serial please take extra care when coding to avoid unintended results in the MXG PDB. -Examples for DVTVOLSER= DVTVOLSER=C99999 selects the volume serial C99999 only. DVTVOLSER=C00000:C99999 selects all volume serials GE 'C00000' and LE 'C99999'. DVTVOLSER=10* selects all volume serials starting with '10' followed by up to 4 more characters. DVTVOLSER=H+++++ selects all volume serials starting with 'H' followed by 5 digits. DVTVOLSER=K*A selects all volume serials starting with 'K' that have a final character 'A' with up to 4 intervening characters. -DVTAND (default) indicates that selection results from DVTDEVNUM= and DVTVOLSER= DVT filter keywords are logically ANDed. DVTAND is effectively ignored if DVT records are NOT selected Results for selected Devices for the same DVTxxxxxx= keyword are ALWAYS logically ORed. NOTE: The DVT filters DEVTYPE=ALL/DASD/TAPE and ZEROIO/NOZEROIO are applied independent of the use of DVTAND. -DVTOR indicates that selection results from DVTDEVNUM= and DVTVOLSER= DVT filter keywords are logically ORed. DVTOR is effectively ignored if DVT records are NOT selected Results for selected Devices for the same DVTxxxxxx= keyword are ALWAYS logically ORed. NOTE: The DVT filters DEVTYPE=ALL/DASD/TAPE and ZEROIO/NOZEROIO are applied independent of the use of DVTOR.
-Examples with DVTAND in effect: DVTDEVNUM=CA00:CAFF DVTVOLSER=SMF* only selects device entries in the DVT table that have a Device Number GE CA00 and LE CAFF AND that have a Volume Serial Number that starts with 'SMF'. DVTDEVNUM=CA00:CAFF DVTVOLSER=SMF* DVTVOLSER=PAG* only selects device entries in the DVT table that have a Device Number GE CA00 and LE CAFF AND that have a Volume Serial Number that starts with either 'SMF' or 'PAG'. -Examples with DVTOR in effect: DVTDEVNUM=CA00:CAFF DVTVOLSER=SMF* selects device entries in the DVT table that have a Device Number GE CA00 and LE CAFF OR that have a Volume Serial Number that starts with 'SMF'. DVTDEVNUM=CA00:CAFF DVTVOLSER=SMF* DVTVOLSER=PAG* selects device entries in the DVT table that have a Device Number GE CA00 and LE CAFF OR that have a Volume Serial Number that starts with 'SMF' or 'PAG'. The logical OR results in less restrictive filtering because any of the 3 conditions results in data selection of a DVT entry. NOTE: The DVT filters DEVTYPE=ALL/DASD/TAPE and ZEROIO/NOZEROIO are applied independent of the use of DVTOR.
-The order of DVT filter application is: 1) DEVTYPE= 2) DVTDEVNUM= 3) DVTVOLSER= 4) ZEROIO/NOZEROIO -Section 5 "Input Data Selection Parameters" in documentation is updated with discussion of all the new DVT selection keywords and aliases. -Section 26 "Summary" in documentation is updated for the new DVT keywords. -Message RMFV034I did not display correctly on a Device Number match with DVTDEVNUM= and SHOWMATCH options in effect. -Version entry for z/OS 2.2 in RMF release table was not Correct. Change 33.221 RMF III data with CPUHOLEN GT 480 and CPUVERG3 EQ 5 ABEND VMACRMFV INPUT STATEMENT EXCEEDED RECORD LENGTH error when IBM Sep 17, 2015 changed CPUHOLEN to 740 but did not update CPUVERG3.
SAGANAL caused the MSU values to be off by a factor of 100 (an Sep 17, 2015 error that was immediately obvious!). SAGANAL builds format $SYS2CAP that maps SMF70CPA to TIME+SYSTEM, and then retrieves a value with this INPUT function that uses the 10.2 INFORMAT to "read" the $SYS2CAP value: SMF70CPA=INPUT(PUT(TIMESYS,$SYS2CAP.),10.2); which worked, but only accidentally, because all previous $SYS2CAP values contained a decimal. But if the value in $SYS2CAP was an integer, the .2 in the 10.2 INFORMAT told SAS to divide by 100. Removal of the .2 that never should have been there corrects the error. Change 33.219 MXG 33.09 Only. VARIABLE MAXCCPUC IS UNINITIALIZED msg, VMACBVIR typo, caused MAXDCUPC to be a missing value in BVIR10. Sep 17, 2015
ADOC110 did not include these recently-added wait variables: VMAC110 DSCHMDTM FCVSWTTM VCXCWTTM ISALWTTM TCALWTTM TDELWTTM Sep 16, 2015 TDILWTTM ====== Changes thru 33.217 were in MXG 33.09 dated Sep 15, 2015========= Change 33.217 z13 in SMT Mode ONLY: LPARCPUS=0 in PDB.TYPE70PR. VMAC7072 This is the last reported issue with MXG code for z13 in Sep 13, 2015 SMT mode, and both SMT=1 and SMT=2 data have been tested. So this change in MXG 33.09 is REQUIRED for z13 SMT mode. Thanks to Scott Barry, SBBWorks Inc., USA.
VMAC7072 and 72 for MOBILE PRICING that eliminates the need to Sep 11, 2015 process the CICS and IMS transaction records, by using new WLM Service Definition Qualifier types of Connection Type (CT) and/or Client Transaction Name (CTN) to set the new WLM Classification "Reporting Attribute" that can be set to NONE/MOBILE which WLM uses to identify mobile work in these new variables. -Dataset TYPE70 new variables: SMF70LACM='MOBILE*LONGTERM*AVERAGE*MSU/HR' SMF70LACA='CAT A*LONGTERM*AVERAGE*MSU/HR' SMF70LACB='CAT B*LONGTERM*AVERAGE*MSU/HR' -Dataset TYPE72GO new variables: R723TSUCP ='TOTAL*GP*SERVICE*MSU/HR' R723TSUSP ='TOTAL*ZIIP*SERVICE*MSU/HR' R723TSUOCP='TOTAL*ELIGIBLE*SERVICE*MSU/HR' R723MSURCP='MOBILE*GP*SERVICE*MSU/HR' R723MSURSP='TOTAL*ZIIP*SERVICE*MSU/HR' R723MSUOCP='TOTAL*ELIGIBLE*SERVICE*MSU/HR' R723ASUCP ='CAT A*GP*SERVICE*MSU/HR' R723ASUSP ='CAT A*ZIIP*SERVICE*MSU/HR' R723ASUOCP='CAT A*ELIGIBLE*SERVICE*MSU/HR' R723BSUCP ='CAT B*GP*SERVICE*MSU/HR' R723BSUSP ='CAT B*ZIIP*SERVICE*MSU/HR' R723BSUOCP='CAT B*ELIGIBLE*SERVICE*MSU/HR' These metrics may be available for z/OS 2.2 and z/OS 2.1 later this year. Note that R723TSUCP=SUM(CPUUNITS,SRBUNITS); Change 33.215 Documentation change only. Added an example of using VMXGSUM VGETDDS to drive the input to VMXGSUM. Sep 9, 2015
UTILBLDP the USERADD= option was used, the second execution failed Sep 10, 2015 because the _IDxxxx "SMF Record Macros" were not cleared. Thanks to Michael Reines, Decadis, GERMANY. Thanks to Ron Hawkins, HDS, USA.
VMAC120 Type 120 Subtype 100 (MXG Dataset TY120100) INCOMPATIBLE. Sep 10, 2015 The record was completely restructured internally, and Oct 8, 2015 these ruleset statistics now exist in SM120HDV=3 records: SM120RULEXBAD ='RULESET*FAILED*EXECUTION*COUNT' SM120RULEXCALLS='RULESET*NUMBER*OF*CALLS' SM120RULEXCMAX ='RULESET*MAX*CPU*JAVA TIME' SM120RULEXCMIN ='RULESET*MIN*CPU*JAVA TIME' SM120RULEXCPU ='RULESET*TOTAL*CPU*JAVA TIME' SM120RULEXFSUM ='RULESET*SUM OF*FIRED*RULES' SM120RULEXNUM ='RULESET*SUCCESSFUL*EXECUTION*COUNT' SM120RULEXPATH ='RULESET*EXECUTION*PATH' SM120RULEXTIME ='RULESET*TOTAL*ELAPSED*JAVA TIME' SM120RULEXTMAX ='RULESET*MAX*ELAPSED*JAVA TIME' SM120RULEXTMIN ='RULESET*MIN*ELAPSED*JAVA TIME' -SM120HDV=1 records (in Versions 8.5.1.0 and 8.6.0.0) and SM120HDV=2 records (in Versions 8.5.1.2) contain only these counters: SM120RULEXNUM SM120RULEXBAD SM120RULEXSUM -Records with no Extension segment are now output; these appear to be interval records when there was no activity. New variable SM120EXNNR identifies if the record has an extension, and if so, which one. -The prior TY120100 dataset was incorrectly/wrongly built with the number of observations in WORK.TY120100 higher than the number of input records, and the number of obs in PDB.TY120100 too few (and wrong). Thanks to Scott Barry, SBBWorks Inc., USA. Thanks to Paul Volpi, UHC, USA. Change 33.212 Support for MEGACRYPTION Version 6 SMF records, VMACMGCR (MGCRLEV='2') which incompatibly increased the length of Sep 8, 2015 the MGCRBYTE and MGCRKS fields from 4 to 8 and 40 to 60. Thanks to Randy Schlueter, First Data Corporation, USA Change 33.211 New variables are added in DB2 Trace Dataset T102S199. VMAC102 QW0199SC='LAST TIME*DATABASE*STATISTICS*UPDATED' Sep 8, 2015 QW0199ID='MORE*RECORDS*OR*LAST?' QW0199SD='SHADOW*COPY?' Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
VMACTMO2 -MONITASK for Version 3 was wrong in MXG 33.08, with Sep 11, 2015 misalignment starting at variable CICOVHTM. -MONITASK Version 4 requires ASG PTF TH03803 to correct invalid values in variables TASTCPUC and TASTCPOC. -The MONISYST dataset was misaligned and has been updated and validated with both 3.3 and 4.0 records. Thanks to Francois Vancoppenolle, PV Group, BELGIUM. Change 33.209 Cosmetic changes from ITRM Validation. VMAC102 -VMXG70PR: Temporary variable N60PLUSLPAR no longer kept VMAC110 in PDB.ASUM70PR and PDB.ASUMCEC datasets. VMAC119 -VMAC110: Variables DS7START,DS7LSTRT now labeled. VMAC50 -VMAC102: The nineteen QWn196Ha variables added by 31.236 VMAC7072 are now labeled/formatted/Length consistently. VMAC74 -VMACNDM: Offset variable NDMGPE1D is no longer kept in VMAC75 NDMRT dataset. VMAC76 Variables NDMZLIBR/LIBS PTRESTRECORD labeled. VMAC77 -VMACSTC: STC14TOD and STC27TPX variables are labeled. VMAC99 -VMAC119: Variables SMF119SM_ and SMF119FT_ are labeled. VMACNDM -VMAC50: Variable TY40EXTL labeled. VMACSTC -VMAC7072: Temp variables R725QSR1/QSR2/QST1/QST2 are not VMACXCOM kept since they were already used to create the VMXG70PR SSQ variables R725QSRQ R725QSTQ. Sep 6, 2015 -VMAC74-7: Variables SMF74/75/76/77/GIE are labeled. -VMAC99: Variables S99CMTFLGS1/2 label typo corrected. -VMACXCOM: Many XCOxxxxx variables are labeled. Thanks to Chris Weston, SAS Institute, USA.
VGETDDS (to read all DDNAMEs starting with PDB), and those DDs Sep 6, 2015 are on tape, VGETDDS mounted all of the tapes twice, once to detect is is a SAS dataset and then once to actually read the data. Now, once VGETDDS finds that a PDBn DD points to a tape device, it will presume all the others are also tape, and thus eliminate the double mounts. But, if a DDNAME that matches the test is NOT a SAS dataset the job ABENDs with ERROR:LIBRARY PDBn IS NOT IN A VALID FORMAT FOR ACCESS METHOD V9SEQ or if UNIT=AFF is used but DEFER=YES was NOT, then a SYSTEM 413 ABEND occurs trying to open all tape devices at the same time. -The typically unneeded MXGNOTE messages are now skipped with the MXGEXIMSG option. Change 33.207 z/OS 2.2: REQUIRES ML-55 of MXGTMNT, for ABEND S0E0-28. ASMTAPEE In z/OS 2.2, IBM's CSRPOOL service, called by MCSOPMSG in Sep 8, 2015 ASMTAPEE, puts diagnostic data into GR0, AR0, and AR15, none of which are expected to be preserved, but R15 was used by ASMTAPEE, because it was unused and available. Now ASMTAPEE clears AR15 to eliminate the ABEND exposure. Change 33.206 z/OS 2.2 Job Correlation Variables SMF30COR is now INPUT BUILD005 kept in TYPE30xx datasets, and also output in PDB.JOBS, VMAC30 PDB.STEPS, and PDB.SMFINTRV. Variable SMF26JCR was INPUT Sep 4, 2015 and kept in TYPE26J2 previously, but now it is also kept Yüklə 28,67 Mb. Dostları ilə paylaş:
|