* copyright (C) 1984-2017 merrill consultants dallas texas usa *


Download 27.49 Mb.
Name* copyright (C) 1984-2017 merrill consultants dallas texas usa *
page1/562
A typeDocumentation
  1   2   3   4   5   6   7   8   9   ...   562
========================================================================

/* COPYRIGHT (C) 1984-2017 MERRILL CONSULTANTS DALLAS TEXAS USA */

========================================================================

This member (CHANGESS) contains ALL changes to ALL MXG Versions, so

that you can search a single member if you are looking for information.

(Use EXCLUDE ALL then FIND ===member= ALL to see MXG Version.)

Member CHANGES still contains the current changes, incompatibilities,

hot notes, etc., and the members CHANGEnn still contain the changes

that were introduced in MXG Version nn.

Member NEWSLTRS contains new technical notes and all past newsletters.

=========================member=CHANGE35================================

/* COPYRIGHT (C) 1984-2017 MERRILL CONSULTANTS DALLAS TEXAS USA */
MXG Version 35.03 is dated Mar 27, 2017, thru Change 35.072

First MXG Version 35.03 was dated Mar 22, 2017, thru Change 35.069

MXG Version 35.02 was dated Feb 10, 2017, thru Change 35.035

MXG Version 35.01 was dated Jan 20, 2017, thru Change 35.014

ANNUAL MXG Version 34.34 was dated Jan 3, 2017, thru Change 34.284

ANNUAL MXG Version 34.34 was dated Jan 3, 2017, thru Change 34.284

MXG Newsletter SIXTY-EIGHT was dated Jan 3, 2017.
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 35.03 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 35.03.

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 35.03 re-dated Mar 27, 2017, thru Change 35.072
Major CHANGES added in MXG 35.03, dated Mar 27, 2017 thru 35.072.
VMAC1415 35.072 First MXG 35.03. Debug HEX DUMPS on log, no ERROR.

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 zVM 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.
Execution Errors Corrected:

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.
Major CHANGES added in MXG 35.01, dated Jan 20, 2017 thru 35.015.
POTENTIALLY SERIOUS Error Corrected:
RMFINTRV 35.006 Duplicate RMFINTRV if Multiple Capacity Groups exist.
Culprit was MXG's addition of variable SMF70GNM to PDB.RMFINTRV

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.
Errors Corrected:

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 OA51484 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.
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 Versions

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 V9.4 M3 Is RECOMMENDED, but MXG executes without error using

SAS Version 9.4 M0, M1, M2, and M3 or SAS Version 9.2 M1 and M2.
SAS V9.4 M2 is USABLE. 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 is USABLE. 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 MXGSAS94 JCL Procedure example.

***************************************************************
MXG 26.03 thru MXG 35.03 will execute under the previously listed

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.
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 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.

****************************************************************
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.
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
  1   2   3   4   5   6   7   8   9   ...   562

Share in:

Related:

* copyright (C) 1984-2017 merrill consultants dallas texas usa * icon* copyright (C) 1984-2011 merrill consultants dallas texas usa *

* copyright (C) 1984-2017 merrill consultants dallas texas usa * icon* copyright (C) 1984-2013 merrill consultants dallas texas usa *

* copyright (C) 1984-2017 merrill consultants dallas texas usa * icon* copyright (C) 1984-2010 merrill consultants dallas texas usa *

* copyright (C) 1984-2017 merrill consultants dallas texas usa * icon* copyright (C) 1984-2017 merrill consultants, dallas, texas *

* copyright (C) 1984-2017 merrill consultants dallas texas usa * icon* copyright (C) 1984-2010 merrill consultants, dallas, texas *

* copyright (C) 1984-2017 merrill consultants dallas texas usa * icon* copyright (C) 1984-2013 merrill consultants dallas texas usa */...

* copyright (C) 1984-2017 merrill consultants dallas texas usa * icon59th Annual Texas cpa tax Institute San Antonio and Dallas, Texas November 13 and 14, 2012

* copyright (C) 1984-2017 merrill consultants dallas texas usa * iconUniversity of Texas at Dallas

* copyright (C) 1984-2017 merrill consultants dallas texas usa * iconAll procedures that involved use of animals were approved by the...

* copyright (C) 1984-2017 merrill consultants dallas texas usa * icon[Obviously the Dallas addresses below apply only to Dallas County...




forms and shapes


When copying material provide a link © 2017
contacts
filling-form.info
search