* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
Feb 9, 2016 is removed as they contain EBCDIC text, not HEX. Feb 11, 2016 -STC variables STCxxRID are now HEX4 formatted, as they Feb 24, 2016 contain numeric hex values. -New format $MGSTCMV maps values in variable STC16MVC. -New variables decode bits of SMF17DFL: STC17DRX='RETENTION*PERIOD*REDUCED?' STC17DAR='AUTO*RECALL?' STC17DMF='FULL*MVS?' STC17DYV='RTD*VARY*COMMAND?' STC17DSW='MVC OR*RTD*REQUIRED?' STC17DRT='RETAIN*PERIOD*APPLIED?' and RID variables show 0-F as their range. -STC11TOL has a third value now supported. -STC11CSP is relabeled CHANNEL TYPE and formatted. -Some labels with "MVS" are corrected to "MVC". Thanks to Randy Hewitt, Hewlett Packard, USA.
EXNDMSE DDDDDD DATASET DESCRIPTION IMACNDM NDMSE NDMSE NDM SESSION END VMACNDM
VMXGINIT Feb 8, 2016 Thanks to Gerard Bosker, RaboBank, THE NETHERLANDS.
VMACMAR TO DO: Subtype 7. Await data in March. Feb 6, 2016
ANALGRCA Inputs are PDB.RMFINTRV,PDB.SMFINTRV,PDB.ASUMCELP. Feb 6, 2016 See Change 34.044 for GRAFWRKC and a comparison.
EXDVS01 New datasets created EXDVS02 DDDDDD DDATASET DESCRIPTION IMACDVS DVS01 DVS01 DVS CLIENT SYSTEM RECORD TYPEDVS DVS02 DVS02 DVS INTERVAL SUMMARY RECORD TYPSDVS -The DVS01 interval dataset is written for each Connection VMACDVS ID, variable DVS1CNID. VMXGINIT -Mar 3: The two lines in the LENGTH statement extended Feb 5, 2016 beyond 72 characters; on z/OS only, those variables Mar 3, 2016 were kept in 4 instead of 8 stored bytes, so there would have been some truncation of datetime values, worst case 255 seconds. Change 34.013 DB2 dataset T102S166 for IFCID 166 variable QW0166SI is a VMAC102 statement identifier input $CHAR8 and format $HEX16, but Feb 4, 2016 it is the statement number, so new variable QW0166SINR is the numeric statement number; labels clarified. Thanks to Akhil Vasudevan, Capital One, USA.
GRAFWRKX value so that you can see which workloads are making Feb 2, 2016 the largest contributions to the rolling 4 hour avg.
ITRM ERROR: File WORK.SUMSTSBP.DATA does not exist. Feb 2, 2016 because the new DB2STSBP dataset is now added into the PDB.DB2STATS dataset, but the new _SDB2SBP sort macro was not known in ITRM ("NEW"!). -The correction is easy for BUILDPDB: ITRM 2.7: Originally reported in 33.301 and MXG 33.33 GA: ITRM users MUST add this statement %LET EPDBOUT= _SDB2SBP; inserted between %CMPROCES... and %CPSTART.... ITRM 3.4-3.6: New in this change: ITRM users MUST add %LET EPDBOUT= _SDB2SBP ; at the top of their SYSIN input. -For TYPSDB2 program, instead of BUILDPDB, create a new TYPSDB2 member in your USERID.SOURCLIB "tailoring" library with these statements: %INCLUDE SOURCLIB(VMACSMF,VMACDB2,IMACKEEP); DATA _VARDB2
_SMF _CDEDB2
_SDB2SBP _SDB2
-ITRM 3.7, when released later this year, eliminates this exposure by invoking the _SDB2 macro which MXG protects. Thanks to Harald Seifert, HUK-COBURG, GERMANY.
GRAFWLM variable MSUSOFT corrected and also re-labeled: VMAC7072 MSU72 ='CAPTURED*HARDWARE*MSU 72*COUNT*NOT A RATE' VMXGRMFI MSUSOFT ='CAPTURED*SOFTWARE*MSU 72*COUNT*NOT A RATE' Feb 4, 2016 HARDWARE MSU: ORIGINAL MSU SU_SEC BASED - LARGER SOFTWARE MSU: NEW MSU SMF70CPA/CECSUSEC BASED, for SOFTWARE PRICING. MSUSOFT can be a missing value if no prior RMF 70 for this system was found, since it needs SMF70CPA from the same-system's RMF 70 to calculate in the RMF 72 code. -These MSU variables are created in RMFINTRV and TRNDRMFI with per interval values: MSUINTRV ='TOTAL*HARDWARE*MSU 70*COUNT*NOT A RATE' MSUPERHR ='TOTAL*HARDWARE*MSU 70*EXTENDED*HOURLY RATE' MSUINTRVS='TOTAL*SOFTWARE*MSU 70*COUNT*NOT A RATE' MSUPERHRS='TOTAL*SOFTWARE MSU 70*EXTENDED*HOURLY RATE' -New Workload XXXXMSU variables (BATMSU,CICSMSU) and XXXXMSUS (BATMSUS,CICSMSUS) variables for each workload are created with these labels: BATMSU ='BATCH*CAPTURED*HARDWARE*MSU 72*COUNT' BATMSUS ='BATCH*CAPTURED*SOFTWARE*MSU 72*COUNT' -New chart of estimated hourly MSU used by IMPORTANCE in GRAFWLM (need all three of these updated members). Change 34.009 -BASECICS and BASEDB2 parameters added to match VMXGALOC VGETALOC logic and allow for different directories to hold the Feb 2, 2016 often large CISTRAN/DB2ACCT datasets. -The message that a LIBNAME could not be found is now suppressed unless MXGEXIMSG is YES.
VMAC115 was input as PIB8 instead of PIB8.6 and was missing the VMAC116 2016 the required divide by 4096 to convert to seconds. Jan 29, 2016 -New variables added to MQMACCTQ dataset. Feb 12, 2016 WTASPBHW='PUBLISH*HIGH*WATER*MARK' WTASPBTT='PUBLISH*TOTAL*ELAPSED*TIME' WTASPRCT='PREPARE*CPU*TIME' WTASPRET='PREPARE*ELAPSED*TIME' WTASPRN ='PREPARES' WTASSMRB='MESSAGE*BLOCKS*READ FROM*SMDS' WTASSMRP='PAGES*OF DATA*READ FROM*SMDS' WTASSMRS='SMDS*READS SAVED*DATA IN*BUFFER' WTASSMWB='MESSAGE*BLOCKS*WRITTEN TO*SMDS' WTASSMWP='PAGES*OF DATA*WRITTEN TO*SMDS' WTASSMWT='WAIT TIME*FOR SMDS I/O*COMPLETION' WTASTPCT='TOPIC*CPU*TIME' WTASTPET='TOPIC*ELAPSED*TIME' WTASTPN ='TOPIC*COUNT' Variable WTASCTSR is corrected in value and formatted as TIME16.6. -Type 115 dataset TYPE115S variable QESDBFPT was wrong; it contained QESDBFBT instead of BFPT. Thanks to Scott Barry, SBBWorks, Inc., USA.
VMACCIMS not correct, because new variables only in 5200 were read Jan 26, 2016 when they should not have been. Logic revised for 5100. Thanks to Betty Wong, Bank of America, USA. Change 34.006 -Change 33.024 incorrectly overlaid UTILRMFI with UTILWORK UTILRMFI when the SYSOTHER message was added, which eliminated the UTILWORK report. Jan 25, 2016 -UTILRMFI generates reports using your RMFMINTRV WORKnn definitions, finding any duplications, by comparing the SMF30s and RMF72s CPU times. -UTILWORK generates a skeleton RMFINTRV member based on SERVICE class or REPORTING class. Thanks to Michael Gebbia, Eddie Bauer, USA.
VMAC113 -Support for zVM HIS (SMF 113) PDB.VXPRCMFM intervaled. VMACVMXA Dataset VXPRCMFC is the old SMF 113 subtype 2 accumulated Jan 30, 2016 and VXPRCMFM is the newer SMF 113 subtype 1 intervaled, Feb 8, 2016 and only VXPRCMFM will be updated by IBM in the future. Feb 25, 2016 -SMF 113 EXTND counter labels for z13 were incorrect; the Feb 27, 2016 values and equations were correct, and now both VMAC113 Feb 29, 2016 (z/OS) and VMACVMXA (z/VM) have the same labels, which default to the labels for the z13 counters. (See Change 31.172 to change _XLA113 to earlier CPUs.) -All zVM MONWRITE VXdddddd datasets now have SYSTEM kept (most did), and all now have CECSER to identify both the software and hardware identifications. -RNI for zEC12 was updated to use 2.3 factor in VMACVMXA. -All calculated variables for the zEC12 were wrong; while VMAC113 was updated, VMACVMXA was not for VN2=3 data. -Support for Multiple CECs/SYSTEMs zVM data changed the sort order of all datasets by inserting CECSER SYSTEM ahead of BEGINMTR: BY CECSER SYSTEM BEGINMTR other vars. Thanks to David Cogar, Wells Fargo, USA. Thanks to Carl D. Ellis, Wells Fargo, USA.
FDRCRYPT syntax error. Jan 20, 2016 Thanks to Michael Gebbia, Eddie Bauer, USA. Change 34.003 A tailored BUILDPDB created a libname with view that PDBAUDIT caused an error when a PROC SQL read DICTIONARY.TABLES Jan 28, 2016 and returned a LIBNAME of _TMPLIB that didn't exist: ERROR: FILE _TMPLIB.XTY70CP.DATA DOES NOT EXIST. The error was in PROC SQL FROM DICTIONARY.TABLES and was difficult to diagnose as there are NO other references on the log to either that libname or that dataset name. This similar example causes an obscure LIBREF not found error: LIBNAME FRED (SASUSER); DATA FRED.DATA; A=1; RUN;
PROC SQL; CREATE VIEW WORK.WILMA AS SELECT * FROM FRED.DATA; QUIT; LIBNAME FRED CLEAR; PROC SQL; CREATE TABLE TABLES AS SELECT * FROM DICTIONARY.TABLES WHERE LIBNAME='WORK'; QUIT;
The error message is that libref FRED is not assigned, but if you weren't the author of this code, you wouldn't have had a clue that you needed a libref called FRED. -This MXG change excludes MEMTYPE EQ 'VIEW' from PROC SQL since only real data libraries are wanted in PDBAUDIT. -PDBAUDIT already skips reports on known SAS LIBNAMES, since its purpose is to audit YOUR data libraries; these additional LIBNAMES are also now skipped: APFMTLIB CTRLLIB ITMACR MAILLIB STMFMT STPSAMP ZOSRSTG1 -The PDBAUDIT report can be skipped if you chose, using %LET MXGPDBAUDIT=NO; in your SYSIN input.
ASUMHSM but four times (REQUEST, ALLOC, START, END) have no date, VMACHSM and if an HSM event spanned one or more days, those Jan 20, 2016 time values couldn't be used to calculate durations. This change creates these four new DateTime variables FSRTIMRDT='DATETIME*REQUEST*ISSUED' FSRTIMSDT='DATETIME*REQUEST*STARTED' FSRTIMADT='DATETIME*ALLOCS*COMPLETED' FSRTIMEDT='DATETIME*REQUEST*ENDED' from those four times, using END-SMF, then ALLOC-END and START-ALLOC deltas to detect when a prior event happened on the prior day and correct the date part. And these two new durations are now created: FSRQUEUETM='FSR*QUEUE*TIME*REQ TO*START' FSRSERVICTM='FSR*SERVICE*TIME*START*TO END' - The comparison of TIMEPART(SMFTIME)-FSRTIME, an 8-byte and a 4-byte stored variable produced non-zero deltas on the order of E-08, so the ROUND(delta,.01) function was needed to prevent false positives. -ASUMHSM was updated to use the new datetime variables. Thanks to Randy Hewitt, Hewlett Packard, USA.
VGETOBS is incorrectly parsed causing CHARACTER OPERAND ERROR: Jan 19, 2016 MXGNOTE: VGETOBS LAST UPDATED MAR 17, 2015 CHANGE 33.063 ERROR: CHARACTER OPERAND WAS FOUND IN THE %EVAL FUNCTION THE CONDITION WAS: %LENGTH(&VGETDSN) = 0 ERROR: THE MACRO VMXGWORL WILL STOP EXECUTING. Changing the text to ( ?? ) resolves the parse. The SAS default is NOCHARCODE, and the only MXG code that needs CHARCODE, member FORMATS, resets to NOCHARCODE, and that program is only run once to update formats for new MXG. Using CHARCODE in FORMATS allows one member to create the MXG formats on both ASCII and EBCDIC platforms, but the rest of MXG code is only validated with NOCHARCODE. Thanks to Francois Vancoppenolle, PVGroup, BELGIUM. LASTCHANGE: Version 34. =========================member=CHANGE33================================ /* COPYRIGHT (C) 1984-2016 MERRILL CONSULTANTS DALLAS TEXAS USA */
First MXG Version 33.33 was dated Jan 11, 2016, thru Change 33.321 MXG Version 33.13 was dated Dec 23, 2015, thru Change 33.311 First MXG Version 33.13 was dated Dec 21, 2015, thru Change 33.309 MXG Version 33.12 was dated Dec 1, 2015, thru Change 33.286 First MXG Version 33.12 was dated Nov 27, 2015, thru Change 33.284 MXG Version 33.11 was dated Nov 2, 2015, thru Change 33.260 MXG Version 33.10 was dated Oct 20, 2015, thru Change 33.250 MXG Version 33.09 was dated Sep 15, 2015, thru Change 33.217 MXG Version 33.08 was dated Aug 20, 2015, thru Change 33.195 First MXG Version 33.08 was dated Aug 17, 2015, thru Change 33.189 MXG Newsletter SIXTY-SIX was dated Aug 17, 2015. MXG Version 33.07 was dated Jul 22, 2015, thru Change 33.172 First MXG Version 33.07 was dated Jul 17, 2015, thru Change 33.170 MXG Version 33.06 was dated Jun 11, 2015, thru Change 33.141 MXG Version 33.05 was dated May 19, 2015, thru Change 33.128 Second MXG Version 33.05 was dated May 12, 2015, thru Change 33.124 First MXG Version 33.05 was dated May 12, 2015, thru Change 33.123 MXG Version 33.04 was dated Apr 29, 2015, thru Change 33.112 MXG Version 33.03 was dated Mar 31, 2015, thru Change 33.085 Second MXG Version 33.03 was dated Mar 29, 2015, thru Change 33.084 First MXG Version 33.03 was dated Mar 27, 2015, thru Change 33.083 MXG Version 33.02 was dated Feb 27, 2015, thru Change 33.047 First MXG Version 33.01 was dated Feb 20, 2015, thru Change 33.044 ANNUAL: MXG Version 32.32 was dated Jan 6, 2015, thru Change 32.309
http://www.mxg.com/Software_Download_Request Your download instructions will be sent via return email.
II. SAS Version requirement information. III. WPS Version requirement information. IV. MXG Version Required for Hardware, Operating System Release, etc. V. Incompatibilities and Installation of MXG 33.33. VI. Online Documentation of MXG Software. VII. Changes Log
and is updated with new notes frequently. All Newsletters are online at http://www.mxg.com in the "Newsletters" frame.
Member CHANGESS contains all changes that have ever been made to MXG. All MXG changes are also online at http://www.mxg.com, in "Changes".
I. MXG Version 33.33 re-dated Jan 18, 2016, thru Change 33.327. Major CHANGES added in MXG 33.33, dated Jan 18, 2016: TYPE110 33.326 MXG 32.10-First MXG 33.33. Increased CPU in SMF 110s from 300 to 500 seconds for 22GB SMF 110s, corrected. TYPEVMXA 33.327 Data set VMBYUSR missing many observations. VMXGALOC 33.325 Correction for WEEK1 allocation. TYPEXAM 33.324 zVPS variable CALENTMT changed from numeric, conflict
TYPE70EC 33.318 Data Set SORT70EC NOT SORTED, configuration changed. TYPE42 33.316 New variables compatibly added by z/OS 2.2. TYPE64 33.316 New variables compatibly added by z/OS 2.2. TYPE71 33.316 New variables compatibly added by z/OS 2.2. TYPE74 33.316 New variables compatibly added by z/OS 2.2. TYPE99 33.308 New variables compatibly added by z/OS 2.2. SMFSRCH 33.307 Support for multiple text strings in LOOKFOR=. ASUMCELP 33.306 Variables SMF70GNM, SMF70GMU, SMF70WLA added. ANALACTM 33.312 Correction for more than one service policy. Major CHANGES added in MXG 33.13, dated Dec 23, 2015: UTILBLDP 33.311 Execution stops if BUILDPDB=YES, with &SPINUOW error. Major CHANGES added in First MXG 33.13, dated Dec 21, 2015: Critical Change for ITRM USERS (MXG 33.12+): ITRM 33.301 ITRM users MUST add %LET EPDBOUT= _SDB2SBP; inserted between %CMPROCES... and %CPSTART.... ERROR: File WORK.SUMSTSBP.DATA does not exist. Critical Change for z/OS 2.2 MXGTMNT/TAPE MOUNT MONITOR: ASMTAPEE 33.207 ML-55 of ASMTAPEE/MXGTMNT REQUIRED for z/OS 2.2. IBM changes cause ABEND S0E0-28, must reassemble. New Products Support TYPEIMS 33.298 Support for IMS 14.1 log records (COMPATIBLE) TYPE74 33.305 z/OS 2.2 RMF 74 Subtype 10 creates TYPE7410/TYPE74SC, (new Storage Class Memory data). TYPE78 33.305 z/OS 2.2 new variables in TYPE78PA. TYPEVMXA 33.299 Support for zVM 6.3 MONWRITE z13 SMT MODE. Errors Corrected: TYPEDB2 33.303 Multiple DB2 100 Subtype 1 created multiple DB2STATS. TYPE102 33.294 SMF 102 IFCIDs 81E5-8160,8051x INPUT EXCEEDED DRROR Enhancements ANALIDDY 33.290 ANALIDDY tabulates ANALID SMF data by date, used to investigate SMF dumping problems. Major CHANGES added in MXG 33.12, dated Dec 1, 2015: Reason for this new version: TYPE7072 33.280 PDB.TYPE70 z13 SMT mode ZIPCPUS value may be wrong. New Products Support: TYPEDB2 33.279 Support for DB2 Simulated Buffer Pool PDB.DB2STSBP. MOBWRK02 33.279 Support for DB2 Simulated Buffer Pool dataset. TYPE102 33.264 Support for APPTUNE 11.2 INCOMPATIBLE change in 8005. TYPE119 33.262 Support for SMF 119 subtypes 2, 5, 6, 7, 41-44, 97. Errors corrected: TYPE102 33.273 DB2 SMF 102 IFCID=109 INVALID DO LOOP CONTROL ERROR. TYPE1415 33.270 Variable SMF14ALIAS misspelled so it was not kept. TYPE120 33.267 SMF 120 dataset TYP120JI only output first instance. TYPEXAM 33.266 MXG 33.11 only. ERROR VARIABLE SYTPN NOT FOUND. TYPETPMX 33.265 ThruputMgr TPMSLM variables TPMSLXGF/LXGN wrong. Enhancements: JCLASMXG 33.275 Assemble/Link Edit all five MXG ASM programs install. ASMRMFV 33.274 ASMRMFV Updates. MXGLOG 33.162 MXGLOG write enabled by //MXGLOG or FILENAME MXGLOG, automatically. Major CHANGES added in MXG 33.11, dated Nov 2, 2015:
TYPE110 33.257 CICS/TS 5.3 BETA CICSTRAN new field added INCOMPAT This should be the last REQUIRED MXG update for CICS/TS 5.3. New Products Support: TYPEXAM 33.259 Support for zVPS Release 4230 for z13 SMT mode. Enhancements: TYPEIMST 33.252 Variable SYSTEM can be added to TYPE56FA with SYSPARM Major CHANGES added in MXG 33.10, dated Oct 20, 2015: New Products Support: TYPE121 33.231 Support for JZOS Java Runtime Performance SMF 121. TYPEATF 33.245 Support for OMEGAMON ATF IMS Log Record LCODE A2. TYPE6 33.233 Support for APAR OA46136 adds IPADDR in PSF SMF 6. TYPEVMXA 33.242 Support for zVM 6.3.15.0 VXSYSPRT for z13 SMT mode. TYPERACF 33.238 Support for RACF IRRDBU00 Record Type 1560. TYPEEDA 33.237 Support for EDA V7706 (INCOMPATIBLE, data inserted). TYPETPMX 33.232 Support for Thruput Manager VARNAME=$ORIGIO. TYPEDOS 33.248 Support for zVSE/Power Version 9 Release 2 accounting Enhancements: ANALCAPD 33.225 Major revision to analysis of Capping, now by LPAR. ASMRMFV 33.222 RMF III DVT Character data Filtering saves DASD. ANAL2642 33.230 Example to select TYPE26 and match with TYPE42. ANAL1430 33.230 Example to select TYPE14 and match with TYPE30. VMACUCB 33.245 DEVCLASS=41 decode identifies specific CTC type. TYPE80A 33.243 RACF Type 80 record "subtypes" (RACFEVNT) for ANALID. IMAC30IO 33.240 EXCPxxxx and IOTMxxxx can be dropped for nonexistent. TYPE7072 33.239 New _KTY70DR to drop variables from TYPE70 dataset. TYPE102 33.236 All DB2 zPARM QWP4xxxx fields are now correct. TYPE42 33.230 Summed vars S42READS,S42WRITES added to TYPE42DS. Error Corrections: TYPE74 33.234 TYPE74HO false duplicates were being removed. TYPENDM 33.229 NDM PT records INPUT EXCEEDED, INCOMPAT inserts. TYPE22 33.227 Dataset TYPE22PB RECONFIG PCIE had zero observations. TYPE74 33.228 SMF 74 St 9 z/OS 2.1 z/13 INPUT STATEMENT EXCEEDED. TYPE103 33.223 Short SMF 103 Subtype 13 INPUT EXCEEDED error. TYPE102 33.250 SMF 102 IFCID 22 INPUT STATEMENT EXCEEDED. Major CORRECTIONS added in MXG 33.09, dated Sep 15, 2015: ASMTAPEE 33.207 ML-55 of ASMTAPEE/MXGTMNT REQUIRED for z/OS 2.2. IBM changes cause ABEND S0E0-28, must reassemble. TYPE7072 33.217 z13, SMT Mode, error: LPARCPUS=0 in PDB.TYPE70PR. TYPE110 33.198 CICS/TS 5.3 BETA, MNSEGCL=5, INPUT STATEMENT EXCEEDED IBM inserted new data. Datasets CICSRDS/RDFI/RDQU. TYPETMO2 33.210 More TMON/CICS Version 3 and Version 4 corrections. MONITASK in V3.3 fixed, MONISYST in V3.3 and 4.0. ASG APAR corrects two obscure fields in 4.0. TYPE7072 33.216 Support for APAR OA47042 WLM MOBILE Resources in RMF. TYPECDC 33.201 Support IBM INFOSPHERE CHANGE DATA CAPTURE CDC V10.2 TYPEAXWY 33.199 Support for AXWAY SMF record, INCOMPATIBLE, inserts. TYPE120 33.213 Support for WASODM Operational Decision Manager 8.7. TYPEMGCR 33.212 Support for MEGACRYPTION Version 6, INCOMPATIBLE. TYPE30 33.206 z/OS 2.2 Job Correlation SMF30COR input/kept. BUILDPDB 33.204 Variable IOTMNODD was never calculated in PDB.JOBS. TYPEXAM 33.202 Velocity ZVPS 5.4 XAMSYT had zero observations. TYPE113 33.197 Variable LPBUSY created in ASUM113 like TYPE113. TYPEDB2 33.205 DB2ACCTP variables QPACPKID/LOCN/ may be truncated. TYPEBVIR 33.196 TCVSIZE is now MGBYES, AVGCPUSE/DEFTH corrected. TYPE70 33.200 TYPE70xx datasets now have VARYed interval data kept. Major CORRECTIONS added in MXG 33.08, dated Aug 20, 2015:
TYPETMO2 33.195 TMON/CICS Version 4 was still wrong in 1st 33.08. Major enhancements added in FIRST MXG 33.08, dated Aug 18, 2015:
TYPE7072 33.186 z13 INCOMPATIBLE ERROR, SMT-MODE, if VARY CP online. The VARY put the new CP after the IIPs which broke MXG logic so the new engine was not seen, causing the CPU metrics to be wrong for all intervals after the VARY, requiring redesign of the MXG SMT logic. TYPETMO2 33.188 TMON/CICS Version 4.0, REQUIRED, MXG coding error. TYPESYNC 33.184 Support for SYNCSORT Release 1.4 (INCOMPAIBLE). NEW SUPPORT ITEMS: TYPExxxx 33.189 Support for z/OS 2.2 COMPATIBLE, but many additions. TYPEMAR 33.183 Support for MAR Hitachi Command Suite Mainframe VMAC115 33.180 Support for MQ Version 8 subtype 215 record TYPEBBMQ 33.175 New IHDRBBMQ "Infile Header Exit" for selection. ASMRMFV 33.182 New filters for RMF III ASI Filtering reading RMFVSAM CORRECTIONS: TYPE74 33.185 zEDC TYPE749 zero divide fixed, R749DFMT formatted. TYPE70PR 33.174 IFL Processor count corrected to number in LPAR. Yüklə 28,67 Mb. Dostları ilə paylaş:
|