* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
TYPE7072 33.179 TYPE70EN z13 SMT Mode, blank LPARNAME, SMF70MTTT fix. TYPE113 33.173 z13 SM1132SP incorrectly forced, should be 5000 MHz. OTHER ENHANCEMENTS: TYPE102 33.187 Dataset T102S106 zPARM variables added. TYPE30 33.185 zEDC variables labels now INFLATE/DEFLATE. RMFINTRV 33.181 Enhancement to ADD variables to be kept in RMFINTRV. JCLPDB9 33.178 JCL Example for BUILDPDB, ANALxxxx members revised. Major enhancements added in MXG 33.07, dated Jul 20, 2015:
Major enhancements added in MXG 33.07, dated Jul 17, 2015: TYPE74 33.155 TYPE74ST now has SCM variables, TYPE74MO is no more. TYPE78 33.156 Support for APAR OA44525, zHPF Extended Distance II. TYPE115 33.151 Support for MQ V8.0 MQCHIN, ERROR.VMAC115.OFFQCCT. TYPE116 33.151 Support for MQ V8.0 MQCHININ, ERROR.VMAC116.LENQWHS. TYPE119 33.144 Support for Type 119 new subtypes 94 and 95. TYPECZA 33.166 Support for Correlog z/OS Agent User SMF record. MXGLOGDO 33.162 "MXGLOG" option to send MXG Messages to MXGLOG. TYPE22 33.146 New TYPE22PB dataset created for Reconfigured PCIE. SMFSRCH 33.159 Support for compressed SMF in SMFSRCH LOOKFOR ANALID 33.159 Support for compressed SMF for DB2 Version/Subtype. ANALQBAT 33.147 Analysis of Batch Queue Times SMF30HQT/JQT/RQT/SQT. TYPEXAM 33.157 zVM XAM ERROR SYTCUP SEGMENT LENGTH corrected. TYPEBVIR 33.145 BVIR VTS Grid dataset BVIR33 wrong for second plus. TYPENDM 33.143 INPUT STATEMENT EXCEEDED NDM-CDI PT record. IMAC6ESS 33.158 Type 6 ESS zero len segment INPUT STATEMENT EXCEEDED. Major enhancements added in MXG 33.06, dated Jun 11, 2015: TYPERMFV 33.140 RMF III RCD records INCOMPATIBLY CHANGED for z13. TYPE7072 33.138 z13 in SMT Mode zIIP variables in TYPE70xx datasets, especially TYPE70EN, could be missing, or DUPLICATE RECORD message could be printed. REQUIRED FOR SMT. The MXG SMT support has come in several iterations as new sequences of data exposed untested logic but this appears to finally resolve the one-to-many merge. If you testing SMT on z13, please email MXG Support with subject: SMT UPDATES so we can inform you if there are any further required changes for SMT mode. Aug 17, 2015: MXG 33.08 is NOW required for SMT mode. See Change 33.186. TYPE30 33.132 Support for zEDC metrics in TYPE30 is now correct. ANAL9914 33.139 z13 Processor Topology Report from SMF TYPE9914 data. SMFSRCH 33.131 SMFSRCH enhancements, ANALID, LOOKFOR list, AND/OR. TYPEAA 33.137 Support for Compuware ABEND-AID USER SMF Record. TYPECIMS 33.136 Support for MainView for IMS 5.2 (a/k/a IMF). TYPEOSEM 33.133 ZOSEM User SMF - INPUT STATEMENT EXCEEDED error. TYPETMS5 33.129 Support for TMS new TRTCH values for TS1140. ASUM113 33.130 Missing values in SMF70xx merged into PDB.ASUM113. ANALDB2R 33.134 Number reports mis-reported,ANALID added, headings. Major enhancements added in MXG 33.05, dated May 19, 2015:
TYPE74 33.127 zEDC TYPE749 dataset was finally revised correctly. Aug 17,2015 added: MXG 33.08 required for SMT mode. Major enhancements added in MXG 33.05, dated May 12, 2015: TYPE7072 33.121 z13 SMT-mode TYPE70/TYPE70PR data is WRONG 33.03-04. ONLY SMT-mode type 70 records were wrong. TYPETANZ 33.123 Support for Tandem ZMS Style records. TYPEZCOS 33.116 Support for ZCOST AutoSoftCapping Version V3.0.00 SMFSRCH 33.117 SMFSRCH corrections, TYPE30_D now populated. TYPEBBMQ 33.115 Mainview for Mq BBMQBUFF variables corrected. TYPECIMS 33.114 IMF/CIMS variable CPUZIPTM was not KEPT in CIMSTRAN. TYPE102 33.113 Some T102S106 DB2 zPARM values were misaligned/wrong. TYPE120 33.120 New IHDR120 header exit created for TYPE120 tailoring IMACICMX 33.119 The optional IMACICMX for length=384 had missing END. Major enhancements added in MXG 33.04, dated Apr 29, 2015:
Note: IBM Changed CICS 5.3 Default to STGPROT=YES Note: MXG 33.08-plus is required. Change 33.192. TYPETMO2 33.099 TMON/CICS V3.4, MXG 32.13-33.03, TASCPUTM WRONG. TYPEBBMQ 33.090 Support for BBMQ PTF BLL2458/BPL2459 (INCOMPAT) TYPE42 33.108 Support for APARs OA45944,OA45897 new SMF 42 metrics. TYPE74 33.087 Support for RMF 74 Subtype 9 zEDC Accelerator. TYPESYNC 33.102A Support for SYNCSORT Release 2.1 (INCOMPATIBLE). TYPEQACS 33.101 Support for iSeries 7.2 (COMPATIBLE, new LRECLs). TYPEXAM 33.086 Support for Velocity Software zVPS XAM Version 5.4. TYPENMON 33.104 Support for NMON CPUnr with three digits. TYPE110 33.106 CICSEXCE variable EXCMTYPE decodes Exception type. UTILCVRT 33.105 Alternate table needed for no TRANSCODE PROC CPORT. ASMRMFV 33.100 Protect invalid ASI table index in UWD, 0C4 ABEND. TYPE7072 33.096 z13 with SMT PROCVIEW=CORE, SMT-NUM not kept. TYPENMON 33.092 Some NMON BBBPnnnn variables were mis-assigned. Major enhancements added in MXG 33.03, dated Mar 29, 2015:
i.e., for PROCVIEW CORE. FOR non-SMT, PROCVIEW CPU, the many changes were COMPATIBLY made. Aug 17,2015: See Change 33.186, MXG 33.08 IS NOW REQUIRED FOR SMT. For SMT PROCVIEW CORE Mode, MXG Change 33.046 in 33.02 updated the TYPE70 dataset, but this Change 33.071 in MXG 33.03 is required to update the new SMT metrics correctly in the TYPE70PR dataset, to get the CPUID, LCPUADDR, and CORE_ID from the four segments that don't have the same number of segments: OFFCPUD and SMF70COS have 20 for the 6 online CPs, 4 offline CPs, and 5 zIIPs with CPU_NUM=2, while SMF70BDN/LPARCPUX has only 18 segments (with the CORE_NUM needed to look-up the LCPUADDR), and there are only 14 Core_ID values. This was a complex update to a CRITICAL MXG MEMBER, with 500+ lines of code inserted lines into the 27,000 lines. The SMT Mode data has been validated with RMF records, with a wide range of LPAR configurations. When in SMT mode, please examine the new data carefully and contact support@mxg.com if you have questions. Note: If you read the changed SMT mode RMF 70s with an old MXG, RMFINTRV may have NEGATIVE CPUOVHTM values and the %PCTCPUBY values may be over 100%. TYPE99 33.053 Support for z13 updates to type 99 subtype 14. TYPE113 33.052 z13 Support for HIS SMF 113, many new equations. UTILEXCL 33.049 New reports, trans without dictionary, READTIME. VMXGINIT 33.062 %LET MXGDEBUG=FULL; shows OPTIONS, enables diags. TYPEDOL 33.060 DCOLLECT Cluster/Multi-VOL now have Class variables. TYPE102 33.067 DB2 Trace IFCID=220 misaligned, ILLEGAL ARGUMENT. TYPE105 33.061 GDPS SMF 105 INPUT STATEMENT EXCEED if no XVMX seg. ANALDB2R 33.069 SAS 9.3 does not have dictionary for DESTINATIONS. TYPEDB2 33.068 Variable Q8STCCPU not kept after Change 30.133. TYPETHAO 33.059 Support for Thales Security Resource Mgr RF1100. FTPING 33.056 OPTIONS OBS=0 fails read with ftp access method. ANALHSM 33.050 Graphics part had a NOT SORTED condition. TYPETPMX 33.070 TOKENID INCLAI, three $LIST_L and $RESTAR added. Many 33.078 All %MACROs from SASAUTOS are replaced by %SYSFUNC() Major enhancement added in MXG 33.02, dated Feb 27, 2015: Many 33.046 Support z/OS on z13 RMF/SMF APARs for z/OS 2.1+ MXG 33.01 CHANGES noted one z13 site had NEGATIVE CPUOVHTM, but that was ONLY IF z/OS on z13 is in MULTI-THREADING MODE. MXG was unaware of IBM's restructuring the RMF type 70 SMF record's calculation of CPU BUSY time for the new MT mode, but this MAJOR CHANGE restructured TYPE70 processing in MXG to order by CORE_ID and CPU_NUM rather than CPUID/LCPUADDR. If you have ANY non-MXG programs that read RMF 70s to get the CPU BUSY time, they MUST BE REWRITTEN for MT Mode records. A Technical Newsletter note on Multi_Threading is planned; this original note then stated an initial opinion of mine: "although relatively few sites have workloads that will be able to exploit that architecture, which can increase thruput but elongate individual tasks elapsed time", but I've changed my opinion about "relatively few sites": ANY SITE with zIIPs or IFLs are VERY LIKELY to find SMT to be a benefit. Major enhancement added in MXG 33.01, dated Feb 23, 2015: Many 33.023 Support z/OS on z13 RMF/SMF APARs (z/OS: COMPATIBLE) However: One site's z13 stress test shows TYPE70 CPU time MUCH LESS than TYPE72 Service Class CPU time (which matches 30s) for many intervals, but valid data before and after the test, causing NEGATIVE CPUOVHTM messages on the log and RMFINTRV observations will have negative CPUOVHTM (uncaptured CPU). NOTE: THIS ERROR WAS CORRECTED IN MXG 33.02, SEE ABOVE NOTE.
TYPEMWLX 33.037 Support for HP MeasureWare for Linux - VMAC30 33.005 Support for APAR OA45767 adds zEDC statistics. TYPEBBMQ 33.030 Support for BMC Mainview for MQ 5.2 (REQUIRED) TYPENTMU 33.028 Support for EDS User SMF Record from NETMENU program. TYPEXPTR 33.040 Support for SystemWare XPTR 5.2 subtype 140, ex-st-40 SMFSRCH 33.041 SMFSRCH redesigned to read the SMFOUT with UTILBLDP. ASUM70PR 33.032 New SMF70WTI/WTS/WTU added to ASUM70LP/ASUMCELP MOBWRKSU 33.039 Summarization of Mobile Work CSV file combines split. TYPEDB2 33.025 QBSTBPIN, Buffer Pool I/O Intensity, added DB2STATB. RMFINTRV 33.024 ANY work in service class SYSOTHER, new log messages. ASMRMFV 33.021 ASMRMFV skips RCD if no Reporting Classes defined. TYPEQACS 33.020 iSeries change in record length can force USER ABEND. TYPE60 33.038 Type 60 with no VVR INPUT STATEMENT EXCEEDED again. TYPE80A 33.036 RACF SMF 80 record, TOKxxxxx fields increased length TYPEIMS 33.034 Variables SYSABEND,USRABEND decoded in IMS56FA. TYPEVMXA 33.043 zVM VXUSEACT/VXUSEINT NOT SORTED ERROR. UTILBLDP 33.042 Using INCLAFTR=BUIL3005 for JES3 PDB.TYPE25 not found 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 TS1M3 (9.4M3) printed as "SAS 9.4 (TS1M3)" or was "SAS 9.4 (TS04.01M2P07232014)" for "SAS 9.4 (TS1M2)" (on SASLOG, if OPTION VERSIONLONG enabled), for SAS 9.4 Maintenance Level M3 and m2.
SAS Version 9.4 M0, M1, M2, and M3 or SAS Version 9.2 M1 and M2. SAS V9.4 M2 Is RECOMMENDED. SAS 9.4 M2 is at LEVEL A SAS Support SAS V9.4 M1 and M0 had no errors and are at LEVEL A SAS Support SAS V9.3 SAS 9.3 TS1M2 was RECOMMENDED. SAS 9.3 TS1M1 works. 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 ok. 9.2 is LEVEL B Support from SAS, as of Sep 30, 2013. SAS V9.1.3 must be at Service Pack 4. Additionally, on z/OS 1.10 only, 9.1.3 requires SAS Hot Fix for SN-35332. 9.1.3 is support level C by SAS Institute, Sep 30, 2013. SAS V9.1.3 is NOT supported by SAS on Windows SEVEN. SAS V8.2 IS 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 MXGSAS93 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.1.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.
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 33.09 is REQUIRED (PCTCPUBY WRONG!), to read the SMT-format RMF records (which are written if you have zIIP engines AND have 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 Yüklə 28,67 Mb. Dostları ilə paylaş:
|