* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
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.
you put in a new product/subsystem/Release/APAR that incompatibly changed its records then you must install the current MXG Version or at least be using the minimum level of MXG that is currently documented in the preceding list in section IV.
that that change only alters a displayed value or may be a spelling error in a label, but it is "cosmetic" in that it ONLY affected the display, and the output data sets created are NOT impacted by this change.
See also member INDEX, but it may be overwhelming. VII. 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. Alphabetical list of important changes in MXG 36.36 after MXG 35.36:
Member Change Description ANAL89 36.165 Analysis of SMF 89 data, including MSU from CPU time. ANAL9914 36.171 Support for z/14 Clusters in IBM Processor Topology. ANAL9914 36.232 SMF99 ST 14 Processor Topology Report Enhanced. ANALCAPD 36.042 ERROR: FOUND "IF" when the CEC= option was used. ANALID 36.081 Support for four-digit SMF Record type reporting. ANALRMFR 36.203 CPU report with INTERVAL=HOUR was incorrect. ASCIIDSN 36.020 ASCII version of JCLDAYDS with SAS FTP for TMC/DCOL. ASMRMFV 36.110 SOC7 ABEND reading non-Extended Format VSAM dataset. ASUM113 36.133 Variable LPARBUSY was not calculated for z14. ASUM70PR 36.026 MXGERROR: MISSING TYPE 70 RECORDS impact ASUMCEC/LP. ASUM70PR 36.041 MXGERROR:MISSING TYPE70 now MXGWARN:MISSING TYPE70. ASUMCICR 36.226 Major revision to CICS RESPONSE TIME SLA reports. ASUMCICR 36.226 Major revision to CICS RESPONSE TIME SLA reports. ASUMUOW 36.107 Using ROLLUPS is useless with ASUMUOW, suppress DB2. BLDSMPDB 36.242 Protection for AUTOALOC=YES and FIRSTRUN=YES CONFIG 36.067 MXG default CAPSOUT option for z/OS now NOCAPSOUT. CONFIG 36.078 OPTION SORTBLKREC corrects DFSORT OC4 in SAS 9.4 M3. DOCUMENT 36.013 APAR OA27291 OC4 USEZOSV1R9RULE(NO) z/OS 1.10+ DOCVLONG 36.247 Utility to create DOCVER with all info on one line. GRAFMSU 36.204 Plots/Tabulate of MSU 4HR usage and capacity. GRAFWLM 36.153 New HIGHTOLOW parm to reverse IMPORTANCE order. JCLCPORT 36.111 Sample JCL to move WPS datasets to SAS. MOBWORK 36.045 Enhanced Mobile Work 4 Hour MSU reporting datasets. MXGNOTE 36.141 zHPF Channel Utilization PDBAUDIT 36.011 %PDBAUDIT(LIBNAMES="Not All" fails with syntax error. READDB2 36.092 ACCTSORT=NO was not working, data ended up in WORK. READDB2 36.121 READDB2(IFCIDS=ALL) did not create DB2STATS dataset. READDB2 36.140 New SORT102=NO option can suppress T102Snnn sorts. READDB2 36.172 IFCIDS=0-999 failed, only 367 are defined, now warns. RMFINTRV 36.136 MXGABNDRMFI option will ABEND if OTHER Work found. RMFINTRV 36.166 CRITICAL ERROR: PDB.TYPE70 MAY BE WRONG WITH 33 ENGS SASNOTE 36.129 SAS Not 61906 SAS 9.4 TS1M3 High CPU fixed in M4/M5. TECHNOTE 36.209 APARs of interest for z/OS. TYPE0 36.009 INVALID TYPE 0 LENGTH=70 is valid, wrongly deleted. TYPE101 36.101 Support for NDM-CDI OP record. TYPE102 36.102 Support for DB2 V11 APARS PI71903/PI84045/PI82755. TYPE102 36.138 Dataset T102S018 was misaligned. TYPE102 36.212 Protection for IFCID 376 invalid offsets STOPOVER. TYPE102 36.251 Support to populate T102S126 for DB2 102 IFCID 126. TYPE106 36.152 New SMF 106 variables decoded and formatted. TYPE110 36.008 CICS/TS 5.3 CPU variables in Statistics CICM dataset. TYPE110 36.077 CICDS Dispatcher Statistics DSGTWT corrected. TYPE110 36.220 Variable WTOTIOTM could exceed ELAPSTM TYPE110 36.235 Support for IBM CICS/TS 5.5 SMF 110 CICSTRAN INCOMPAT TYPE110 36.244 CICS Variable D2GDB2ID added to CICDB2GL BY list. TYPE115 36.005 QWHSDURN different in subtype 231, new vars, cleanup. TYPE119 36.008 Variable TTAPLDAT in dataset TYP11902 misaligned. TYPE119 36.018 STOPOVER ABEND: SMF 119 Subtype 81, at IBM now. TYPE119 36.038 "INVALID SMF 119 TYPE 81" corrected, not invalid. TYPE119 36.079 Support for SMF 119 subtypes 24, 38, 39, 40, and 45. TYPE119 36.127 Support for ZERT SMF type 119 Subtype 12 TYPE119 36.230 ZERT SMF 119 Subtypes 11 and 12 minor corrections. TYPE119 36.250 New variables added to TYP11952 subtype 52 dataset. TYPE120 36.022 Support for Liberty 8.9.1.0 SMF 120 ST 100 (COMPAT). TYPE120 36.134 WebSphere SMF 120 subtypes 5/6 only first was output. TYPE122A 36.066 Support for IBM Devel z Systems IDZ SMF 122 record. TYPE122A 36.207 Support for zExplorer SMF 122 Subtype 2. TYPE21 36.218 Support for APARs OA52915 and OA52940, 4 byte counter TYPE30 36.012 The created GMTOFF30 could be .01 seconds plus/minus. TYPE30 36.150 Support for APAR OA54589, OSPROTECT, TRUSTED. TYPE30 36.175 Support for SMF 30 User Key CSA RAXFLAGS OA53355. TYPE42 36.023 Another invalid LENSR=232, STOPOVER ABEND OA54668. TYPE42 36.106 TYPE42DS Encryption variables were not kept. TYPE42 36.124 SMF 42 ABEND, more invalid values protected. TYPE42 36.151 New variables from Jul 30, 2018 SMF Manual. TYPE62 36.151 New variables from Jul 30, 2018 SMF Manual. TYPE70 36.166 CRITICAL ERROR: PDB.TYPE70 MAY BE WRONG WITH 33 ENGS TYPE7072 36.035 Incorrect LPAR/ZIP SHAR/SHAC if last engine was IFL. TYPE7072 36.073 Support for z14 ZR1, new SMF70MAXPU variable COMPAT. TYPE7072 36.208 Support for APAR OA56011 for TYPE70 OSPROTECT. TYPE70PR 36.039 TYPE70PR variable LPARZIPS, online zips, added. TYPE70TR 36.003 New 70 Tenant Resource Group TRG updated/validated TYPE72GO 36.215 Variable MSUSOFT, Software MSU frequently missing. TYPE72GO 36.253 MOBILE Service Units CPU Time not in CPUTM variable. TYPE72TR 36.003 New 72 Tenant Resource Group TRG updated/validated TYPE73 35.010 TYPE73 dataset, variable CHFXRATE slightly wrong. TYPE74 36.211 TYPE749 variables added and corrected. TYPE80A 36.108 Support for RACF TOKENs REQTCRE and ADMINCII' TYPE82 36.036 Support for new SMF 82 subtype 82 JOB-Level Crypto. TYPE89 36.003 New 89 Tenant Resource Group TRG updated/validated TYPE99 36.072 New EWLM & SERV variables added to TYPE99_6 dataset. TYPEACF2 36.075 ACF2 INVALID SMF RECORD, ACSMFREL=0, should be 6.2. TYPEACF2 36.100 ACF2 6.2 Change 36.076 didn't correct STOPOVER. TYPEBE97 36.217 Support for new BE97 subtype 6 and subtype 22 update TYPEBETA 36.015 ERROR when TYPEBETA and TYPE70 used together. TYPEBETA 36.074 Variables BETALOG reversed, subtype 51 doesn't match. TYPEBETA 36.199 Beta 93 Subtype 51 and subtype 22 updates. TYPEBETA 36.246 BETA 93 Version 6.2.0 updates subtypes 0/22/25/50/59 TYPEBVIR 36.120 Support for BVIR V412 History HSM Compression data. TYPECIMS 36.162 Support for multiple IMS SYSTEMS, using JFCB DSNAME. TYPECIMS 36.163 IMS56FA obs for CPI-C had incorrect INPQUETM. TYPECIMS 36.167 Support for BMC Energizer for IMS Connect for IMF. TYPECMFV 36.173 Support for Mainview MVS History Records new datasets TYPEDB2 36.004 DB2 V11 IFCID 376 INPUT STATEMENT EXCEEDED. V11 only. TYPEDB2 36.037 Var QWHSACE missing from DB2STSBP sort, ABEND TYPEDB2 36.082 DB2 BPHITRAT corrected. TYPEDB2 36.113 Incorrect test for QPAC_PIPE_WAIT/COUNT in DB2ACCTP. TYPEDB2 36.114 DB2ACCTR dataset has been misaligned, NRQLAC GT 1. TYPEDCOL 36.086 z/OS 2.3 DCOLLECT Encryption Variables added DCOLDSET TYPEIAM 36.071 INPUT STATEMENT EXCEEDED IAM 9.2 Length Changed. TYPEIMS 36.040 Support for unpopulated IMS 56FA with APAR UI50912. TYPEIMS 36.044 Variable IMSVERS, the value in your _IMSVERS is kept. TYPEIMS 36.238 MXG 36.11 protection for IMS 14.1 IMS56FA offset. TYPEMGCR 36.240 Support for MegaCryption MEGACR34, subtype 3 and 4. TYPEMVCI 36.234 Support for BMC's MainView for CICS(v69) COMPATIBLE. TYPENDM 36.046 Support for NDM-CDI Version 5.2, corrects NDMCPU plus TYPENMON 36.109 Significant CPU reduction processing NMON data. TYPEPOEX 36.002 PowerExchange updated, trashed CPU values, open prob. TYPEPOEX 36.135 Support for PowerExchange Version 10. TYPEPOEX 36.231 Protection for truncated POEX File Segment records. TYPERHEL 36.043 Initial support for NMON Red Hat Linux RHEL monitor. TYPERHEL 36.109 Significant CPU reduction processing RHEL data. TYPERHEL 36.137 Invalid data for variable MICROCODE. TYPERMFV 36.201 MXG 36.09, z/OS 2.2 only, ASIxxx text misaligned. TYPERMFV 36.201 WPS failed ERROR: format '$ CPUPHYAD' invalid TYPERMFV 36.241 CPC_CECNAME added, ASITRT/TET corrected, MSU ACT. TYPERSDA 36.143 Support for RSD Folders Version 6.0 AUDIT (INCOMPAT). TYPESMF 36.131 MXGREADSMF=LOGGER didn't invoke CICSIFUE exit. TYPESRDF 36.112 Support for SRDF Symmetric Remote Data Facility VV.RR TYPESTC 36.084 Dataset STCVSM11 Change 34.237 variables corrected. TYPESTC 36.222 Numerous STC formats were updated with new values. TYPESYSX 36.105 TYPESYSL renamed to TYPESYSX to avoid conflict. TYPETAND 36.118 Support for Tandem TMF Transaction DATA, TANDTMF. TYPETCP 36.001 TYPETCP (archaic 118) APISTART date was on GMT. TYPETMO2 36.236 Support for ASG-TMON CICS for z/OS V4.2 - NO CHANGES. TYPETPMX 36.024 Support for ThruPutManager Release 18.02 TMT7113. TYPEVMXA 36.025 Support for zVM64 Level 40061702 (INCOMPATIBLE). TYPEVMXA 36.155 Support for z/VM LINUX LNXAPPL Process & Summary data TYPEVMXA 36.198 z/VM VXBYUSR High CPU, records not on same second. TYPEVMXA 36.221 MONWRITE DEFECT caused large values, LCUPPNUM issue. TYPEVMXA 36.237 z/VM 6.3 PROBABLE DATA LOSS ABEND MTRSYS 1.04 TYPEWSF 36.132 Support for EOS Version 160 (INCOMPATIBLE). TYPEXCOM 36.047 Support for XCOM Version 36.02 (COMPATIBLE). TYPEZCOS 36.174 Support for AutoSoftCapping ZCOS Version 4.2 INCOMPAT UTILBLDP 36.139 AUDITAFTER, SUPPRESS=ID, SORTOUT=NO revisions. UTILBLDP 36.176 MXG 36.08, Extraneous % with EXPDBOUT= 180 ABEND. UTILBPV 36.007 Program to examine the BPV cylinder value for EAV. UTILEXCL 36.220 Variable WTOTIOTM could exceed ELAPSTM. UTILEXCL 36.235 Support for IBM CICS/TS 5.5 SMF 110 CICSTRAN INCOMPAT VMXGALOC 36.243 Protection for READONLY=YES with FIRSTRUN=NO VMXGSUM 36.245 VMXGSUM with user's INCODE GT 32756 chars, ABEND. VMXGSUM 36.249 OBS=0 protection adds non-zero SYSCC Error test. See member CHANGESS for all changes ever made to MXG Software, or the CHANGES frames at http://www.mxg.com. Inverse chronological list of all Changes: NEXTCHANGE ====== CHANGES THRU 36.255 WERE IN MXG 36.36 DATED Jan 4, 2019========= Change 36.255 T102S083 was incorrectly input to the report twice. One ANALDB2R report line with the correct AUTH CHG type was printed, PMAUD02 a report line with type that is blank. Jan 4,2019 Thanks to Henry Boone, GEICO, USA.
VMACDB2 DB2STATS dataset: Jan 4, 2019 QISTTRAVMIN='FTB*THRESHOLD' QISTFTBCANT='INDEXES*THAT*MEET*FTP CRITERIA' QISTFTBCAN='INDEXES*THAT*MEET*TRAVERSE OK' QISTFTBSIZE='TOTAL*MEMORY*ALLOCATION' QISTINBNUMP='INDEXES*FTB*EXIST*PREVIOUS' QISTINBNUMC='INDEXES*FTP*EXIST*CURRENT' Thanks to Jan Tielemans, KBC, BELGIUM.
VMAC7072 in TYPE72GO and TYPE72TR datasets, in variables R723MSUCP Jan 3, 2019 and R723MSUSP, but their CPU times were not created, and the GP CPU time is NOT included in CPUTM. New variables CPUMOBILECP and CPUMOBILESP are created, but the CP CPU time is still not added into CPUTM at this time. Instead CPUTM_ALL=SUM(CPUTM,CPUMOBILCP) is created so the values can be examined and validated; if you have MOBILE work, please contact support@mxg.com to discuss how this new new data can be best presented. Thanks to Kare Martin Torsvik, EVRY,
Many VMACNDM: NDMOPSEQ Jan 3, 2019 VMAC119: DM_LSVLANID,UC_LTEDATE GMTOFFTM VMAC74 and VMAC79: DEVNR5HEX VMAC78: IOPDSTX VMAC89: SMF89NUM was changed to SMF89_NUM VMACWSF: ACCSTAT, AUDOBJRN VMACBETA: BETASSI Thanks to Chris Weston, SAS ITRM, USA.
VMAC102 "serviceability" with no descriptions, and a 4095 byte Jan 3, 2019 field that is mixed binary and character, but no info. The R1O is 41 and R1L is 4096 so 4137 bytes are described and read, but records have 4448 bytes, 311 undocumented. Thanks to Jan Tielemans, KBC, BELGIUM. Change 36.250 New variables added to TYP11952 Subtype 52 dataset: VMAC119 SMF119ML_IP_CONCOUNT=CONNECTION*COUNT' Jan 3, 2019 SMF119ML_IP_CONFAILCOUNT=CONNECTION*FAILURE*COUNT' SMF119ML_IP_RCVDBYTES='RECEIVED*BYTES' SMF119ML_IP_SENTBYTES='SENT*BYTES' SMF119ML_IP_ESMTP='ESMTP*SUPPORTED?' Thanks to Randy Shumate, RELX Group, USA
VMXGSUM to confirms a prior SAS error had set OBS=0, which can Jan 1, 2019 cause VMXGSUM to fail, depending on the arguments used, so VMXGSUM can be gracefully stopped with MXGERRORs that no dataset was output and to look on the log for ERROR and correct it. Change 36.248 CICS variables TASELGTM CPUTONTM CPUTONCN are added to ASUMCICS the PDB.ASUMUOW dataset from CICSTRAN, and CICS variables ASUMCICX TASELGTM TASZIPTM CPUTONTM CPUTONCN OFFLCPTM OFFLCPCN are VMXGUOW added to PDB.CICS created from PDB.ASUMUOW by ASUMCICX, Dec 31, 2018 or created from CICSTRAN.CICSTRAN by ASUMCICS, but read the comments in ASUMCICS that suggest ASUMCICX is better. Thanks to Scott Barry, SBBWorks Inc., USA.
DOCVLONG with all info on a single line for each MXG variable. MXG Dec 27, 2018 variable names can be the 32 character max SAS allows, so DOCVER descriptions are split if the name is 9 or more. This program creates 94-byte records for each variable. Thanks to MP Welch, Bank of America, USA. ====== CHANGES THRU 36.246 ARE IN MXG 36.12 DATED Dec 25, 2018========== Change 36.246 BETA 93 Version 6.2.0 updates for subtype 0/22/25/50/59. VMACBETA Versions 4.x.x and earlier may not be supported, contact Dec 21, 2018 MXG Support if you are still at that BETA93 level. Contact Support if you have other 6.2.0 subtypes so they can be validated and supported. Thanks to Robert Gilbert, BNP Paribas Fortis, FRANCE. Change 36.245 MXG 36.05-36.11, VMXGSUM fails if user option INCODE text VMXGSUM exceeds 32756. Change 36.109 added detection of "BY" in Dec 19, 2018 your VMXGSUM INCODE= argument, but 32K is the limit that is permitted by the %INDEX function. Now, INCODE string is compressed of blanks to mitigate that length issue and the test for BY is only executed if resultant length is LT 32755. MXGWARN messages are written to the log at 30K length, suggesting the use of INCODE1= option if needed. Note that the counts of INCODE length can be different between z/OS and ASCII. Thanks to Bill Davis, TransAmerica, USA.
VMAC110 NODUP PROC SORT of dataset CICDB2GL, which may be needed Dec 17, 2018 for NODUP protection. Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY. Change 36.243 If you specified READONLY=YES (which suppresses the aging VMXGALOC of old directories) and a directory did not exist, it was Dec 15, 2018 created but not populated. This could cause dataset not found errors but suppressing that creation could cause LIBNAME statements to fail. Now, VMXGALOC detects all of these conditions and only allocates the LIBNAMES that are found and does not create new ones with READONLY=YES and FIRSTRUN=NO. Change 36.242 Using BLDSMPDB with AUTOALOC=YES does two things. First, BLDSMPDB it allocates all of the directories needed to satisfy the Dec 15, 2018 parameters you specified - 5 weeks, 1 month, 7 days, etc. Then at the end of the daily processing it makes a 0 OBS copy of all of the datasets contained in the PDB. But if you ran (incorrectly) with FIRSTRUN=YES a second time, all of those datasets were set to 0 OBS by this process (intended to prevent DATASET NOT FOUND errors when running a weekly or a monthly process). Now, with FIRSTRUN=YES, it first looks to see if there are any datasets in the libref and if there are any datasets present, it's assumed you did not really mean it, it prints a warning message, and bypasses the 0 OBS copy.
ADOCRMFV more ZRBxxx datasets where they are likely to be useful. ASMRMFV -The original MXG01 record written at CLOSE is now split EXZRBAS2 into an MXG01 written at VSAM OPEN, so the CPC_CECNAME IMACRMFV could be captured for all RMF III datasets (it's kept VMACRMFV kept where it makes sense). and an MXG02 record written Dec 18, 2018 at CLOSE with those statistics. Dec 23, 2018 -Datasets ZRBAS1 and new ZRBAS2 decode the MXG01 and MXG02 records. -ZRBASI variables ASITRT/ASITET are 1024 microsecond units but weren't multiplied by 1024. ASIDCTIA_S is 128 usec but wasn't multiplied by 128. -New ASIPHTCP='ENCLAVE*ON*GP*TIME=ASIPHTMA-ASIPHTZI is created to complete the CPU Schematic in ZRBASI: <------------GP------------><----ZIIP----> <--ASICPUTA--><--ASIPHTCP--><--ASIPHTZI--> 0.083 0.048 37.692 0.131 ASIPHTMA=37.740 ASITRT/ASITET=29.696 -In dataset ZRBLCPLPAR, the CPC Capacity report, the value under MSU ACT is the variable ZRBLCPCPUMSUHR, but that is the interval MSU extended to an hour by MSU*3600/DURATM so it is NOT the 4HR MSU value. -Incremental improvements and some fixes. -Positioning for a future new filtering feature. -FROMTIME= and TOTIME= now support optional seconds for time values in ASMRMFV. The time format used depends on the number of digits coded as follows:
-------- ---------------------------- 0 RMFV057I NULL VALUE message 1 000M00
2 00MM00 3 0HMM00
4 HHMM00 5 0HMMSS
6 HHMMSS > 6 RMFV004E ERROR message Example Full Equivalent Time --------------- --------------- -------- FROMTIME=1 FROMTIME=000100 00:01:00 FROMTIME=12 FROMTIME=001200 00:12:00 FROMTIME=123 FROMTIME=012300 01:23:00 FROMTIME=1234 FROMTIME=123400 12:34:00 FROMTIME=12345 FROMTIME=012345 01:23:45 FROMTIME=123456 FROMTIME=123456 12:34:56 -Seconds are NOT supported in Relative Time values such as FROMTIME=*-nnS because this time offset unit from the current time is too small to be of practical use when building a PDB. The minimum Relative Time is 1 minute. -Origin message RMFV009I for each RMF III data set processed will now include the CPCNAME (aka CECNAME) for z/OS Release 3.3 and up. If the LPAR is running under z/VM then the CPCNAME will display as VMGUEST. For lower z/OS releases the CPCNAME shows as N/A as RMF III does not track this information at lower levels. -New information only message RMFV057I KEYWORD VALUE IS NULL issued when an ASMRMFV keyword has no value assigned. For example, FROMDATE= . Before this change the keyword would be ignored with no user notice. -Warning message RMFV085W is now issued when a filter or or parameter requires a specific RMF III table, but the table has not been selected. Avoid this message by specifying all desired RMF III tables first before any other parameters that need them. For example, ASIJOBNAME=MYJOB11 requires the ASI table. -Improved display format when a single character error is detected showing both EBCDIC and hexadecimal values for the character. -Initialization message RMFV001I now shows the size in bytes of the step level program used to invoke ASMRMFV (usually ASMRMFV itself). -New message RMFV091I is issued when the IBM modules ERBR3DEC (RMF III Decompression) or IGGCSI00 (Catalog Search Interface) are loaded into the user region. Warning message RMFV091W is issued if the module cannot be identified as an IBM module. In this case this could be a duplicate naming problem with a third party product. -MXG table MXG01 has been split into two tables for each RMF III data set processed. MXG01 contains VSAM data set Open statistics and MXG02 contains VSAM data set Close Statistics. These both appear in the ASMRMFV log in Detail and Summary reports. -Former message RMFV075W is now message RMFV090W. RMFV075* is now used for table id mismatch errors.
one ASMRMFV parameter appeared in one SYSIN record. -Messages RMFV012I and RMFV013I could show incorrect GMT offset values for the last sample range and last selected times. -Space message RMFV031I always showed an EF (Extended Function) VSAM type even for non-EF VSAM data sets. -Message RMFV035* showed an incorrect reason in ASMRMFV Yüklə 28,67 Mb. Dostları ilə paylaş:
|