* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
ASUM70PR 35.150 Option %LET CECONLY=YES creates ASUMCEC/ASUMCELP only ASUM70PR 35.144 MXGERROR:MISSING TYPE 70 RECORDS message. TYPE113 35.141 SMF 113 Formula for RNI updated for z13. IMACINIT 35.128 Note: OPTIONS NOCAPSOUT recommended for ODS users. ASMRMFV 35.135 RMF III Enhancements, Filtering. UTILBLDP 35.143 Options SUPPRESS enhanced, NEVER corrected.
TYPEDB2 35.111 DB2 12.1 INVALID QLAC, CONTINUOUS DELIVERY CAUSED. THIS IS IMPORTANT: LOOK FOR INVALID QLAC ERROR ON YOUR SAS LOG - OBSERVATIONS ARE NOT OUTPUT. THE FIELDS WERE INSERTED BY APAR PI74456. TYPE7072 35.113 35.04 only. TYPE79 SHARE weights wrong, ASUMCELP ok. VMXGPRNT 35.120 WPS only, MXG 35.04 Only, Blank Label ERROR. VMXGFIND 35.117 Multiple input PDBs were read, only one was output. JCLTEST9 35.116 35.04 only. //MVJEIN DD in wrong step. VGETSORT 35.112 35.04 only. ERROR Truncated SORTBY (name GT 32). TYPE129 35.109 Variables SM1209EX/EY/EZ/FA were dropped. ANALID 35.108 ANALID report TITLE for BUILDPDB can be tailored. New Products Support TYPEIAM 35.107 Support for IAM Version 9.0. Enhancements TYPE110 35.105 CICS duration fields are now formatted TIME16.6. ==Major CHANGES added in MXG 35.04, dated May 1, 2017 thru 35.104. Error Corrections TYPE7072 35.093 MXG 35.03 only. PLATBUSY/PCTOF HDW TYPE70/RMFINTRV. TYPEVMXA 35.079 z/VM 6.3 SMT in VXSYTPRP, VXAPLSO0 corrections. TYPEXAM 35.074 Velocity XAM SYTCPU invalid errors at vendor. TYPEDB2 35.081 DB2ACCTP, truncated QPACLOCN/COLN/PKID/ASCH/AANM New Products Support TYPEMVJE 35.094 Support for BMC Mainview for Java Environment. TYPEVMXA 35.092 Updated support for z/VM 6.4 (INCOMPAT, SYTLCK). Enhancements ANALFTP 35.087 New ANALFTP analysis provided five new reports. ANALCNCR 35.091 New example count/plot concurrent TELNET sessions. IHDRNDM 35.089 New NDM-CDI IHDRNDM exit for NDMRTYPE selection. BUILDPDB 35.088 Running MXG on ASCII, free SMF alloc at read end. TYPEOPSS 35.090 Support for CA's OPSS Product User SMF Record.
Not serious, but easily corrected with this update. ==Major CHANGES added in MXG 35.03, dated Mar 22, 2017 thru 35.069. Significant Correction/Documentation TYPE7072 35.064 SMT Mode corrections, "Inflated" CPUZIPTM in MT=2 ONLY IMPACTS 72 and 30 - TYPE 70 DATA JUST FINE! New Products Support TYPE110 35.069 Support for CICS/TS 5.4 BETA 11 CICSTRAN new vars. TYPESVIE 35.059 Support for CA SYSVIEW for IMS 14, missing values. TYPEIMS 35.058 Support for IMS LOG 67D0 DIAGNOSTIC DC Log Record. TYPEMVIP 35.055 Support for Mainview for IP PTF BPN2331 adds flag. TYPE120 35.051 Support for Liberty 17.0.0.1 SMF 120 ST 12 new data. TYPEOPC 35.048 Support for IWS/TWS/OPC Version 9.3 ST 66 was ST 23. TYPE102 35.047 Support for IFCID 316 ACCESS CONTROL AUTH EXIT PARMS. TYPE102 35.046 Support for IFCID 125 Truncated fields. TYPEVMXA 35.040 Support for Velocity ZWRITE z/VM MONWRITE records. TYPEXAM 35.063 Support for XAMSYS wrong length, XMTCPSYS NAMENODE. TYPEMVCI 35.062 Support for Mainview CICS CMRDETL file VER 6700. TYPE30 35.066 APAR OA59593 adds INELIGHONOR flag to SMF 30s. Enhancements TYPEDCOL 35.064A Multi-Volume DCOLDSET fields retained & populated. ASUMCELP 35.061 Variable SMT_NUM added to PDB.ASUMCELP with MT mode. TYPE120 35.060 SMF 120 ST 11 TYP120BL CP and zIIP variables added. GRAFCAPS 35.042 Example report of Resource Group CPU use and CAPPING. ASUM70PR 35.061 Enhancement adds SMT_NUM to PDB.ASUMCELP dataset. TYPE120 35.060 Enhancement adds TOTAL/CP ONLY/ZIP CPU to TYP120BL. ASMRMFV 35.054 RMF Monitor III Enhancement for OPD data filtering. ASUM70PR 35.050 Error message if PDB.ASUMCELP does not have all 70s. Corrections VMXGSUM 35.056 Correction for KEEPMNTH= (very rarely used) option. TYPERMFV 35.044 ZRBCP SMT vars missing, new CPC_CECNAME variable. TYPE1415 35.040A IBM APAR OA51325 corrects missing UCB segment. CICINTRV 35.038 MXG correction for ITRM to NOT delete CICINTRV ==Major CHANGES added in MXG 35.02, dated Feb 10, 2017 thru 35.035.
VMXGSUM 35.022 COMPBL too few arg, VARIABLE QWACBSC ALREADY... Rare and obscure, only three reports, but nasty if encountered deep in your daily run, so please "drop in" 35.02, which is a very good LEVEL SET. VMXGSUM 35.020 MXG 35.01. Ignore MXGWARN VMXGSUM BACKLEVEL msg. UTILEXCL 35.023 MXG 35.01.Old Dictionary Records were not used. TYPEVMXA 35.025 Using _VMINPUT. z/VM variable VMDUSER was 1 byte. Variables corrected: TYPEDB2 35.027 DB2STATS QISTxxxx Storage multiplied by 4K vs 1K. TYPE78 35.021 TYPE78PA variables R782LSMO/GMFO/GFRR are wrong. GRAFWRKX 35.018 WARNING but ZIPTM, IFATM, and ZIETM were not plotted. TYPE120 35.024 Subtype 9 variables SMF1209EV,FI,EW no longer kept. VMXGALOC 35.033 Month begin/logic revised, MNTHKEEP zero protected TYPE42 35.031 Variable S42DSIOS added to TYPE42DS. TYPEDB2 35.030 DB2STAT4 _REAL variables way too large. New Products Support TYPE102 35.017 New DB2 ZPARMS added to T102S106 dataset. TYPE117 35.015 Support for SMF 117 GTZ record. TYPE125 35.015 Support for SMF 125 GTZ record, untested. TYPE80A 35.029 RACFTYPE=6 seg increased in length, message, no fail. TYPERMFV 35.028 New RMF III ZRBENC "long names" now input and kept. IMACDBNZ 35.027 Support for DB2ACCT NETEZZA Q8AC "Accumu" variables. TYPEBBMQ 35.034 Support for BBMQ BMC Utility BBM9MD73 restructure. Enhancements UTILRMFI 35.026 Enhanced reporting if SRVCVLASS=SYSOTHER detected. TYPETPX 35.035 Protection for invalid TPX subtype 7 record.
back in MXG 34.01 in Feb, 2016, but only reported now by only two sites. THERE IS NO ERROR MESSAGE ON THE LOG. PROC FREQ DATA=PDB.RMFINTRV; TABLES SMF70GNM; will show if you are exposed. %INCLUDE SOURCLIB(RMFINTRV); with //PDB DD DISP=OLD with this Change will rebuild PDB.RMFINTRV correctly for each mis-built PDB data library.
UTILEXCL 35.004 ERROR PDB.CICSDICT not FOUND - USE THIS UTILEXCL. TYPE115 35.011 For local time zones with +GMT, GMT115TM wrong. TYPE120 35.007 Liberty SMF 120 st 12 SM120CCC/CCD Year 2027. TYPEPOEX 35.002 INVALID SMF Records caused STOPOVER ABEND. TYPEOSEM 35.010 OSEM User SMF INPUT EXCEEDED, invalid, circumvented. New Products Support TYPE71 35.009 Support for APAR OA48913 with 2GB Memory Frames Enhancements TYPERMFV 35.005 Dataset ZRBLCP obs created for ONLINE LCPUADDRs. Please read CHANGESS for the complete list of major enhancements.
current MXG Technical Notes. All of these enhancements are described in the Change Log, below.
The current version nomenclature is SAS 9.4 TS1M5 (9.4M5), "M5", or "SAS 9.4 (TS04.01M5P09132017)" if the OPTION VERSIONLONG is enabled.
NOERRORSTOP option to protect all MXG PROC SQLs from the M5 defect that will be corrected in SAS Note 61672 defect. See Change 35.308 for more details on using NOERRORSTOP for your own PROC SQLs.
using SAS Version 9.4 M0-M4 or SAS Version 9.3 M0-M2. SAS V9.4 (ALL) and SAS V9.3 (ALL) are at LEVEL A SAS Support. SAS V9.3 SAS 9.3 TS1M2 was RECOMMENDED. SAS 9.3 TS1M1 works ok. But SAS 9.3 at TS1M0, the HOT FIX for SAS Note SN-43828, see CHANGE 29.169, IS REQUIRED: The %MACRO compiler error is in processing %LET statements. While only two MXG members failed repeatedly in MXG QA tests on z/OS, there were random %LET errors in ASCII QA tests, so ANY use of %LET statement on ANY platform are vulnerable to this error, as the %MACRO compiler is SAS portable code, used on all platforms. So this is NOT just an MXG error, but impacts ALL SAS programs. SAS9.3 is LEVEL A support from SAS. SAS V9.2 Was recommended, prior to 9.3, and was error-free with MXG 26.03 SAS Hot Fix for SAS Note 37166 is required to use a VIEW with the MXG EXITCICS/CICSFIUE CICS/DB2 Decompression Infile Exit. but SAS V9.2 does execute on that platform. 9.2 is LEVEL B Support from SAS, as of Sep 30, 2013. SAS V9.1.3 on z/OS 1.10 requires SAS Hot Fix for SN-35332 and is at Support level C by SAS Institute, Sep 30, 2013. SAS V9.1.3 is NOT supported by SAS on Windows SEVEN. SAS V8.2 SUPPORT LEVEL C BY SAS INSTITUTE; NOT ALL OF MXG WORKS! with SAS 8.2. SAS 8.2 is Level C Support from SAS as of Dec 31, 2011. JCL in MXGSAS94 or MXGSAS93 can be used, or MXGNAMES can be used *************************************************************** As documented in Change 27.356, for SAS V9.2 or later): The standard SAS JCL Procedure can be used for MXG with SAS V9.2+ // EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)' //MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR or you can continue to use the MXGSAS94 JCL Procedure example. ***************************************************************
SAS Versions on all supported platforms Unrelated to the above SAS Note/Hot Fix, ODS users will want to use MXG 29.06+, because SAS V9.3 did expose incompatibilities in MXG code for ODS reporting, that were fixed in MXG Version 29.06. See Changes 29.159 and 29.169. And, only for z/OS 1.10 with SAS V9.1.3 with ANY version of MXG, the SAS Hot Fix for SN-35332 is REQUIRED (to be completely safe). Without this Hot Fix, "LIBREF XXXXXXXX IS NOT ASSIGNED" errors can occur even though //XXXXXXXX DD is a valid SAS Data Library. This error ONLY occurs with z/OS 1.10 and SAS V9.1.3; it does NOT occur with SAS V9.2, nor with z/OS 1.9. It can be circumvented by adding a LIBNAME statement that specifies the ENGINE name. See the Technical Note in Newsletters for SN-35332. Note that SAS V9.1.3 is now at "Level B" Support from SAS.
"Level C" support from SAS Institute, and there are known errors in V8.2 that are only fixed in SAS V9. I no longer QA with V8.2; While many MXG programs (accidentally) will still execute under V8.2, I cannot guarantee that all of MXG executes error free. PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS! If you are absolutely stuck on V8, you need to copy MXG member V8GETOBS into USERID.SOURCLIB and rename to VGETOBS. MXG Software has not executed under SAS V6 in many years. The "PDB" libraries (i.e., SAS data libraries) must be created by SAS V8 or later, but any of those data libraries can be read or updated by the SAS Versions that MXG Supports, above. For SAS Version V9.3: SAS 93 TS1M1 is RECOMMENDED; for TS1M0, SAS Hot Fix in SAS Note SN43828 is REQUIRED. See text of Change 29.159. With SAS 93 TS1M1, (or TS1M0 with that Hot Fix) MXG Versions 26.03 or later execute under SAS V9.3 on all platforms. SAS Data Libraries created by SAS V8.2, V9.1.3, V9.2, V9.3 and SAS V9.4 are interchangeable and can be read/written by any of those versions, provided they are on the same platform. BUT: on ASCII, the 32-bit and 64-bit SAS versions are NOT the same "platform" and attempting to read/use the FORMAT catalog created on one of those "platforms" on the other "platform" will error out to remind you of that difference! SAS V9.4 did change some V9.3 ODS processing defaults and syntax that might cause errors with MXG 29.05 or earlier; MXG 29.06, Change 29.160 documents the major revisions made in MXG to fully support ODS, and MXG 29.06 is STRONGLY recommended for ODS with SAS V9.3 or SAS V9.4. For (Archaic) SAS Version V9.2 (TS1M0): Big Picture: SAS Version V9.2 is COMPATIBLE with MXG Software. On z/OS, SAS changed the DSNAMES for some of the SAS libraries, so you do need to use the new MXGSAS92 JCL Procedure for MXG, but it still uses the CONFIGV9 configuration file.
However, NEW, and documented in Change 27.356, with SAS V9.2+: The standard SAS JCL Procedure can be used for MXG: // EXEC SAS,CONFIG='MXG.SOURCLIB(CONFIMXG)' //MXGNAMES DD DSN=MXG.USERID.SOURCLIB(MXGNAMES),DISP=SHR instead of using the MXGSAS92 JCL Procedure example. ****************************************************************
and V9.4. "PDBs" can be read/written interchangeably between these SAS versions.
and with NO ERRORS reported. Pre-MXG 26.03, SAS Hot Fix F9BA07 was required to suppress a new SAS V9.2 WARNING, that on z/OS, set CC=4 (condition/return code). That warning is harmless (to MXG code) and all MXG created SAS datasets were correct, even with that warning. The ONLY exposure was ONLY on z/OS, and ONLY if condition code tests are used in your MXG jobstreams. SAS Version 9.2 requires z/OS 1.7 or later, both officially as documented by SAS Institute, and actually as V9.2 fails with 0C4 under z/OS 1.4.
not support long length character variables, it can't be used. SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED. For (back-level!) SAS V9.1 or V9.1.2 on z/OS: SN-013514 is REQUIRED to be able to read datasets that were created by V6SEQ (tape) engine. SN-012437 is REQUIRED to prevent creation of corrupt/unreadable datasets with tape engines V7SEQ, V8SEQ, or V9SEQ. Both fixes ARE included in SAS V9.1.3, but V9.1 or 9.1.2 is NOT SAFE without those two hot fixes, and if you do NOT have those two fixes on 9.1 or 9.1.2, you MUST set V6SEQ in CONFIGV9. With MXG 23.02 or later, V9SEQ is the default sequential engine specified in CONFIGV9, but if you are back at SAS V9.1 or V9.1.2 you MUST install the two hot fixes listed above.
as an absolute minimum level when that SAS Version was last supported by MXG Software. PLEASE INSTALL SAS V9.x ASAP.
V9SEQ was fixed in V9.1.3; it has been default in CONFIGV9. V8SEQ was always safe under SAS V8.2, but it wasted CPU time by always compressing when writing in tape format. V6SEQ, if used under V9.1.2, requires SN-013514, but V6SEQ should no longer be used, as it does not support long length variables.
Eight (64-bit) on 64-bit hardware, and sometimes on Centos 6.4, but MXG users execute MXG on MANY (ALL??) SAS platforms, including AIX, Linux, and other 'nix' variants, on many different hardware platforms, and since they all work we don't need to list them. If SAS executes so does MXG. Prior QA tests have been run with all SAS releases available at that time on Linux RH8 on Intel, on Solaris v2.8 on a Model V880, and on HP-UX v11.11 model rp5470, confirming full compatibility.
platform without errors! Each new MXG version is also tested with the SAS ITSV/ITRM product by the ITRM developers. III. WPS Version requirement information: WPS Version 3.02 (03.02.03.00.016221) is required Change 34.266. and other errors with 3.00 or 3.01 have been corrected in the current WPS version. WPS Version 3.01.1 maintenance level 731 required for PDB to tape WPS Version 3.01 (also shows 3.1.1) is required for AUTOEZOS. WPS Version 3.01 is required for MOBILWRK, PICTURE fails in 2.5. WPS Version 3.01 executed MXG 32.03 BUILDPDB with no errors. WPS Version 3.0 requires MXG 31.09 (see Change 31.251). WPS Version 2.4 required MXG 27.09 (see Change 27.239). WPS Version 2.3.5 required MXG 27.05. See NEWSLETTERS for WPS Support Statement. WPS prints this message ERROR: COULD NOT CREATE DATA SET "PDB.ID" when the LIBNAME PDB does not exist; there would also have been a prior log message NOTE: Library PDB does not exist as the clue. IV. MXG Version Required for Hardware, Operating System Release, etc. MXG is usually NOT sensitive to z/OS Hardware changes, but: The z/EC12 with 85+ engines required MXG 30.07. Support for 255 engines was added in MXG 31.04. The z/13 with 61+ LPARs requires MXG 32.05 IF NON-SMT MODE.
INCOMPATIBLY CHANGED, and MXG 34.03 is REQUIRED (PCTCPUBY WRONG!), to read the SMT-format RMF records (which are written if you have zIIP engines AND have enabled the new PROCVIEW CORE option for Multi-Threading, even if only one thread is enabled).
new metrics. For z/VM, MXG REQUIRES MXG 33.02 to support the z/13 changes. Availability dates for the IBM products and MXG version required for error-free processing of that product's data records:
Availability MXG Version Product Name Date Required
MVS/ESA 4.2 Mar 29, 1991 9.9 MVS/ESA 4.2.2 Aug 15, 1991 9.9 MVS/ESA 4.3 Mar 23, 1993 10.10 MVS/ESA 5.1.0 - compatibility Jun 24, 1994 12.02 MVS/ESA 5.1.0 - Goal Mode May 3, 1995 13.01 MVS/ESA 5.2.0 Jun 15, 1995 13.05 MVS/ESA 5.2.2 Oct 19, 1995 13.09 OS/390 1.1.0 Feb 22, 1996 14.01 OS/390 1.2.0 Sep 30, 1996 14.05 OS/390 1.3.0 Compatibility Mode Mar 28, 1997 14.14 OS/390 1.3.0 WLM Goal Mode Mar 28, 1997 15.02 OS/390 2.4.0 Sep 28, 1997 15.06 OS/390 2.5.0 Feb 24, 1998 15.06 OS/390 2.6.0 Sep 24, 1998 16.04 OS/390 2.7.0 Mar 26, 1999 16.09 OS/390 2.7.0 APAR OW41318 Mar 31, 2000 18.03 OS/390 2.8.0 Aug 24, 1999 16.09 OS/390 2.8.0 FICON/SHARK Aug 24, 1999 17.08 OS/390 2.8.0 APAR OW41317 Mar 31, 2000 18.03 OS/390 2.9.0 Mar 31, 2000 18.03 OS/390 2.10.0 Sep 15, 2000 18.06 OS/390 PAV Oct 24, 2000 18.09 z/OS 1.1 Mar 30, 2001 18.11 z/OS 1.1 on 2064s Mar 30, 2001 19.01 z/OS 1.1 with correct MSU Mar 30, 2001 19.02 z/OS 1.2 Oct 31, 2001 19.04 z/OS 1.1,1.2 APARs to 78 Oct 31, 2001 19.05 z/OS 1.2+ APAR OW52227 Apr 26, 2002 20.02 z/OS 1.3+ APAR OW52227 Apr 26, 2002 20.02 z/OS 1.2 JESNR Z2 MODE Apr 26, 2002 20.03 z/OS 1.3 JESNR Z2 MODE Apr 26, 2002 20.03 z/OS 1.4 Tolerate Sep 27, 2002 20.03 z/OS 1.4 Support Sep 27, 2002 20.06 z/OS 1.4 Over 16 CPUs/LPARs May 29, 2003 21.02 z/OS 1.4 DFSMS/rmm, RACF Aug 29, 2003 21.04 z/OS 1.5 Mar 31, 2004 21.21 z/OS IRD ASUM70PR/ASUMCEC Sep 22, 2003 *24.10 z/OS IRD TYPE70PR Mar 11, 2004 *24.10 z/OS IRD TYPE70,RMFINTRV Mar 22, 2002 *24.10 z/OS 1.6 - No IFAs Sep 30, 2004 *22.09 z/OS 1.6 - With IFAs Sep 30, 2004 *22.11 z/OS 1.7 (COMPATIBLE CHANGES) Sep 30, 2005 *24.10 z/OS 1.7 (SPLIT70 CORRECTION) Sep 30, 2005 *24.10 z/OS IFA data in RMF 79s Sep 30, 2005 23.10 z/OS 1.8 - ASMTAPEE assembly Sep 30, 2005 *25.03 z/OS 1.8 - SMF 119 INCOMPAT Sep 30, 2005 *25.06 z/OS More than 32 LPARs Jan 30, 2006 *24.24 z/OS SPLIT RMF 70 records Jan 30, 2006 *24.24 z/OS Dupe SYSTEMs in a SYSPLEX Jan 30, 2006 *24.02 z/OS IRD errors corrected May 15, 2006 24.03 z/OS ASUMCEC errors corrected May 15, 2006 *24.24 z/OS ASUM70LP errors corrected Jun 13, 2006 *24.24 z/OS zIIP Processor Support Jun 22, 2006 *24.24 z/OS Dedicated zIIP Support Mar 8, 2008 *26.01 z/OS Dedicated zAAP Support Mar 8, 2008 26.01 z/OS 1.8 (COMPATIBLE CHANGES) Sep 20, 2006 *24.24 z/OS 1.9 (INCOMPAT, 54 CPs) Sep 27, 2007 25.10 z/OS 1.9 MXGTMNT at ML-39 reASM Sep 27, 2007 25.10 z/OS new z10 variables Mar 5, 2008 26.01 z/OS 1.8 With HiperDispatch Sep 15, 2008 *26.10 z/OS 1.9 With HiperDispatch Sep 15, 2008 *26.10 z/OS 1.10 (INCOMPAT, MXG code) Sep 15, 2008 26.07 z/OS 1.10 With HiperDispatch Sep 15, 2008 *26.10 z/OS 1.10 RMF III, SMF 119 Jul 20, 2009 27.05 z/OS 1.11 Sep 2, 2009 27.08 z/OS 1.11 New 30 variables Apr 14, 2010 *28.02 z/OS 1.12 Aug 17, 2010 *28.05 z/OS 1.12 SMF 85 Subtype 79 Aug 17, 2010 *29.03 z/OS 1.12 VMGUEST option Aug 17, 2010 *29.06 z/OS 1.13 Sep 30, 2011 29.03 z/OS 1.13 - MXGTMNT only Dec 15, 2011 29.08 z/OS 1.13 SMF 119 ST 6 INCOMPAT Feb 7, 2012 30.01 z/OS 2.1 - Most Records support Jul 23, 2013 30.05 z/OS 2.1 - ID=0 ERROR MESSAGE Jul 23, 2013 31.07 z/OS 2.1 - ID=85 INCOMPAT Jul 23, 2013 32.03 z/OS 2.1 - ID=70 SMF70CPA Jul 23, 2013 32.03 z/OS 2.1 - INPUT STATEMENT EXCEEDED ERROR SMF 74 33.10 z/OS 2.2 COMPATIBLE CH 33.189 Aug 19, 2015 33.08 z/OS 2.2 MXGTMNT ABEND S0E0-28 Sep 15, 2015 33.09 REQUIRES ASMTAPE ML-55 Sep 15, 2015 33.09 z/OS 2.2 OAM SMF 85 ABEND 33.067 Apr 5, 2016 34.02 z/OS 2.2 SPLIT 73, ABEND 33.068 Apr 5, 2016 34.02 z/OS 2.2 JES2 8-char JOBCLASS Oct 7, 2016 34.07 z/OS 2.2 NEW SMF 124 IOS Spvr Oct 7, 2016 34.07 z/OS 2.3 Many new variables Sep 24, 2017 35.166 35.09* z/OS 2.3 RMF III Support Sep 24, 2017 35.190 35.09* z/OS 2.3 type 2 st 2 STOPOVER Sep 24, 2017 35.190 35.09* z/OS 2.3 type 90 st 38 STOPOVER Sep 24, 2017 35.199 35.09* z990 CPUs - CPUTYPE '2084'x Aug 25, 2003 21.04 z890 CPUs - CPUTYPE '2086'x Jun 24, 2004 22.07 z9 CPUs - CPUTYPE '2094'x Jul 20, 2005 *24.24 z9EC CPUs - CPUTYPE '2094'x: with 64-bit z/OS - no change required *24.24 with 32-bit z/OS only: Aug 26, 2006 24.06 z9BC CPUs - CPUTYPE '2096'x: with 64-bit z/OS - no change required 24.01 with 32-bit z/OS only: Jul 27, 2006 *24.24 z10 CPUs - CPUTYPE '2097'x Dec 7, 2008 25.11 z10 HiperDispatch/Parked Time Mar 3, 2008 *26.10 Yüklə 28,67 Mb. Dostları ilə paylaş:
|