LASTCHANGE: Version 32.
=========================member=CHANGE31================================
/* COPYRIGHT (C) 1984-2014 MERRILL CONSULTANTS DALLAS TEXAS USA */
ANNUAL MXG Version 31.31 is dated Jan 20, 2014, thru Change 31.296
MXG Version 31.09 was dated Dec 30, 2013, thru Change 31.278
MXG Version 31.08 was dated Nov 12, 2013, thru Change 31.244.
First MXG Version 31.08 was dated Nov 12, 2013, thru Change 31.240.
MXG Version 31.07 was dated Sep 20, 2013, thru Change 31.204.
MXG Version 31.06 was dated Sep 3, 2013, thru Change 31.187.
First MXG Version 31.06 was dated Sep 1, 2013, thru Change 31.184.
MXG Newsletter SIXTY-TWO was dated Sep 1, 2013.
MXG Version 31.05 was dated Jul 29, 2013, thru Change 31.156.
MXG Version 31.04 was dated Jun 26, 2013, thru Change 31.125.
MXG Version 31.03 was dated Jun 17, 2013, thru Change 31.114.
MXG Version 31.02 was dated May 5, 2013, thru Change 31.088.
First MXG Version 31.02 was dated Apr 29, 2013, thru Change 31.079.
MXG Version 31.01 was dated Mar 13, 2013, thru Change 31.044.
MXG Newsletter SIXTY-ONE was dated Jan 21, 2013.
Annual MXG Version 31.31 is dated Jan 20, 2014, thru Change 30.296.
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.
Contents of member CHANGES:
I. Current MXG Software Version 31.31 is available upon request.
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 31.31.
VI. Online Documentation of MXG Software.
VII. Changes Log
Member NEWSLTRS contains Technical Notes, especially APARs of interest
and is updated with new notes frequently. All Newsletters are online
at http://www.mxg.com in the "Newsletters" frame.
Member CHANGES contains the changes made in the current MXG version.
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 31.31 dated Jan 20, 2014, thru Change 31.296.
Major enhancement added in MXG 31.31, dated Jan 20, 2014:
TYPE111 31.283 Support for CICS Transaction Gateway V9R0 (COMPAT)
UTILEXCL 31.295 Negative values in variable TASELGTM with IMACEXCL.
VMAC73 31.291 SMF73SPD Channel Speed now always in MBits/sec.
TYPE30 31.280 IOTMNOCA=SMF30AIC-IOTMDASD corrected (was IOTMTOTL).
ASMRMFV 31.296 RMF III Enhancements including new TABERR parameter.
ASMRMFV 31.287 MXG 31.02-31.09. ASMRMFV could skip RCD tables.
MXGLABEL 31.288 New %MXGLABEL creates LABEL with NAME and LABEL.
VMXGINIT 31.285 JCL //INSTREAM DD is no longer required for z/OS MXG.
ANALDB2R 31.286 Selection by PLAN moved into READDB2, saves time.
TYPEDB2 31.282 DB2PM *ROLSUM*,*ROLLUP* both now set DB2PARTY='R'.
JCLUOTT2 31.293 Sample JCL to create PDB.ASUMUOW,CICS with TMON/CICS.
GRAFWRKX 31.294 New NEWMODEL parameter view workloads on new CPU.
FORMATS 31.291 MG073FR decodes SMF73CPP frame size 16/24/50/64KB.
IHDRTMO2 31.290 TMON/CICS TA header exit IHDRTMO2 now after offsets.
Major enhancement added in MXG 31.09, dated Dec 30, 2013:
FORMATS 31.251 WPS FAILS WITH 31.08 FORMATS, PICTURE NOT SUPPORTED.
TYPEBVIR 31.254 BVIR30 dataset was incorrect with VERSION 3 records.
TYPEDB2 31.245 Support for APAR PM90886 new IDAA/NETEZZA ELIGIBLEtm.
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
UTILBLDP 31.276 Ad hoc read SMF UTILBLDP is enhanced WANTSMF= list.
TYPERMFV 31.273 Support for RMF III CATG3 Cache Data ERB74CA dataset.
ASMRMFV 31.273 Support for RMF III CATG3 Cache Data ERB74CA dataset.
TYPENMON 31.264 Support for Red Hat Linux Data Group,NFSCLIV4 metrics
TYPEDB2 31.272 Invalid SMF 101 subtype 1 from ASG TMON/DB2 DB2ACCTP.
TYPE30 31.277 TYPE30MU dataset now has zero obs by default: useless
VGETOBS 31.250 A better way to identify TAPE data libraries.
READDB2 31.269 "Too few" IFCIDs listed caused no sort to PDBOUT.
TYPE110 31.253 SMSGDHWM/SMSGCCUR correction for CICS/TS 4.2 or later
TYPEDB2 31.259 Variable QWHSNIDIP=IP*ADDR*FROM*QWHSNID QWHCATYP=8
TYPETPMX 31.263 ERROR.VMACTPMX. VARNAME=$INCLAI or $DBS_SD NOT FOUND.
TYPE7072 31.274 System with only CPs + ICFs, LPAR SHARE weight wrong.
TYPE7072 31.266 MSU Units (Hardware vs Software) in TYPE70/TYPE72GO.
GRAFCEC 31.246 NOT SORTED error with multiple CEC's data.
ANALDB2R 31.262 Some AVG Buff stats wrong, possible dataset not found
ANALHSM 31.260 Variable HSMPLEX added to all HSM reports.
TYPE80A 31.257 TOKDANAM='UTYPE' ERROR if last, new TOK variables.
ANALGRID 31.248 DATES= any one of the "one word" tokens didn't work.
VGETOBS 31.247 ERROR: WORK.MXGTABLES NOT FOUND with earlier VGETOBS.
VMXGRMFI 31.268 Some RMFINTRV xxxxSWAP xxxxTRAN xxxxEXCP un-formatted
TYPEDB2 31.275 MXGWARN: T102S225 DOES NOT EXIST.
Many 31.270 Messages with 'ERROR:' starting in byte one shifted.
Major enhancement added in MXG 31.08, dated Nov 12, 2013:
TYPEDB2 31.240 Support for DB2 V11.1. (MXG 30.30+ TOLERATES with no
EXECUTION error, but the QLST variables in DB2STATS
require MXG 31.04 for both DB2 V10.1 and V11.1.)
ASMRMFV 31.230 RMF III Enhancements: BIG DISK SPACE SAVED in ZRBDVT.
ASMRMFV 31.230 RMF III Support for DSNTYPE=LARGE.
MANY 31.221 ODS Support for TYPE=PDF, MANY ANALxxxx updated
TYPECIMS 31.233 Correction for IMF 4.2 thru 5.1 (WRONG VALUES)
TYPECIMS 31.206 Support for IMF 5.1 (INCOMPAT, but only CIMSDBDS).
TYPEPDM 31.226 Support for Alebra Parallel Data Mover SMF record.
TYPEJESC 31.225 Support for Emtex JESCONNECT SMF Record.
EXCICJRN 31.217 Support for CICS "multi journal records".
TYPETLMS 31.215 Support for new TLMS variables, compression percent
TYPE7002 31.220 Enhancement to CRYPTOGRAPHIC PROCESSOR (70-2) support
VGETOBS 31.212 Final (?) revisions to VGETOBS to bypass tape mounts.
TYPE110 31.214 CICSJS variables SJSMAJCP/SJSMINCP are not CPU time.
TYPE113 31.208 ASUM113 LPARBUSY/MIPSEXEC wrong for zEC12 processor.
TYPE6 31.207 31.07 only. Debugging SMFLN3=162 LENLEFT=552 removed.
TYPE119 31.218 INVALID DATA FOR SCACTIME in ID=110 SUBTYPE=32.
TYPE42 31.216 INVALID DATA FOR S42CSYNC.
ANALATEN 31.205 Analysis of Latent Demand report.
VMXGSRCH 31.219 Search which character variables contain text string.
WPS 31.224 Current status of WPS circumventions and differences.
Major enhancement added in MXG 31.07, dated Sep 20, 2013:
TYPE0 31.193 z/OS 2.1 ID=0 "IPL" RECORD now 68 bytes, MXG DELETES.
(ONLY A PROBLEM IF YOU THINK ID=0 IS AN IPL WHICH IT
often is not - always use the PDB.IPLS BUILDPDB DATA
to report IPL events. See change text.)
The DB2 MXG 31.06 "VGETOBS" enhancements still had some glitches:
ANALDB2R 31.204 ANALDB2R (31.06) with PDB=PDB and PDB on tape fails.
READDB2 31.191 READDB2 PDBOUT=, or PDBOUT=XXX may not work right.
VGETOBS 31.200 Revisions in concert with VMXGWORL for READDB2.
VMXGWORL 31.200 Revisions in concert with VGETOBS for READDB2.
Those VGETOBS changes solved two very different problems:
1. WPS failed when there was no LIBNAME when there was a
WHERE clause on PROC SQL read of DICTIONARY.TABLES.
Solved by looking at DICTIONARY.FILENAMES without a
WHERE first to see if the DD even exists.
2. SAS mounting and rereading every tape with every
execution of VGETOBS reading DICTIONARY.TABLES, even
when there was NO where clause.
Solved by keeping track of tape DDs and excluding
them from DICTIONARY.TABLES searches with a WHERE
CLAUSE NE.
-Solving problem 2 cut tape mounts in daily CICS/DB2 job
at one site from over 90 to less than 20.
TYPEDB2 31.196 Support for DB2 APAR PM67806 adds QW0225DMH DMG GETMs
TYPE115 31.188 Support for MQ SMF 115 ST 2 SMDS/QESD, new TYPE115S.
FORMATS 31.189 Support for CEX41 Crypto Coprocessor type corrected.
JCLVSB2U 31.198 JCL example to change RECFM=VBS to RECFM=U w/o copy.
TYPEVMXA 31.194 MXG 31.02-31.06 BROKEN CONTROL, STOSHD MRHDRLEN=112.
TYPETMMQ 31.190 Many new variables added to TMMQQU MQ QUEUE dataset.
TYPE117 31.199 S17NNDM added to the BY list _B117NOD for NODUP.
TYPEIDMS 31.197 After MXG 30.30, only IDMS 17, zero obs in IDMSINS.
Major enhancement added in MXG 31.06, dated Sep 3, 2013:
TYPERMFV 31.181 RMF III Support for z/OS 2.1 plus Enhancements.
TYPE115 31.179 Support for MQ 7.1.0 SMF 115 subtypes 5, 6, and 7.
TYPE102 31.166 Support for IFCID=380 STORED PROCEDURE DETAILS
TYPEBVIR 31.168 Support of Hydra/BVIR Version 3 new data fields.
TYPEXAM 31.160 Support for Velocity Software new segments new data.
All SMF 31.182 New INPUT SMF FILE DID NOT END WITH ID=3 message.
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
TYPE120 31.170 Variable SM1209BK (Short Server) added TYP1209C/S/U.
TYPESHDE 31.177 SHADOW variable SM01ADCT ADABAS COMMAND COUNT wrong.
TYPEZPRO 31.167A VOLTAGE Release 4.2 segment count circumvention.
READDB2 31.167 DB2 V8 ONLY. V8-only IFCID=225 were not read.
READDB2 31.165 PDB.DB2STAT1 not created with READDB2 STATISTICS.
TYPEBETA 31.162 Variable JOB and BETAJOBN are now consistent.
TYPE7072 31.174 WARNING: MULTIPLE LENGTHS FOR IFAUPTM and Tutorial
TYPENMON 31.164 Protection for invalid NMON DISKxxxx records.
VMXGSRCH 31.171 UNABLE TO CREATE WORK.TABLES.DATA circumvented.
VGETOBS 31.180 Circumvent WPS 3 ABEND with unopened LIBNAME on tape.
READDB2 31.163 WPS 3 ONLY. WPS 3 Compiler macro resolution error.
Major enhancement added in MXG 31.05, dated Jul 23, 2013:
MANY 31.153 Support for z/OS 2.1: COMPATIBLE, VALIDATED WITH DATA
TYPEVMXA 31.151 Support for zVM 6.3 MONWRITE, INCOMPAT due to MXG.
TYPETMD2 31.133 Support for TMON for DB2 Version 5 second iteration.
ASMRMFV 31.150 MAJOR RMF III enhancement - dynamic VSAM allocation.
TYPE70PR 31.140 SMF70GNM, Group Name, blank in MXG 31.03-31.04.
TYPE70 31.130 SHARE Weights for zIIP/zAAPs corrected.
TYPE78CU 31.127 Vars R783DCTM/DDTM (CU Connect/Disconnect) added.
ASUMTAPE 31.149 _GRPMNNM/_GRPMNCD failed after Change 30.203.
TYPERACF 31.146 INPUT STATEMENT ERROR RACF UNLOAD, invalid data too.
TYPE120 31.143 TYP1209E variables SM1209DA-DF are accumulated.
UTILEXCL 31.147 Support for CANPROD4, CANPROD5 and CANPROD6 fields
VMAC80A 31.139 Support for RACF TOKDANAM='UNAME'.
RMFINTRV 31.138 Multi-period RSP/TRN/SWP mislabeled BAT1 vs BATHI.
TYPECIMS 31.137 IMF TRXZxxxx variables incorrectly input.
TYPEWWW 31.137 IIS Log with ' ... ' COOKIE value caused MXG loop.
READDB2 31.128 LDB2*** parameters were not honored.
EXUTILEX 31.131 EXUTILEX is NO LONGER SUPPORTED for UTILEXCL tailor.
Major enhancement added in MXG 31.04, dated Jun 26, 2013:
TYPENMON 31.119 Variables IPCSTIME and TIMEZONE added to NMONBBBP.
TYPEEDGR 31.118 Support for EDGRXEXT variables added in z/OS 1.13
TYPEDB2 31.117 DB2 V10. All QLSTxxxx numerics WRONG (DBSTATR/STATS).
TYPETPMX 31.116 TYPETPMX variable JOBNUM truncated if 6 digits long
READDB2 31.115 READDB2 with COMPRESSED/Internal, NO OBS created.
Major enhancement added in MXG 31.03, dated Jun 17, 2013:
SAS Version 9.4 is COMPLETLY COMPATIBLE with MXG QA tests; no changes
to MXG are required, no errors nor new warnings were observed.
See SAS Technical Note in Newsletter SIXTY-TWO for comparison metrics.
TYPEDB2 31.117 ALL QLSTxxxx VALUES IN DB2 V10 ARE WRONG.
TYPEIMS 31.102 Support for IMS 13, INCOMPATIBLE, DLRAZAAP inserted.
TYPEIMSA 31.102 Support for IMS 13, INCOMPATIBLE, DLRAZAAP inserted.
TYPE110 31.110 CICS/TS 5.1 MNSEGCL=5 file resource INCOMPATIBLE.
ASMTAPEE 31.105 ML-51 corrects MXGC010E error when STKX=NO used.
TYPEDB2 31.093 New "INVALID" DB2 ID=100 ST=5 Startup now Supported.
(and more accurately, "UNDOCUMENTED/UNEXPECTED").
Prior MXG 31.02's could ABEND without this change.
MXG 31.01 and earlier will NOT fail, but will print
1,440 "CALL HOME" messages per subsystem per day.
EXPDBACC 31.094 BUILDPDB enhancement: create your own acct variables.
IMACICUS 31.090 MXG 31.02. LENUSRCH=32 should be LENUSRCH=0 default.
ANALID 31.086 SMF Audit Reports DB2 ACCUMAC ZPARM enabled status.
ASMRMFV 31.111 Further internal enhancements to RMF III support.
Major enhancement added in re-dated MXG 31.02, dated May 5, 2013:
TYPEDB2 31.088 Protection for INVALID ID=100 SUBTYPE=5 DB2 record.
TYPEDB2 31.081 Support for DB2 V10 ID=100 ST=5 IFCID=369 CPU by CONN
New DB2 Statistics record with CPU and Wait Times and
all QBACxxxx variables by Connection Type.
Major enhancements/corrections added in MXG 31.02, dated Apr 29, 2013:
TYPEXDFG 31.049 Support for WAS XD (WebSphere Extended Deployment).
ASMIDMP 31.068 Pace-contributed IDMS exit code for Change 31.018.
JCLSQLID 31.067 Point-in-time mapping DBID/OBID hex to their names.
ANALDB2R 31.067 Point-in-time mapping DBID/OBID hex to their names.
ANALDB2R 31.061 New MXGACC03 report counts concurrent DBATs.
ASMRMFV 31.062 RMF III Enhancements - blocking CPU and CPCDB.
TYPERMRV 31.062 RMF III Enhancements - blocking CPU and CPCDB.
TYPERMFV 31.074 RMF III dataset ZRBLCP var LCPUPOLR/CHIN/CHIX wrong.
TYPE74 31.072 Format MG0748L new value for 16 GB/s Link Type
IMACICUX 31.051 Support for user field CHARGE creates USCHARGE Var.
UTILEXCL 31.051 ***UNKNOWN FIELD*** protection still didn't protect.
IMACCADI 31.060 CA-Dispatch CADIxxxx values corrected.
TYPENMON 31.058 NMON records SEA, SEAPACKET, DONATE are supported.
TYPEDB2 31.056 Variable THREADS now correctly set for ROLLUPs.
TYPEPRPR 31.054 Corrections to '1031' and '1061' records.
TYPEWWW 31.052 IIS Weblog URIQUERY with &=1 and no name supported.
TYPE110 31.048 MXG 31.01 only, STID=29, CICSMDSA dataset wrong.
IMAC6ESS 31.047 ESS GEPARMKY=0039 creates new ESSOPTNS in TYPE6.
TYPE90A 31.045 ID=90.6,7 EVENTIME is IPLTIME of the system.
Major enhancements/corrections added in MXG 31.01, dated Mar 13, 2013:
TYPEVFTP 31.023 Support for Software Diversified Services VFTP SMF.
TYPEVIP 31.022 Support for Software Diversified Services VIP SMF.
TYPESHDW 31.022 Support for Shadow user SMF subtype 21 record.
TYPEBVIR 31.016 Support for BVIR Version 2.0/2.0a/2.1.
TYPETMMQ 31.020 Support for TMON/MQ Version 2.15 new data.
TYPE85 31.006 Support for OAM SMF ID=85 STs 90,91,92 and 93.
TYPEIDMP 31.018 Support for PACE's IDMS 17 KOMAND/IDCS SMF record.
TYPE102 31.001 Support for variable QW0141OT in T102S141 dataset.
TYPENTSM 31.030 Major update for NTSMF adds datasets and variables.
TYPERMFV 31.021 RMF III Enhancements including ASI/ENC blocking.
TYPERMFV 31.004 RMF III, z/OS 1.13 APAR OA38660 ASI data wrong.
VGETWKLD 31.028 Hardcoded VIEWs removed.
TYPE102 31.027 Variable QWHCEUWN added to T102Snnn DB2 datasets.
PREINIT 31.026 Pre-MXG-Initialization exit for SASHELP.VEXTFL.
TYPEDB2 31.015 "Truncated" QPACLOCN/COLN/PKID/ASHC/AANM maybe wrong.
VMACSMF 31.014 New %LET SMFPUTHD=NO; suppresses header messages.
TYPE110 31.012 CICLDR output tests LDRTU instead of LDRFC.
TYPETMNT 31.010 MSGID NOT FOUND for MXGTMNT SYSLOG SUBTYPE 8 record.
ANAL120 31.008 Example WebSphere SMF 120 reports revised.
TYPE113 31.003 Message UNINIT VARIABLE SM1132MM minimal impact.
CICINTRV 31.002 CICTSQ new A12xxxx variables now kept in CICINTRV.
TYPEBVIR 31.039 Option to add SYSTEM value to IBM TS7700 BVIR data.
TYPEBETA 31.036 BETA93 had invalid data in BETA1 for 4.2.0 and 4.3.0.
ANALDB2R 31.034 MXG 30.10-30.30. PMAUD02 caused ERROR keyword parm.
Please read CHANGESS for the complete list of major enhancements.
See member NEWSLTRS or the Newsletters frame at http://www.mxg.com for
current MXG Technical Notes.
All of these enhancements are described in the Change Log, below.
II. SAS Version requirement information:
SAS Version 9.4 and SAS 9.4.1 were both tested with NO CHANGES.
JCL in MXGSAS94 or MXGSAS93 can be used, or MXGNAMES can be used
with your existing, installed SAS JCL procedure - see below.
SAS Version 9.3 TS1M1 is RECOMMENDED for all PLATFORMS, because
SAS Version 9.3 TS1M0 REQUIRES THE HOT FIX in SAS NOTE SN43828
(for all platforms), and TS1M1 contains that Hot Fix.
Note: SAS 9.2 is reduced to SAS Level B support Sep 30, 2013.
Note: SAS 9.1.3 is reduced to SAS Level c support Sep 30, 2013.
***************************************************************
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.
***************************************************************
MXG 26.03 thru MXG 31.31 will execute under SAS Version 9.3, on
all supported platforms, but as noted above, you need TS1M1. With
TS1M0, then the Hot Fix in SAS Problem Note SN43828 is REQUIRED to
correct an error in the %MACRO compiler, which is SAS portable
code, so that Hot Fix is required for ALL platforms.
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.
With the Hot Fix on TS1M0, the full MXG QA test stream executed,
and there were no new warnings on z/OS.
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.
MXG 26.03 thru MXG 31.31 will execute under SAS V9.4, V9.3, V9.2
or SAS V9.1.3 with Service Pack 4, on all supported SAS platforms.
SAS Hot Fix for SAS Note 37166 is required to use a VIEW with
the MXG EXITCICS/CICSFIUE CICS/DB2 Decompression Infile Exit.
SAS V9.1.3 is NOT supported by SAS on Windows SEVEN platform,
but SAS V9.2 does execute on that platform.
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.
Old MXG code may continue to execute with SAS V8.2, but V8 is now
"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 can not guarantee that all of MXG executes error free.
PLEASE INSTALL V9.2/V9.3/V9.4, TO AVOID FIXED PROBLEMS!
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
Version 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 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.
****************************************************************
SAS Data Libraries are compatible for V8.2, V9.1.3, V9.2, V9.3,
and V9.4. "PDBs" can be read/written interchangeably between
these SAS versions.
MXG Versions 26.03+ do execute with SAS V9.2 with NO WARNINGS
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.
For SAS V9.1.3 on z/OS with Service Pack 4:
On z/OS 1.10, Hot Fix SN-35332 is REQUIRED.
CONFIGV9 now specifies V9SEQ instead of V6SEQ. As V6SEQ does
not support long length character variables, it can't be used.
SAS V9.1.3 with current Service Pack 4 is STRONGLY RECOMMENDED.
Dostları ilə paylaş: |