* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
the 39-character format. Some IPV6 addresses did exist in variables with names ending in 6, but this new suite of variable's names end with IPV6. -Only these SMF 119 subtypes have been validated with data 1,2,3,5,6,7,10,20,21,70 and 72. -The subtype 2 record has an old note suggesting that Because this information duplicates all information contained in the TCP connection initiation (subtype 1) record, only collect the TCP connection termination record (subtype 2). -Jul 13: Variable UCLIPV6 was not kept until now; it was incorrectly spelled UCLIPB6 but could be added using _KT11910. Thanks to Karl Lasecki, Chemical Abstracts Service, USA. Thanks to Robert Hamilton, Chemical Abstracts Service, USA. Thanks to Jose Neto, Public Authority Civil Info, KUWAIT. Thanks to Arylon Brooks, Verizon Wireless, USA. Thanks to Scott S. Throckmorton, SPRINT, USA.
VMAC110 record was an MXG coding error exposed by the 156 bytes Jan 31, 2012 of new data that MXG had overlooked, causing the CICSJS dataset to have no observations created, and possible MXG skipping subsequent statistics segments in that record. New variables added to CICSJS dataset are: SJSGCPOL='GC*POLICY' SJSHEAPC='CURRENT*HEAP' SJSHEAPI='INITIAL*HEAP' SJSHEAPM='MAXIMUM*HEAP' SJSHEAPO='HEAP*OCCUPANCY' SJSHEAPP='PEAK*HEAP' SJSHVMCL='JVM*CREATION*DATETIME*LOCAL' SJSJVMCG='JVM*CREATION*DATETIME*GMT' SJSMAJCP='TOTAL*CPU IN*MAJOR*GC' SJSMAJFR='STORAGE*FREED*BY*MAJOR GC' SJSMAJGC='MAJOR*GC*COLLECTIONS' SJSMINCP='TOTAL*CPU IN*MINOR*GC' SJSMINFR='STORAGE*FREED*BY*MINOR GC' SJSMINGC='MINOR*GC*COLLECTIONS' SJSSYTHN='NR WAITING*ON*SYS*THREAD' SJSSYTHP='PEAK*WAITING*ON SYS*THREAD' SJSSYTHU='SYSTEM*THREAD*USE*COUNT' SJSSYTTM='TOTAL*WAIT*SYSTEM*THREAD' SJSSYTCN='WAITS ON*SYSTEM*THREAD' Thanks to Thomas H. Puddicombe, CSC, USA. Change 30.007 PMSTA01/PMSTA02 DB2 Statistics reports with INTERVAL=DATE ANALDB2R created multiple observations for each date because SHIFT VMXGDBSS was in the SUMBY= list in VMXGDBSS. That SUMBY argument Jan 29, 2012 is now a parameter with the current default values and uses the new parameter in ANALDB2R when required by the requested INTERVAL value. Also, errors in page numbering were cosmetic - no data was skipped - just page numbers were, due to an extra LINK in the heading routine. Thanks to Charles Savikas, DCF, State of Florida, USA.
VMACHSM -Dataset HSMDSRST: Jan 29, 2012 DSRFRBKT DSRFRBKF DSRFRRCT DSRFRRCF -Dataset HSMFSRBO: FSRF9ATT FSRSRCDV FSRRETDY FSRDLMD FSRDLUD FSRBDATE FSRDATRD FSRDLMD DSRDATED -Dataset HSMFSRST: FSRF9ATT FSRSRCDV FSRRETDY FSRDLMD FSRDLUD FSRBDATD FSRDATRD FSRDLMD -Dataset HSMVSRST: VSRFRBKT VSRFRBKF VSRFRRCT VSRFRRCF VSRDATED -Dataset HSMWWFSR: WFSRCONT WFSRDATR WFSRRMTS WFSRDATE WFSRDATS WFSRRSTS WFSRRETS WFSRXMNT WFSRHOST WFSRF9AT -These existing variables still contain julian date values DSRDATE FSRDLM FSRDLU FSRBDATE FSRDATR VSRDATE but new corresponding SAS DATE variables are now created with DATE9. format (prints 29JAN2012) for prettiness and so they can be directly subtracted for delta-days: DSRDATED FSRDLMD FSRDLUD FSRBDATD FSRDATRD VSRDATED These date variables were never kept; they are now kept and are now SAS Date Variables with DATE9. format. WFSRDATR WFSRDATS WFSRDATE Variable FSRDATE is always missing; it was sometimes missing and sometimes 0 (which printed 01JAN1960). -Datasets HSMFSRTP and HSMWWVOL had no observations so they have not been validated. Thanks to Randall R. Schlueter, First Data Corporation, USA. Change 30.005 If you used UTILBLDP to create your BUILDPDB code and UTILBLDP you used the MXGINCL parameter to include members that BLDSMPDB were not in the default list, they were ignored. Now Jan 29, 2012 they will not be ignored. They can alternatively be in the INCLAFTR= parameter (where they wouldn't have been ignored). When BLDSMPDB used the output of UTILBLDP as as the source of the BUILDPDB code, it didn't use the AUTOINC= parameter, but now it does. With this change members can be included after the BUILDPDB step from one one of these three parameters: UTILBLDP - MXGINCL or INCLAFTR BLDSMPDB - AUTOINC But, if the same member appears in more than one it will be executed more than once. -MXGINCL should primarily be used to remove these members that are automatically included: ASUMUOW ASUMCICX ASUM70PR ASUMCACH ASUMTAPE ASUMTMNT ASUMTALO ASUMDBAA ASUMDBSS One or more can be removed if you choose. The same is true of the AUTOINC parameter in BLDSMPDB, but when you build the BUILDPDB code with UTILBLDP, that parameter is not used. Thanks to Peter Farrell, Commerce Bank of Kansas, USA.
VMAC73 RMF documentation implied that DURATM should be used for Jan 27, 2012 the interval duration, but the Channel Path Measurement Interval SMF73PTI should have been used, and subtraction from EOC and ETC were also wrong. Fortunately, the input variables to these calculated variables are in dataset TYPE73 so they can be recalculated with this SAS code: CHFRATE=SMF73EOC/SMF73PTI; IF SMF73EOC GT 0 THEN CHFACTV=SMF73EOS/SMF73EOC; ELSE SMF73EOC=.; CHFDFER=SMF73EOD/SMF73PTI; CHFXRATE=SMF73ETC/DURATM; IF SMF73ETC GT 0 THEN CHFXACTV=SMF73ETS/SMF73ETC; ELSE SMF73ETC=.; CHFXDFER=SMF73ETD/SMF73PTI; without rebuilding the TYPE73 dataset from SMF records. And the RMF documentation will (hopefully) be revised. Thanks to Steve Olenik, IBM System z Processor Performance, USA. Change 30.003 Spurious XAM INVALID CPU RECORD messages were due to a VMACXAM mislocated SKIP=0; statement if SEGLEN=100. This MXG Jan 27, 2012 error caused XAMCPUBY to have only one observation. Thanks to Robert Obee, IMSHealth, USA. Change 30.002 Change 29.238 typo in line 250: VMACM204 IF ID= _M204LOG OR _IDM204L THEN DO; Jan 27, 2012 was corrected to IF ID= _M204LOG OR ID= _IDM204L THEN DO; So that the correct Model 204 dataset was output. Thanks to Steve Bagshaw, Marks & Spencer, ENGLAND. Change 30.001 MXG Format MGD319F had reversed decoding the Encryption FORMATS type. The correct values are: '00'X:DES, '40'X:AES. VMAC102 -Variable QW0319UR is created from first bit of QW0319FL, Jan 25, 2012 QW0319FLL is now used for the input of QW0319FL (so that any new bits are available), and QW0319FL will be either '00'X or '40'X (unless IBM changes its definition). Thanks to Jason Bierman, Great Lakes Educational Loan Services, USA.
=========================member=CHANGE29================================ /* COPYRIGHT (C) 1984-2012 MERRILL CONSULTANTS DALLAS TEXAS USA */
Second MXG Version 29.29 is dated Jan 18, 2012, thru Change 29.301. First MXG Version 29.29 was dated Jan 17, 2012, thru Change 29.298. MXG Version 29.09 was dated Jan 4, 2012, thru Change 29.291. MXG Version 29.08 was dated Dec 20, 2011, thru Change 29.284. MXG Version 29.07 was dated Nov 24, 2011, thru Change 29.262. Second MXG Version 29.07 was dated Nov 21, 2011, thru Change 29.259. First MXG Version 29.07 was dated Nov 14, 2011, thru Change 29.253. MXG Version 29.06 was dated Sep 8, 2011, thru Change 29.204. First MXG Version 29.06 was dated Sep 1, 2011, thru Change 29.198. MXG Version 29.05 was dated Jul 11, 2011, thru Change 29.151. MXG Version 29.04 was dated May 17, 2011, thru Change 29.116. Final MXG Version 29.03 was dated Apr 19, 2011, thru Change 29.094. First MXG Version 29.03 was dated Apr 11, 2011, thru Change 29.086. Early MXG Version 29.03 was dated Apr 4, 2011, thru Change 29.077. MXG Version 29.02 was dated Mar 1, 2011, thru Change 29.050. MXG Version 29.01 was dated Feb 4, 2011, thru Change 29.022. First MXG Version 29.01 was dated Feb 3, 2011, thru Change 29.020. Annual MXG Version 28.28 was dated Jan 18, 2011, thru Change 28.331. MXG Newsletter FIFTY-SEVEN is dated Jan 18, 2011. Instructions for ftp download can be requested by using this form: 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 29.29. 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 29.29 dated Jan 23, 2012, thru Change 29.307. Major enhancements added in MXG 29.29, dated Jan 23, 2012 TYPEIMS 29.307 Support for IMS Version 12: Adds ZIIP/ZAAP CPU times. RMFINTRV 29.305 INTERVAL=SHIFT generated warnings & incorrect output. TYPETMS5 29.304 USER ABEND 1234 can be bypassed for TMSCLEAN input. IMACICRD 29.302 Comment within comment block if default used. Major enhancements added in MXG 29.29, dated Jan 18, 2012 TYPENDM 29.301 Old Version 4.7 "PS" record INPUT STATEMENT EXCEEDED. TYPERMFV 29.300 Wrong ASMRMFV in first 29.29, VMACRMFV updated. Major enhancements added in MXG 29.29, dated Jan 17, 2012 VMACSMF 29.290 USER ABEND 69 due to invalid SMFTIME now bypassed. TYPENDM 29.295 NDM/Connect-Direct V5.0 added jobname/jctjobid. TYPEXAM 29.294 Support for VNDNIC, LPARNW, USVCPU segments. TYPE110 29.293 Support for CICS Statistics STID=143 and 144. ASMDBLKU 29.289 ASMDBLKU, ASM version of UDEBLOCK, revised. ASMRMFV 29.297 Continued RMF III enhancements. TYPERMFV 29.297 Continued RMF III enhancements. TYPEDCOL 29.296 DCOLLECT support updated to execute on ASCII. BLDSMPDB 29.292 Support for execution under unix. VMXGALOC 29.292 Support for execution under unix. VMXGPPDS 29.298 Compare contents of multiple PDS/PDSE libraries.
(Examples http://www.mxg.com/downloads, ANALGRID.) ASUM4HRS 29.268 %MACRO calculates "Four Hour" running average values (or running average for any number of hours). VMAC30 29.281 CPUTASKALLTM and PCTTASKTIME added SMFINTRV/TYPE30_V. ("Task Time" is recommended by IBM for analysis). ASMTAPEE 29.280 "YOU SPECIFIED ASCENV" Assembly error with z/OS 1.13. (MXGTMNT does NOT need to be reassembled on 1.13) TYPE16 29.264 Support for DFSORT z/OS 1.13 COMPAT new variables. TYPESVIE 29.273 Support for SYSVIEW subtypes 34 and 35. TYPETLMS 29.269 Support for CA TLMS tape library 2003 record changes. TYPETMS5 29.274 CA-1 TMS Extended Format TMC records have no impact. TYPE120 29.272 SM1209CI and SM1209CX can be negative. MXGSASxx 29.265 MXGTEMP temporary DDNAME/FILENAME added to MXG JCL. ASMRMFV 29.279 RMF III RCD INPUT STATEMENT EXCEEDED error.
SMFSRCH 29.236 SMFSRCH, search SMF records for text, print all obs. TYPE7072 29.220 Support for z/OS 1.13 (WAS IN MXG 29.03 or later). TYPETMO2 29.244 Support for TMON/CICS V3.3 (mostly COMPATIBLE) TCE. TYPEQACS 29.208 Support for IBM i-series (AS400), more than 32 CPUs. TYPEDB2 29.213 Support for DB2 V10 IFCID 225 Subtype4 INCOMPATIBLE. TYPETPMX 29.211 Support for Throughput Manager APAR TMT6214, st=16. TYPEBETA 29.233 Support for BETA93 Version 4.1.0 subtype 25 changes. TYPEAXWY 29.231 Support for Axway CFT/ESA (Cross File Transfer) SMF. TYPEPOC 29.219 Support for Tivoli Workload Schedulr Ver 8.3 INCOMPAT TYPEFERT 29.247 Support for ZEN FERRET V2.3 (INCOMPATIBLE). TYPEMPLX 29.247 Support for ZEN IMPLEX V5.1 (COMPATIBLE) TYPEZOSA 29.247 Support for new ZEN OSA MONITOR V1.3 SMF records. TYPEITRV 29.223 Support for APAR OA37114, ITRF (OMEGAMON IMS V420) TYPE70x 29.239 Variable SHIFT (used as "ZONE") added to all RMF. TYPEDB2 29.209 DB2 V10 ID=100 ST=1 INVALID HEADER. TYPEVMXA 29.207 z/VM MONWRITE Broken Control Rec if 2.14 (SCALL) rec. TYPE102 29.235 IFCID=22 in Change 28.234 wrong in DB2 V9. TYPSXAM 29.249 TYPSXAM didn't sort all XMdddddd datasets to the PDB. ASUM113 29.243 Calculation of ESTSCP1M incorrectly had small values. ASMRMFV 29.217 Enhanced RMF III RCDSD section support, CHAR->NUM fix TYPE120 29.240 Length of Character Variable SMF1209FH can't change. TYPEaaaa 29.238 All USER SMF have MACRO _IDaaaa nnn as SMF record id. TYPE16 29.232 DFSORT variables ICEMNVLX, ICEMNVLY, ICEMNVLZ wrong? TYPETPMX 29.229 TPMCA7JN, TPMPI, and TPMDUEOT may be wrong. TYPE1415 29.226 False ERROR.TYPE1415.DEFECTIVE.EXTENDED... log msg. TYPEDB2 29.225 INVALID DB2 V10 QMDA segment for QMDAPTYP='JCC'. TYPE80A 29.223 New TOKENIDs starting with NOxxxx (NOCPUTIMEMAX, etc) TYPE110 29.221 CICS Statistics datasets CICDB2GL,CICSMDSA, corrected TYPE119 29.215 Variables T119STCK/TISSTCK/TIESTCH were still GMT. TYPE78PA 29.214 Values in TYPE78PA ending with TOTL could be wrong. TYPE845 29.212 Invalid JES3 JMF SMF 84 Subtype 1 Segmented Records. Major enhancements added in MXG 29.06, dated Sep 8, 2011 SAS V9.3 29.159 Support for SAS Version 9.3 - SAS Hot Fix E80004: SAS V9.3 Hot Fix E80004 (for SAS Problem Note SN43828) is REQUIRED to correct an error in the %MACRO compiler, which is SAS portable code, so the Hot Fix is required for ALL platforms for SAS V9.3. The %MACRO compiler error is in processing %LET statements. While only two MXG members actually failed in MXG QA tests, ANY use of %LETs can fail in MXG (or in your own %MACRO code).
Seen first with SAS V9.3; complete revision of MXG ODS HTML examples with new %macros with consistent arguments, etc, for all platforms. TYPEVMXA 29.172 Support for APAR VM64961, SMF 113 in z/VM MONWRITE!! TYPE113 29.176 Support for APAR OA36816, SMF 113 HIS DATALOSS parm. IBM now recommends SMF 113 always be created. TYPEIMST 29.162 Validation of TYPEIMST, many changes for IMS56FA. Finally: IMS Transaction CPU/Response from ONE IBM IMS LOG RECORD. TYPEADAB 29.189 Support for Software AG's ADABAS SMF user record. TYPECFS 29.186 Support for InfoSphere Classic Federation Server SMF. TYPE23 29.177 Support for APAR OA35175, logstream stats in SMF 23. TYPE30 29.175 Support for APAR OA35617, SMF30CRM VELOCITY MNGED? TYPE30 29.174 Support for APAR OA34895, EXCP/IOTM Missed, SMF Lock. TYPE57 29.173 Support for APAR OA36966, JES3 expanded NJEJOBNO. TYPEIDMS 29.156 Support for IDMS/R Performance Monitor Version 18. TYPEVMXA 29.163 z/VM Crypto Record (5,10) with PRCAPMCT=6 error. TYPE115 29.161 MXG 29.03-MXG 29.05 dataset MQMCFMGR was wrong. TYPEDM 29.158 NDM-CDI Version 5 new fields supported. TYPE110 29.155 CICS/TS 4.2 Statistics variables overlooked, added. VMXGSUM 29.154 AUTOCALL %macro's %CMPRES/%QCMPRES removed. TYPE111 29.153 UNDECODED CTGRECID message, possible CPU loop. TYPE7072 29.152 VMSYSTEM='Y' RMF records validated, and revised. RMFINTRV 29.194 Stats on Page Dataset Slot Usage added to RMFINTRV. ASUM113 29.193 zVM MONWRITE VXPRCMFC (SMF 113 for z/VM) included. ASUMUOW 29.188 Case 4 example prevents blank TRANNAME in ASUMUOW. ASMRMFV 29.187 Do not use ASMRMFV in MXG29.05, fails with 0C4 ABEND. GRAFWRKX 29.185 Workload RMFINTRV graph's update uses new workloads.
TYPE110 29.149 Support for CICS/TS 4.2. MNSEGCL=5 requires 29.05. TYPE120 29.136 Support for WebSphere WAS 8.0 (COMPATIBLE). TYPE70 29.127 Support for z/OS 1.12 VMGUEST option, CPU Time in 70. TYPEIMST 29.144 IMS Transactions in IMS56FA, replaces JCLIMSL6!!! TYPETIMS 29.123 Support for TMON/IMS Version 3.0 (INCOMPATIBLE). TYPEPOEX 29.134 Support for Informatica's POWER EXCHANGE SMF record. TYPEDB2 29.140 New LUUVTIME instead of QWACBSC for start time. TYPE90A 29.142 Enclave variables decoded in TYPE9030 dataset. TYPEVMXA 29.133 z/VM LPARNAME, LPNUMBER kept in PDB.VMXAINTV. UTILARCH 29.137 New UTILARCH archives data (like Outlook archive). TYPEDB2 29.131 DB2PARTY added to DB2ACCTP, Rollup impact documented. TYPEDB2 29.128 DB2 INVALID DISTRIUTED HEADER message corrected. TYPEDB2 29.121 QWHADSGN/QWHAHAMN were sometimes blank. TYPE102 29.125 DB2 SMF 102 IFCID 22 INPUT STATEMENT EXCEEDED error. TYPEVMXA 29.129 MXGERROR DM 5 RC 10 UNDECODED PRCAPMCT due to IBM. TYPEXAM 29.126 XAM variables in VXSYTEP2 were not all input/kept. TYPE111 29.124 Variables CTGIAREQ/CTGLALRQ revised keeps. ANALDB2R 29.145 Performance and Reporting Enhancements
DB2ACCT 29.111 DB2 CICS TRAN name could be wrong, now from QWHCCV. TYPEIMSA 29.110 the exit _IMSTRN invocation was accidentally removed. BUIL3005 29.106 JES3 PDB.JOBS variable JOBCLAS8 has after change. VMXGSRCH 29.103 RESULTS=FINDVAR finds all datasets with a variable. TYPE70PR 29.098 Counts ICFCPUS/IFLCPUS/IFACPUS/ZIPCPUS too high. TYPE110 29.097 INPUT EXCEEDED 110-2 MNSEGLC=5 with DPL segment
TYPE116 29.057 Support for Websphere for z/OS MQ Version 7.0.1. TYPE115 29.057 Support for Websphere for z/OS MQ Version 7.0.1. TYPEBBMQ 29.056 Support for MainView MQ (MVMQ) Version 4.4. TYPEQACS 29.078 Support for OS/400, AS/400 Version 7.1 (INCOMPATIBLE) TYPE110 29.076 CICS CPUTM exceeds ELAPSTM, zAAP/zIIP Equivalent time TYPE120 29.081 Support for User Field in SMF 120 Subtype 9 record. TYPETPMX 29.071 Support for Throughput Manager subtype 10 and 16. TYPENTSM 29.075 Support for 62 new objects and 1425 new NT metrics. UTILVREF 29.075 MXG now creates DATASET names up to 32 characters. BUILDPDB 29.068 MXG 28.28-29.02. ABEND=JCL obs missing in PDB.JOBS. TYPERACF 29.067 RACF UNLOAD dataset RACF0270 UID limit variables. TYPEBETA 29.059 Support for Beta 93 Version 4.2 subtypes 25/50. TYPE30 29.058 Variable CPUCEPTM always now set to a missing value. MONTHxxx 29.052 SAS 9.1.3 Only. %QCMPRES needed versus %CMPRES. TYPE85 29.093 INPUT STATEMENT EXCEEDED st 79, z/OS 1.12. ASUM70PR 29.092 ZIPCPUS/IFACPUS included parked time. TYPEVMXA 29.092 z/VM new PDB.VXINTUSR sums all engines for each VM. Major enhancements added in MXG 29.02, dated Mar 1, 2011 VSETMNTH 29.041 POSSIBLE LOSS OF MONday DATA IN FEBRUARY MONTHLY PDB. (Unfortunately, EVEN with the newest MXG 29.01). The MXG2828 or MXG2901 ftp credentials are still valid; you can download 29.02 and copy the two members you need (VSETMNTH, and BUILDxxx or BLDSMPDB), or you can ftp only those specific files to correct the error, for this month and for future months, or you can install 29.02. Without these updated members/29.02, future MONTHly's can also be missing one or more day's PDBs in your MONTH PDB. The complete details are in Change 28.041, below. TYPENDM 29.042 Support for NDM-CDI Version 5 records (COMPATIBLE). VMACDB2H 29.037 DB2 V9.1 false "INVALID DISTRIBUTED HEADER" message. TYPE30 29.034 Invalid data for SMF30RGT is true, circumvented. TYPECIMS 29.033 Support for IMF Version 4.5 is in place. TYPE0 29.032 PDB.IPLS, now, DOES always report a SYSTEM IPL. TYPEDB2 29.031 DB2 V9.2 only, most QBGxxx variables DB2GBPST wrong. TYPEVMXA 29.026 Support for zVM APAR VM64794 (COMPATIBLE). TYPE30 29.025 Small negative CPUUNITS now set to zero. TYPE26J2 29.024 Cosmetic: INREASON NOT DECODED messages corrected.
MONTHBLD 29.017 SERIOUS ERROR CORRECTED: last day's PDB skipped. BLDSMPDB 29.017 LIBNAME WEEK1 not found corrected.
BLDSMPDB 29.008 SORTEDBY=NO default to eliminate NOTSORTED exposure. WEEKBLD 29.008 MXGNOBY default to eliminate NOTSORTED exposure. MONTHBLD 29.008 MXGNOBY default to eliminate NOTSORTED exposure. TYPEENDV 29.012 Support for Endeavor Version 14 (INCOMPATIBLE). TYPE111 29.001 Support for IPIC creates obs in TY111CXI. TYPE115 29.015 Support for MQ Version 7 compression statistics. TYPE89 29.002 Support for APAR OA31615, zIIP/zAAP times added, and false error messages are eliminated.
current MXG Technical Notes. All of these enhancements are described in the Change Log, below.
all supported platforms, but SAS V9.3 Hot Fix E80004 is REQUIRED (for SAS Problem Note SN43828) to correct an error in the %MACRO compiler, which is SAS portable code, so the Hot Fix is required for ALL platforms for SAS V9.3. 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. With Hot Fix E80004, the full MXG QA test stream executed with no errors, and there were no new warnings on z/OS. Users of ODS will want MXG 29.06, because SAS V9.3 did expose incompatibilities in Yüklə 28,67 Mb. Dostları ilə paylaş:
|