* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
READDB2 31.163 WPS ONLY. WPS Compiler macro resolution error. READDB2 31.165 PDB.DB2STAT1 not created with READDB2 STATISTICS. READDB2 31.167 DB2 V8 ONLY. V8-only IFCID=225 were not read. READDB2 31.191 READDB2 PDBOUT=, or PDBOUT=XXX may not work right. READDB2 31.191 READDB2 revision for PDBOUT=WORK or PDBOUT=XXX. READDB2 31.269 "Too few" IFCIDs listed caused no sort to PDBOUT. RMFINTRV 31.138 Multi-period RSP/TRN/SWP mislabeled BAT1 vs BATHI. TYPE0 31.193 TYPE 0 IPL RECORD now 68 bytes in z/OS 2.1, DELETED. TYPE0 31.193 z/OS 2.1 SMF ID=0 Length changed, record DELETED. TYPE102 31.001 Support for variable QW0141OT in T102S141 dataset. TYPE102 31.027 Variable QWHCEUWN added to T102Snnn DB2 datasets. TYPE102 31.166 Support for IFCID=380 STORED PROCEDURE DETAILS TYPE102 31.258 Support for IFCID 359, "DB2 Statement ID" decoded. TYPE102 31.261 Support for DB2 IFCIDs 370 and 371 (OPEN/CLOSE TRACE) TYPE102 31.278 Support for DB2 Trace IFCID=733 PSEUDO DELETE CLEANUP TYPE110 31.012 CICLDR output tests LDRTU instead of LDRFC. TYPE110 31.048 MXG 31.01 only, STID=29, CICSMDSA dataset wrong. TYPE110 31.075 ASCII execution, RTYPE/RRTYPE may be incorrect. TYPE110 31.110 CICS/TS 5.1 MNSEGCL=5 file resource INCOMPATIBLE. TYPE110 31.214 CICSJS variables SJSMAJCP/SJSMINCP are not CPU time. TYPE110 31.253 SMSGDHWM/SMSGCCUR correction for CICS/TS 4.2 or later TYPE111 31.283 Support for CICS Transaction Gateway V9R0 (COMPAT) TYPE113 31.003 Message UNINIT VARIABLE SM1132MM minimal impact. TYPE113 31.169 SMF 113 vars DWINSORM and DWDASORM wrong for zEC12. TYPE113 31.169 SMF 113 vars SM1132MT and SM1132MM were blank. TYPE113 31.172 Macro to re-label SMF 113 counters for old machine TYPE113 31.208 ASUM113 LPARBUSY/MIPSEXEC wrong for zEC12 processor. TYPE115 31.179 Support for MQ 7.1.0 SMF 115 subtypes 5, 6, and 7. TYPE115 31.188 New TYPE115S dataset for SMDS/QEST data. TYPE115 31.188 Support for MQ SMF 115 ST 2 SMDS/QESD, new TYPE115S. TYPE117 31.199 S17NNDM added to the BY list _B117NOD for NODUP. TYPE119 31.218 INVALID DATA FOR SCACTIME in ID=110 SUBTYPE=32. TYPE120 31.143 TYP1209E variables SM1209DA-DF are accumulated. TYPE120 31.170 Variable SM1209BK (Short Server) added TYP1209C/S/U. TYPE30 31.277 TYPE30MU dataset now has zero obs by default: useless TYPE30 31.280 IOTMNOCA=SMF30AIC-IOTMDASD corrected (was IOTMTOTL). TYPE42 31.216 INVALID DATA FOR S42CSYNC. TYPE6 31.106 PRINTWAY and PSF TYPE6 TASKTIME TCP/PSF/TCPE values. TYPE6 31.207 31.07 only. Debugging SMFLN3=162 LENLEFT=552 removed. TYPE70 31.130 SHARE Weights for zIIP/zAAPs corrected. TYPE7002 31.220 Enhancement to CRYPTOGRAPHIC PROCESSOR (70-2) support TYPE7072 31.174 WARNING: MULTIPLE LENGTHS FOR IFAUPTM and Tutorial TYPE7072 31.266 MSU Units (Hardware vs Software) in TYPE70/TYPE72GO. TYPE7072 31.274 System with only CPs + ICFs, LPAR SHARE weight wrong. TYPE70PR 31.140 SMF70GNM, Group Name, blank in 31.03-31.04. TYPE74 31.072 Format MG0748L new value for 16 GB/s Link Type TYPE78CU 31.127 Vars R783DCTM/DDTM (CU Connect/Disconnect) added. TYPE80A 31.257 TOKDANAM='UTYPE' ERROR if last, new TOK variables. TYPE85 31.006 Support for OAM SMF ID=85 STs 90,91,92 and 93. TYPE90A 31.045 ID=90.6,7 EVENTIME is IPLTIME of the system. TYPEBETA 31.036 BETA93 had invalid data in BETA1 for 4.2.0 and 4.3.0. TYPEBETA 31.162 Variable JOB and BETAJOBN are now consistent. TYPEBVIR 31.016 Support for BVIR Version 2.0/2.0a/2.1. TYPEBVIR 31.039 Option to add SYSTEM value to IBM TS7700 BVIR data. TYPEBVIR 31.168 Support of Hydra/BVIR Version 3 new data fields. TYPEBVIR 31.254 BVIR30 dataset was incorrect with VERSION 3 records. TYPECIMS 31.137 IMF TRXZxxxx variables incorrectly input. TYPECIMS 31.206 Support for IMF 5.1 (INCOMPAT, but only CIMSDBDS). TYPECIMS 31.233 Correction for IMF 4.2 thru 5.1 (WRONG VALUES) TYPEDB2 31.015 "Truncated" QPACLOCN/COLN/PKID/ASHC/AANM maybe wrong. TYPEDB2 31.056 Variable THREADS now correctly set for ROLLUPs. TYPEDB2 31.081 Support for DB2 V10 ID=100 Subtype 5 DB2STAT5 dataset TYPEDB2 31.093 DB2STAT5 "INVALID" record supported, STARTUP event. TYPEDB2 31.108 DB2STATS vars QXSTCWLP+ and QISTWMXU incorrect. TYPEDB2 31.117 DB2 V10. All QLSTxxxx numerics WRONG (DBSTATR/STATS). TYPEDB2 31.196 Support for APAR PM67806 adds QW0225DMH DMH GETM. TYPEDB2 31.196 Support for DB2 APAR PM67806 adds QW0225DMH DMG GETMs TYPEDB2 31.240 Support for DB2 V11.1. MXG 30.30 TOLERATES, see text. TYPEDB2 31.245 Support for APAR PM90886 new IDAA/NETEZZA ELIGIBLEtm. TYPEDB2 31.259 Variable QWHSNIDIP=IP*ADDR*FROM*QWHSNID QWHCATYP=8 TYPEDB2 31.272 Invalid SMF 101 subtype 1 from ASG TMON/DB2 DB2ACCTP. TYPEDB2 31.275 MXGWARN: T102S225 DOES NOT EXIST. TYPEDB2 31.282 DB2PM *ROLSUM*,*ROLLUP* both now set DB2PARTY='R'. TYPEEDGR 31.118 Support for EDGRXEXT variables added in z/OS 1.13 TYPEIDMP 31.018 Support for PACE's IDMS 17 KOMAND/IDCS SMF record. TYPEIDMS 31.197 After MXG 30.30, only IDMS 17, zero obs in IDMSINS. TYPEIMS 31.102 IMS 13 inserted field in 07 Log record INCOMPAT TYPEJESC 31.225 Support for Emtex JESCONNECT SMF Record. TYPENMON 31.058 NMON records SEA, SEAPACKET, DONATE are supported. TYPENMON 31.119 Variables IPCSTIME and TIMEZONE added to NMONBBBP. TYPENMON 31.164 Protection for invalid NMON DISKxxxx records. TYPENMON 31.264 Support for Red Hat Linux Data Group,NFSCLIV4 metrics TYPENTSM 31.030 Major update for NTSMF adds datasets and variables. TYPEPDM 31.226 Support for Alebra Parallel Data Mover SMF record. TYPEPRPR 31.054 Corrections to '1031' and '1061' records. TYPERACF 31.146 INPUT STATEMENT ERROR RACF UNLOAD, invalid data too. TYPERMFV 31.004 RMF III, z/OS 1.13 APAR OA38660 ASI data wrong. TYPERMFV 31.021 RMF III Enhancements TYPERMFV 31.074 RMF III dataset ZRBLCP var LCPUPOLR/CHIN/CHIX wrong. TYPERMFV 31.273 Support for RMF III CATG3 Cache Data ERB74CA dataset. TYPERMRV 31.062 RMF III Enhancements - blocking CPU and CPCDB. TYPESHDE 31.177 SHADOW variable SM01ADCT ADABAS COMMAND COUNT wrong. TYPETLMS 31.215 Support for new TLMS variables, compression percent TYPETMD2 31.133 Support for TMON for DB2 Version 5 second iteration. TYPETMMQ 31.020 Support for TMON/MQ Version 2.15 new data. TYPETMMQ 31.190 Many new variables added to TMMQQU MQ QUEUE dataset. TYPETMMQ 31.190 New variables added to TMMQQU. TYPETMNT 31.010 MSGID NOT FOUND for MXGTMNT SYSLOG SUBTYPE 8 record. TYPETPMX 31.116 TYPETPMX variable JOBNUM truncated if 6 digits long TYPETPMX 31.263 ERROR.VMACTPMX. VARNAME=$INCLAI or $DBS_SD NOT FOUND. TYPEVFTP 31.023 Support for Software Diversified Services VFTP SMF. TYPEVIP 31.022 Support for Software Diversified Services VIP SMF. TYPEVMXA 31.151 Support for zVM 6.3 MONWRITE, INCOMPAT due to MXG. TYPEVMXA 31.194 31.02-31.06, z/VM 6.2.12, STOSHG BROKEN CONTROL REC. TYPEVMXA 31.194 MXG 31.02-31.06 BROKEN CONTROL, STOSHD MRHDRLEN=112. TYPEWWW 31.052 IIS Weblog URIQUERY with &=1 and no name supported. TYPEWWW 31.137 IIS Log with ' ... ' COOKIE value caused MXG loop. TYPEXAM 31.160 Support for Velocity Software new segments new data. TYPEXDFG 31.049 Support for WAS XD (WebSphere Extended Deployment). TYPEZPRO 31.167A VOLTAGE Release 4.2 segment count circumvention. UTILBLDP 31.276 Tool to ad hoc read SMF is enhanced WANTSMF= list. UTILEXCL 31.051 ***UNKNOWN FIELD*** protection still didn't protect. UTILEXCL 31.147 Support for CANPROD4, CANPROD5 and CANPROD6 fields. UTILEXCL 31.295 Negative values in variable TASELGTM with IMACEXCL. VGETOBS 31.180 Circumvent WPS ABEND with unopened LIBNAME on tape. VGETOBS 31.200 Revisions in concert with VMXGWORL for READDB2. VGETOBS 31.212 Final (?) revisions to VGETOBS to bypass tape mounts. VGETOBS 31.247 ERROR: WORK.MXGTABLES NOT FOUND with earlier VGETOBS. VGETOBS 31.250 A better way to identify TAPE data libraries. VGETWKLD 31.028 Hardcoded VIEWs removed. VMAC73 31.291 SMF73SPD Channel Speed now always in MBits/sec. VMAC80A 31.139 Support for RACF TOKDANAM='UNAME'. VMACSMF 31.014 New %LET SMFPUTHD=NO; suppresses header messages. VMXGINIT 31.285 JCL //INSTREAM DD is no longer required for z/OS MXG. VMXGRMFI 31.268 Some RMFINTRV xxxxSWAP xxxxTRAN xxxxEXCP un-formatted VMXGSRCH 31.171 UNABLE TO CREATE WORK.TABLES.DATA BECAUSE ..VIEW.... VMXGSRCH 31.219 Search which character variables contain text string. VMXGWORL 31.200 Revisions in concert with VGETOBS for READDB2. WPS 31.224 Current status of WPS circumventions and differences.
Inverse chronological list of all Changes: NEXTCHANGE: Version 31. ====== Changes thru 31.296 were in MXG 31.31 dated Jan 20, 2014========= Change 31.296 -RMF III Enhancements and Fixes ASMRMFV -New parameter TABERR=ABEND/IGNORE/WARN directs ASMRMFV ADOCRMFV when one or more RMF Monitor III table validation ZASMRMFV errors have occurred (default WARN). Table validation Jan 18,2014 has been part of ASMRMFV since Change 31.080 in MXG V31.02.
conflicting data from being absorbed into an MXG PDB that could be difficult to detect, diagnose, and resolve. -A validation error occurs when an offset or length within a table is not as expected or is logically inconsistent. For example, the length of the table header is greater than the total table length. This should be a VERY RARE event.
0000 when such errors occurred thus making it appear that there were not any problems in the ASMRMFV run.
one or more table validation errors occur. This is the only condition for which this Return Code is issued.
skipped and thus the data will not appear in the result PDB.
reported to MXG Technical Support as soon as possible. Use TABERR=IGNORE to bypass these errors and not set Return Code 0016 until the issue can be resolved. -Such tables are skipped and written to the optional RMFSKIP DD if present in JCL. They will not be included in the result PDB so all data in the table is lost. These are not reliable data sources and could result in more serious problems if they were input to a PDB build.
reports table validation errors both in ASMRMFV detail and summary reports. In some cases RMFV035* will report more details on the specific error. -Prologue documentation in ASMRMFV source code and in the ADOCRMFV member has been updated with a discussion of the TABERR= parameter.
RMFBSAM file is improved by using block data moves to the output buffer when moving contiguous entries within a table. In the past ASMRMFV moved single entries at a time. This applies to the CPD, CSR, ENT, OPD, and SPG tables only. -RCD processing did not include the RCDRD section when validating this table and this is corrected. -ASMRMFV was initializing variable mode messages before PARM processing was complete so that *ERR= PARM overrides were not affecting the corresponding message format. The overrides were functional but the corresponding message format could be incorrect.
archival ZASMRMFV member intended only for use with non-z/Architecture hardware. No other changes after Change 31.181 are included as this member is stabilized. -REQUIREMENT: In order to receive these improvements the current ASMRMFV utility program from this MXG change must be installed. See MXG SOURCLIB member JCLASM3 for sample JCL for the assembly and link-edit install steps. Change 31.295 Negative values in variable TASELGTM, zIIP Eligible time, UTILEXCL in dataset CICSTRAN, when UTILEXCL was used to create the Jan 18, 2014 tailored IMACEXCL member (support for EXCLUDEd fields in your CICS SMF 110 records). The generated IMACEXCL code incorrectly subtracted TASZIPTM from OFFLCPTM. -UTILEXCL logic to KEEP TASELGTM,TASZIPTM was added. Thanks to Paul Volpi, UHC, USA.
GRAFWRKX see what your workloads would look like on a different Jan 18, 2014 CPU model. Formats TMPSUSEC and TMPNRCPU are defined in member GRAFWRKX to map NEWMODEL to Hardware SU_SEC and NRCPU Engine count for MSU Capacity for the new processor, to recalculate CPU time and percent busy. Change 31.293 Sample JCL to create PDB.ASUMUOW, PDB.CICS for TMON/CICS. JCLUOTT2 The MONICICS file is read with tailored "TYPETMO2" logic Jan 16, 2012 to create MONITASK dataset, but KEEPs only the variables that are needed, to save disk space, CPU, and I/O. Then, MONITASK dataset is summarized by ASUMUOW and ASUMCICX to create the PDB.ASUMUOW and PDB.CICS summary datasets. No DB2 nor MQ data is processed in this example.
VMXGPRNT TITLE1 by VMXGPRNT. However, see also MXGLABEL that is Jan 15, 2014 added by Change 31.288 which may be simpler to learn! -MXGWARN that WORK.SP_L does not exist is suppressed. Thanks to Scott Barry, SBBWorks Inc, USA.
FORMATS in Bits/sec otherwise with Bits/sec in the label, but it VMAC73 makes more sense to label and store MBits/sec for this VMAC79 new Channel Speed metric added by APAR OA22918 for z196 Jan 16, 2014 (High Performance FICON support). SMF73SPD is zero for FICON Express 4 channels; the enhanced metrics are only generated by FE-8 and FE-8S or later channels. -Variable SMF73CPP in TYPE73 and R79CCPP in TYPE79 are decoded by MG073FR format to display the channel path frame size (16/24/40/64KB). Thanks to Dr. H. Pat Artis, Performance Associates, USA. Thanks to Brian Currah, Independent Consultant, CANADA. Change 31.290 For TMON/CICS Transaction Records, 'TA', the IHDRTMO2 IHDRTMO2 exit is now taken AFTER the offsets to the 22 subsections VMACTMO2 have been INPUT so you can know what data is present and Jan 15, 2014 so you could reset the NUMBER to zero to suppress their processing; IHDRTMO2 comments identify entry variables.
VGETOBS notably in VMXGUOW if MQ/DB2/CICS is suppressed. Jan 12, 2014 This change detects the _NULL_ and returns eliminating warning messages. Change 31.288 New MXGLABEL macro reads the contents of a SAS dataset to MXGLABEL create a LABEL statement with the VARIABLE NAME and LABEL Jan 16, 2014 as the label's value for each variable in that dataset. These labels are the same as VMXGPRNT/VMXGPRA1/VMXGPRAL print, but if you know how to use PROC PRINT, you can use MXGLABEL and not have to learn those program's arguments: %MXGLABEL(DATASET=PDB.JOBS,NAMEPOSITION=BOTTOM); PROC PRINT DATA=PDB.JOBS SPLIT='*'; &MXGLABEL; TITLE PRINT WITH NAME AND LABEL OF DATASET &MXGDATASET; The VARIABLE NAME can be at the TOP or BOTTOM of the new label when split-printed, and you can choose the bookend character (around the variable name) and even change the asterisk SPLIT CHARACTER. -%MXGLABEL also creates a macro variable &MXGDATASET with the name of the dataset dataset name (like for TITLEs). -The LABEL statement is returned in both the old-style macro token _MXGLABL and in the macro variable &MXGLABEL. -Macro variables are limited to 64K characters, and with a 32-character name and 40-character label, only 858 vars labels would fit in 64K text, but this implementation has no such limit, by storing only the NAME of the old-style macro (%LET MXGLABEL= _MXGLABL;) for the macro variable's value, so only your disk space limits amount of code. THIS ONLY WORKS IF &MXGLABEL IS EQUATED TO _MXGLABL TEXT BEFORE MACRO _MXGLABL IS INSTANTIATED. Equating after instantiation will fail if the expanded text exceeds 64K. -The USEFILE argument defaults to MXGLABEL and writes to the WORK file as a CATALOG so it can be any 8-character file name for the write and read. See Change 31.285. -A LABEL statement AFTER the &MXGLABEL statement will override the stored label; SAS uses the last statement. Change 31.287 MXG 31.02-31.09. ASMRMFV could skip RCD tables during ASMRMFV validation added in Change 31.080 (MXG 31.02) of the Jan 12, 2014 RCDSD/RCDPD section entry lengths. There were no error nor warning messages, but an uncleared register could cause the calculated length to exceed 32K which caused the entire RCD record to be not be written to RMFBSAM, causing RCD datasets to have zero observations. (The ASMRMFV report of record types read/written did show there were RCD records read but now all written.) The register is now cleared in the two overlooked places. -This change to ASMRMFV also requires MXG at 31.09 to read the new RMFBSAM 31.287 records, due to new source members added to support the CAT records. Specify NOCAT instead. -However, if you update your current ASMRMFV with these two one-line-inserts in ASMRMFV, the RCD records won't be skipped, and your current MXG VMACRMFV processing will correctly populate the RCD datasets. Find these two ICM statements in your ASMRMFV and insert the SR statement between the JL and ICM like this:
SR R0,R0 SET REG0=0 <===ADD THIS LINE ICM R0,3,RCDPDAL(R9) GET LENGTH OF ONE RCDRD ENTRY
SR R0,R0 SET REG0=0 <===ADD THIS LINE ICM R0,3,RCDSDAL(R9) GET LENGTH OF ONE RCDRD ENTRY
link-edit installation of the EDITed ASMRMFV. Thanks to LaRae Balthazor, Charles Schwab, USA Thanks to Anh Ngo, Charles Schwab, USA Change 31.286 If you specified MXGxxxxx=NO, to skip that report, errors ANALDB2R resulted: ANALDB2R syntax error caused that parameter to Jan 11, 2014 be compiled as a DATA step statement, but there was no semi-colon to end the statement, causing various errors. NO or blanks are now taken as NO.
not passed to READDB2 so ALL records were read and then selection was done by ANALDB2R after READDB2, where it should have been done to minimize disk,I/O,CPU,etc. PLAN is now included in this list of parameters that can be passed from ANALDB2R to READDB2 for READDB2 selection. AUTHID BEGTIME CONNID CONNTYPE DB2 ENDTIME PLAN Thanks to Stephen Hughes, Excellus, USA. Change 31.285 SEE CHANGE 32.022 WHICH REMOVED THIS CHANGE FROM MXG. VMXGINIT INSTREAM FILEREF OR DDNAME IS STILL REQUIRED IN MXG. Jan 13, 2014 ORIGINAL CHANGE TEXT: Feb 4, 2014 The //INSTREAM DD is no longer required for MXG on z/OS. Now, VMXGINIT, at MXG Initialization, executes FILENAME INSTREAM CATALOG 'WORK.MXGTEMP.INSTREAM'; which allows INSTREAM to be used as an external I/O file. On z/OS, the CATALOG will be used when there is no DD. On ASCII, the VMXGINIT FILENAME INSTREAM is always used, since it will be after any FILENAME in AUTOEXEC and will replace an existing INSTREAM fileref if one exists.
//INSTREAM DD in the JCL, or FILENAME INSTREAM, because MXG writes text (SAS statements) to it "on the fly" and a %INCLUDE INSTREAM; executes the created program code. -The CATALOG syntax has a three or four part name FILENAME INSTREAM CATALOG 'lib.catalog.entry.entrytype' where entrytype can be anything for READ, but only LOG, OUTPUT, SOURCE, or CATAMS (the default 4th) for WRITE. -In testing this transparent enhancement, I re-discovered .On z/OS or ASCII, FILENAMEs allocated with a FILENAME can be CLEARed, and the MXGNAMES/VMXGCNFG JCL for z/OS uses FILENAME INSTREAM, so INSTREAM it could be cleared. .On z/OS, FILENAMEs allocated in JCL cannot be CLEARED. .But you should never need to CLEAR the JCL INSTREAM DD: There's nothing that precious about FILENAME INSTREAM except that it is guaranteed to be there when needed. Especially since you can't clear the JCL DD anyhow! You can always use a different NAME in your FILENAME statement, with either CATALOG or TEMP to create an external file for your "instream" code creation. I did consider using TEMP instead of CATALOG for INSTREAM default in VMXGINIT, but on z/OS the CATALOG syntax is simpler, while the more complex (but more powerful) TEMP option requires device and size and JCL DD stuff. .ERROR: Catalog WORK.MXGTEMP DOES NOT EXIST if you try to read INSTREAM (INCLUDE/INFILE) before it was written. Change 31.284 If you specified MXGMQADD=NO and executed _SUOWMQ you got VMXGUOW a SAS message that a data step was being stopped because Jan 9, 2014 it was looping. This was caused by the absence of a SET statement that is conditionally executed if MXGMQADD=YES. An ELSE STOP; was added to prevent the message (which did not cause an ABEND or failure.) Change 31.283 Support for CICS Transaction Gateway CTG V9R0 (COMPAT). VMAC111 -Variable CTGSTART, DAEMON*START*DATETIMESTAMP is INPUT Jan 9, 2014 and kept in all TY111xx datasets. -New variables added to TY111GD Daemon dataset: CTGIRESP='INTRV*DAEMON*AVG RESP*WITH I/O' CTGLRESP='LIFE*DAEMON*AVG RESP*WITH I/O' CTGIXNHI='INTRV*PEAK*INFLIGHT*XA TRANS' CTGIXNHI='LIFE*PEAK*INFIGHT*XA TRANS' See correction in Change 32.007.
VMACDB2 display '*ROLSUM*' for DB2 V10 Packages with QPACRUSM='Y' Jan 8, 2014 for the new Rollup Summary record flag, while '*ROLLUP*' is unchanged in V9 if QPACROLL='Y'. With this alert, MXG variable DB2PARTY='R' is now set if QPACRUSM='Y' so both Rollup and Rollup Summary records are identified in the DB2ACCTP dataset.
VMAC102 input as 4 bytes when it is a 2 byte field, which caused Jan 8, 2014 wrong values in QW0377FL/QW0377PG/QW0377NU. (This was my bad for missing my own coding error, that Yüklə 28,67 Mb. Dostları ilə paylaş:
|