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

Required for TYPEIMS users; major revision in IMS log processing.

Strongly recommended for DB2 sites, because it:

- has significant corrections in ANALDB2R reporting,

- has speeded up MXG DB2 processing and reduced WORK space needed,

- allows DB2ACCT direct to tape for sites with large DB2 activity,

- has new ASUMDB2A to summarize and reduce size of DB2ACCT.

- has MVS Account fields added to DB2ACCT (DB2 2.3).

Offers support for these new products or releases:

Support for AICorp's KBMS user SMF record.

Support for Amdahl's APAF replacement for MDFTRACK.

Support for Blue Line's Vital Signs for VTAM type 28.

Support for Fujitsu's FACOM MSP/EX (incompatible) SMF records.

Support for MVS/ESA 4.2 Dynamic I/O Reconfig in MXG Tape Monitor.

Support for NETSPY Release 4.2 added.

Support for NETSPY Token-Ring records added.

Support for ROSCOE Release 5.7 changes to SMF data.

Support for RSD's WSF/WSF2 Release 3.4.1.

Support for SPMS 1.2.13 incompatible changes.

Support for STOPX37 Release 3.4.

Support for Software Ag "Natural Process" SMF record.

Support for System Center's NETMASTER type 37 SMF records.

Support for The Network Director North Ridge Software

Support for UNIX iostat and vmstat commands from ULTRIX.

ASMVTOC avoids 213/314 abends reading VTOC of TPF or VM volumes.

LPAR CPU utilization reports added.

MINTIME=,MAXTIME= parameters added to VMXGSUM.

MVS/ESA 4.2.0 changed format of DEVNR/UNITADR in TYPE75.

MXG Tape Mount Monitor supports MVS/ESA dynamic reconfiguration.

New dataset TYPE40_D can be created for tape analysis

TAPE3490 (3490s allocated) added to PDB.STEPS/JOBS.

Trending with INTERVAL=MONTH members added.
Each of these enhancements are described in the Change Log, below.
The following table lists announced availability dates for the IBM

product, and the corresponding Version of MXG required to support

that IBM product.

Availability MXG Version

Product Name Date Required
MVS/370, MVS/XA (all) long ago 8.8

RMF 4.1.2 (for MVS/ESA 3.1.3) Sep 7, 1990. 8.8

RMF 4.2 (for MVS/ESA 4.1) Oct 26, 1990. 8.8

MVS/ESA 4.1 Oct 26, 1990. 8.8

MVS/ESA 4.2 Mar 29, 1991. 9.9

RMF 4.2.1 (for MVS/ESA 4.2) Mar 29, 1991. 9.9

MVS/ESA 4.2.2 Aug 1991. 9.9

RMF 4.2.2 (for MVS/ESA 4.2.2 Aug 1991. 9.9

MVS/ESA 4.3 Mar 23 1993. 10.5

RMF 4.3.0 (for MVS/ESA 4.3 Mar 23 1993. 10.5

CICS/ESA 3.1 1990 8.8

CICS/ESA 3.2 Jun 28, 1991. 9.9

CICS/ESA 3.3 Mar 28, 1992. 10.1

DB2 2.2.0 1990 8.8

DB2 2.3.0 Oct 28, 1991. 10.1

VM/ESA 1.1.0 (370 Feature) Oct 26, 1990. 8.8

VM/ESA 1.1.0 (ESA Feature) Mar 29, 1991. 8.8

VM/ESA 1.1.1 Dec 27, 1991. 10.1

VM/ESA 2.0 Dec 23, 1992. 10.4
II. Incompatibilities, Installation, and Space Requirements.
1. Incompatibilities in MXG 10.10 which will cause syntax errors:
a. If these members exist in your USERID.SOURCLIB, then you must

replace them, by re-tailoring your changes starting with the

new MXG 10.10 member:
IMACCICS IMACCIMS IMACCMF IMACDB2 IMACDCOL IMACIMS

IMACINTV IMACMONI IMACNSPY IMACOPC IMACPDSM IMACROSC

IMACSTX IMACTPX IMACZRB IMAC30DD IMAC40DD IMAC434D

These members defined the DDNAME to which MXG sent certain

datasets (eg., MACRO _CICTRAN CICSTRAN % set the DDname for

DATA _CICTRAN.CICSTRAN). The new "_L" architecture provides

the same function with different syntax (eg., now the macro

_LCICTRN defines both the DDNAME (LIBREF) and dataset name).

Change 10.175 provides specific details of what old-names have

to be changed to what new-names for these incompatibly changed

members.
b. If you had tailored BUILDPDB/3 to create TYPETMNT (the MXG

Tape Mount Monitor records), you will need to remove your

tailoring in members EXPDBINC,EXPDBVAR,EXPDBCDE,EXPDBOUT.

In MXG 10.10 TYPETMNT is automatically created by BUILDPDB/3.

Sites migrating to MXG 10.10 from MXG 9.9 thru MXG 10.x should find

no other compatibility issues.

Sites migrating to 10.10 from an MXG version earlier than 9.9 must

read the compatibility section of the installation instructions in

MXG Newsletter TWENTY-ONE (also in member NEWSLTRS).

MXG 10.10 will still execute under SAS 5.18, but this is likely to

be the last version that will fully work under that archaic version

of SAS; MXG intends to begin to exploit Version 6 features in MXG

future versions, and we strongly recommend use of SAS 6.07 or later!

2. Installation and re-installation procedures are described in detail

in member INSTALL, but they are summarized here:
a. Install member MXGSAS as JCL Procedure MXGSAS in your PROCLIB.

b. Allocate a 70-cyl PDS: MXG.V1010.MXG.SOURCLIB, & use IEBUPDTE

to read the MXG tape to create the 1800+ member Source Library.

c. Allocate a 1-cyl PDS: MXG.V1010.USERID.SOURCLIB for your site

"Installation Tailoring" Source Library. Installation specific

tailoring (like telling MXG your shift hours, which performance

groups are TSO, CICS, etc.) is done by copying and modifying MXG

source members into V1010.USERID.SOURCLIB.

d. Allocate a 1-cyl SAS Data Library: MXG.V1010.MXG.FORMATS and

execute SAS to create the library of Formats required by MXG.

Sample JCL for the above three steps is in member JCLINSTL.
e. If re-installing MXG, copy your existing USERID.SOURCLIB library

members into the MXG.V1010.USERID.SOURCLIB. Then examine the set

of IMACs that were changed incompatibly (see member CHANGES).

If any members in MXG.V1010.USERID.SOURCLIB are in that list,

you must reinstall your site's tailoring for that IMAC, starting

with the IMAC member from the MXG 10.10 Source Library.

e. If this is the initial install of MXG, tailor these members into

your MXG.V1010.USERID.SOURCLIB tailoring library:

IMACACCT (Account Length),

IMACSHFT (Shift Definitions),

IMACWORK (Performance Group to Workload mapping), and

IMACSPIN (for BUILDPDB).

Each IMAC member is self-documenting, and IMACAAAA is the index

of all of the IMACs. You should at least scan IMACAAAA to see

the acronyms MXG uses for the many products MXG supports.

f. EDIT and submit member JCLTEST6 (JCLTEST if still on SAS 5.18)

to verify that your tailoring did not create any errors.

g. EDIT and submit JCLPDB to create a Daily PDB for testing. Or

use the TYPE.... members to process specific data sources, use

the ANAL.... members for report examples, the GRAF.... members

for SAS/GRAPH reports.
You have now installed MXG 10.10 in its own set of libraries. When

parallel testing is complete and are ready to implement MXG 10.10

in production, rename your three current MXG Production Libraries

(MXG.MXG.SOURCLIB, MXG.USERID.SOURCLIB, and MXG.MXG.FORMATS) to

(MXG.BACK.MXG.SOURCLIB, MXG.BACK.USERID.SOURCLIB, MXG.BACK.MXG....)

and rename the MXG.V1010.x.y libraries to their Production names!

Again, detailed installation instructions are in member INSTALL

Always read comments in the CHANGES member for compatibility issues, as

well as for any last minute changes.
Whenever you install changes or test a new version of MXG (or even your

own reports), be extra careful to look on the SAS log for any real error

conditions. Search for all occurrences of "ERROR:" and "ERROR :" and

"UNINITIALIZED" and "NOT CATLGD", as they may indicate a serious error.

A PROC PRINT and a PROC MEANS of each new MXG-built SAS dataset can help

you to understand their contents, and should be used to examine any

unusually large, negative, or suspicious values. Print all variables in

the dataset, and read the variable's descriptions in its ADOC member.

III. Documentation of MXG Software.

Member CHANGES always contains the version number of MXG Software, and

it lists changes that were installed in that version. Members named

Changenn are the CHANGES member from MXG Version "nn". Each change in

MXG software is documented by a Change number and text. The text of

each Change identifies the member(s) that were added or altered.

Documentation (especially for new product's support) is often

also found in comments at the beginning of those members listed in the

Change entry. The CHANGE member is designed to be read online (with SPF

BROWSE); you can search for specific product name references (CICS,

MVS/ESA, etc.), or the MXG member name.
Member NEWSLTRS contains the text of all newsletters (up through the

newsletter that accompanied that MXG release). You can search NEWSLTRS

for product name or acronym to find the technical notes, APARs, etc.

from all MXG newsletters. The Change Log pages of each Newsletter are

in member CHANGES or CHANGEnn and are not repeated in member NEWSLTRS.
Member DOCVER lists alphabetically ALL datasets and variables that can

be build by this MXG Software Version. "Delta-documentation" between

MXG versions, which lists only those datasets and variables that were

Changed by version "nn" is found in DOCVERnn members for each version.

Chapter FORTY in the MXG Guide and MXG Supplement books are still the

primary documentation of MXG datasets and their variables (at least for

those data sources that existed in 1987!). This should be the first

place you look for information about MXG variables and/or datasets.

As each section of chapter FORTY is rewritten, it becomes an ADOCxxxx

member of MXG.SOURCLIB, providing online documentation for product xxxx.

ADOCs contain alphabetic descriptions of datasets and variables, the

instructions on how to enable that product, bibliography to the vendor

documentation, sample PROC PRINT and PROC MEANS of real data, and the

MXG member names that you use to process that product, etc. Sounds

great? It will be when finished - this is work in progress!
Beginning with MXG 10.3, there has been an IMACxxxx member for every

product supported by MXG. Once you know the xxxx suffix for a product,

you then know the names of all of the MXG members for that product:
IMACxxxx - Defines record IDs, and "_K,_L" macros for product xxxx.

ADOCxxxx - "Chapter FORTY" style dataset and variable documentation.

VMACxxxx - The "real" code member, often documentation in comments.

TYPExxxx - Standalone member to test or process product xxxx records.

ASUMxxxx - Summarization example (only for some products)

TRNDxxxx - Trending example (only for some products)

ANALxxxx - Reporting/analysis example (only for some products)

GRAFxxxx - SAS/GRAPH report example (only for some products)

EXyyyzzz - OUTPUT exit for each dataset. There can be more than one

dataset per product. The EX member name suffix yyyzzz is

the same as the suffix of "_L" and "_K" macros defined in

IMACxxxx for the product. See further discussion under

"Using the MXG Exit Facilities".
Member IMACAAAA is an index of all IMACs, and is the best place to

begin to find what xxxx suffix Merrill chose for which product!

You can often find additional documentation by searching members

NEWSLTRS, CHANGES, and the CHANGEnn members for the xxxx suffix.

Finally, remember that MXG is source code, so you can often find your

answer by BROWSE/EDIT of the source member, especially the VMACs that

actually create the data set, or ANALs that analyze the MXG data sets.

In most cases, the MXG Variable name is the IBM or Vendor's field or

DSECT field name. In other cases, the DSECT field name is carried as a

comment beside in the MXG INPUT statement to map field name to MXG's

variable name. MXG does expect that you will also have access to the

vendor's documentation of the data records you are processing.

The MXG Technical Newsletter is published aperiodically, one copy per

licensed site, and describes changes and enhancements to the software,

provides APARs and PTFs affecting MXG users, and provides tutorial

information of interest to MXG users.

IX. Change Log

==========================Changes Log=================================
You MUST read each Change description to determine if a Change will

impact your site. All changes have been made in this MXG Library.

Member CHANGES of the MXG SOURCLIB will always be more accurate than

the printed changes in a Newsletter, because the software is created

after the newsletter is sent to the printer!
Member CHANGES always identifies the actual version and release of

MXG Software that is contained in that library.

The actual code implementation of some changes in MXG SOURCLIB may be

different that described in the change text (which might have printed

only the critical part of the correction that can be made by paper).
Scan each source member named in any impacting change for any comments

at the beginning of the member for additional documentation, since the

documentation of new datasets, variables, validation status, and notes,

are often found in comments in the source members.

Alphabetic INDEX of significant changes in MXG 10.10 (since MXG 9.9):

Member Change Description

All 10.175 Powerful new "_L" and "_K" macros tailor MXG datasets

All 10.261 Support for MVS/ESA 4.3.

ADOCAAAA 10.332 Seventy-Three ADOCs documentation members now exist.

ANALDB2R 10.001 DB2 Report truncated character values.

ANALDB2R 10.034 SORTBY= operand parsed only the first SORT variable.

ANALDB2R 10.046 LIBRARY SMF IS NOT VALID message with PMSQL04 report.

ANALDB2R 10.047 DBID/OBID hex values printed instead of name.

ANALDB2R 10.055 Date/time selection in PMSACC01/02 produced no report

ANALDB2R 10.094 ANALDB2R Accounting report uses ASUMDB2A if exists.

ANALDB2R 10.135 DB2 Audit report may not be produced.

ANALDB2R 10.158 DB2 SQL Trace report FORMAT NOT FOUND error.

ANALDB2R 10.272 Buffer Pool statistics average values wrong.

ANALDSET 10.097 VSAM data sets may have wrong PROGRAM name.

ANALMONI 10.066 TMON/CICS sample report filled WORK file.

ANALRMFR 10.301 IBM-formatted RMF reports are now produced by MXG.

ANALRMFR 10.301 IBM's RMF reports produced from MXG datasets.

ASMIMSLG 10.084 Major revision in IMS log processing algorithms.

ASMIMSLG 10.142 Revision to "Appended" IMS log processing.

ASMIMSLG 10.191 "Appended" IMS process might miss RACF segment

ASMISMLG 10.146 New "Appended" IMS log processing works with IMS 2.2.

ASMTMNT 10.012 MXG Tape Mount Monitor supports Dynamic I/O Reconfig.

ASMTMNT 10.136 (MXG 10.1 only). ABEND S55F at startup.

ASMTMNT 10.226 MXG Tape Monitor sets TMNTRTRN=3 for MIM event.

ASMTMNTO 10.177 MXG Tape Mount Monitor for sites still on MVS/XA.

ASMVTOC 10.073 Avoid 213/314 abends reading VTOC of VM/TPF volumes

ASMVTOC 10.157 (MXG 10.1 only). Assembler error MSGAREA.

ASMVTOC 10.202 Use ASMVTOCO for ASMVTOC under MVS/ESA 3.1.3.

ASMVVDS 10.156 ASMVVDS fails with User 666 Abend.

ASUMDB2A 10.090 DB2 Account "transactions" summarized into ASUMDB2A.

ASUM70PR 10.131 PR/SM,MDF,MLPF summarization now supports 16 LPARs.

ASUM70PR 10.218 MXG 10.2 only, corrupted Effective/Management times.

ASUM70PR 10.284 Amdahl MDF LPARNUM=0 now supported, for 17 LPARs.

ASUM70PR 10.335 PCTOFHDW busy in this partition added to RMFINTRV.

BUILDPDB 10.117 BUILDPDB under SAS 6.07 needs changes.

BUILDPDB 10.129 Execution under CMS requires changes.

BUILDPDB 10.153 Step account variable SACCT1 now added to PDB.

BUILDPDB 10.190 JES APAR OY56235 filling SPIN library circumvention.

BUILDPDB 10.298 TOTLINES added to PDB.PRINT dataset.

CMS 10.129 SAS 6.07 under CMS has problems for MXG.

CONFIG07 10.109 Option S=72, s2=72 added to MXG Config members.

EXCICJRN 10.132 New exit for CICS journal data sent to SMF.

EXTY72 10.064 CPURCTTM PTF now exists, circumvention removed.

GRAFxxxx 10.227 SAS 6.07 replaced XSWISS font name with SWISS.

GRAFDB2 10.151 Not all DB2 graphs were produced.

GRAFLPAR 10.052 LPAR CPU utilization reports added.

GRAFTRND 10.049 Graphic trending reports were not always correct.

IMACACCT 10.119 Invalid type 30 subtype 1 SMF caused INPUT STATEMENT.

IMACDB2 10.149 CORRNAME/CORRNUM set from QWHCATYP now.

IMACDOS 10.168 Support for VSE DOS POWER Version 4.2 account records

IMACFACO 10.100 Fujitsu's FACOM MSP/EX SMF records now supported.

IMACFMTS 10.173 Member made archaic by SAS 6.07 FMTSEARCH option.

IMACICSA 10.164 Support for SAP Accounting data in CICS type 110.

IMACICUS 10.297 Optional HOGAN application variables in CICSTRAN.

IMACPDB 10.053 New macro _DB2ACCT added. Compatibility exposure.

IMACPDB 10.068 TAPE3490 (3490s allocated) added to PDB.STEPS/JOBS.

IMACPDB 10.133 PDB.JOBS can have JELPSTM missing when it should not.

JCLPDB6 10.127 (MXG 10.1 only) JCLPDB6 fails, TYPETMNT not found.

JCLTEST6 10.030 INVALID DATA FOR SMFTIME, SAS zap MV313550 required.

MNTH.... 10.091 Trending with INTERVAL=MONTH members added.

MONTHBLD 10.206 All JCLPDB6 PDB & ASUM.... datasets are in MONTHBLD.

MXGSAS 10.336 Example JCL Procedure MXGSAS now provided

READDB2 10.045 TRACECLS= parameter does not select all IFCIDs.

RMFINTRV 10.299 Additional statistics added to RMFINTRV dataset.

TRNDDB2A 10.093 TRNDDB2A Account Trending uses ASUMDB2A if exists.

TTXPDS 10.111 Verstand's TTX product is now included in MXG.

TYPEAICO 10.048 Support for AICorp's KBMS user SMF record.

TYPEAIM6 10.161 Support for FACOM's AIM Version 12 type 116 SMF.

TYPEAPAF 10.078 Support for Amdahl's APAF replacement for MDFTRACK.

TYPEAPAF 10.143 Variable Balance not kept in APAFDOMA

TYPEASTX 10.245 Support for Legent's ASTEX Trace Record

TYPECIMS 10.063 IMF flag variables wrong if multiple bits are on.

TYPECMF 10.230 Boole's CMF variable R783PT in error.

TYPECMF 10.292 Support for IMF Release 2.8.

TYPECTLD 10.327 CONTROL-D Release 2.0.0 is also supported.

TYPECTLD 10.327 CONTROL-D Release 2.0.0 is supported.

TYPEDB2 10.024 MVS Account fields added to DB2ACCT!

TYPEDB2 10.333 DB2ACCT fields ACCOUNTn were not input.

TYPEDB2 10.333 MVS Account fields now are actually input to DB2ACCT!

TYPEDCOL 10.071 INVALID VALUE FOR FUNCTION DATEJUL message.

TYPEDCOL 10.148 DCOLBKUP variables UBALLSP,UBUSESP,UBRECSP wrong.

TYPEDCOL 10.221 DCOLLECT variable UCTOTAL was incorrectly documented.

TYPEDCOL 10.307 DCOLLECT SMSDATA writes SMF constructs records.

TYPEFOCU 10.334 FOCUS record caused INPUT STATEMENT EXCEEDED error

TYPEFTP 10.176 NETVIEW FTP SMF record timestamps reversed.

TYPEF127 10.162 Support for FACOM PDLF Type 127 for MSP/EX Version.

TYPEHIPR 10.300 Support for Empact's HiperCache SMF records.

TYPEHPCS 10.178 Support for HP Unix (HP/UX) PCS Performance Data.

TYPEHPCS 10.294 HP's MPE operating system records now supported.

TYPEHSM 10.080 FSTTRKR/W large values are actually negative values.

TYPEIDMS 10.219 IDMS variable DBKDBKEY was incorrectly documented.

TYPEIDMS 10.265 Support for IDMS Release 12 PM records confirmed.

TYPEILKA 10.121 Invalid data because incorrect offset/documentation.

TYPEIMSA 10.142 STRTTIME/ENDTIME/INPQUETM/SERVICETM/RESPNSTM wrong.

TYPEIMSA 10.205 NMSGPROC value wrong. Must use ASMIMSLG for IMS log.

TYPEIMSA 10.288 Zero service time corrected.

TYPEITRF 10.273 Support for Candle's IMS Trans Report Facility,ITRF.

TYPEMON8 10.020 Landmark CICS "INVALID OFFSETS" message.

TYPEMON8 10.067 MONITASK variables STRTTIME/CREATIME now equal.

TYPEMON8 10.145 Landmark CICS variable TAMRCNT input incorrectly.

TYPEMON8 10.271 Support for Landmark's/CICS Release 9 and Release 1.

TYPEM204 10.120 MODEL204 variable M24IODEV input, EXM24ACT eliminated

TYPENATP 10.033 Support for Software Ag "Natural Process" SMF record.

TYPENETP 10.039 NETPACTM was total response, should be average.

TYPENRS 10.075 Support for The Network Director North Ridge Software

TYPENSPY 10.015 Support for NETSPY Token-Ring records added.

TYPENSPY 10.057 Support for NETSPY Release 4.2 added.

TYPENSPY 10.144 NETSPY type 'N' records cause INPUT STATEMENT EXCEED.

TYPENSPY 10.262 Support for NETSPY Release 4.3 and LANSPY 1.1

TYPENSPY 10.326 NETSPY AHOSTRSP calculation corrected.

TYPEOMCI 10.182 Omegamon V550 ESRA (user) SMF "INPUT EXCEEDED".

TYPEOMVT 10.194 Support for OMEGAMON II for VTAM V150 user SMF.

TYPEOPC 10.112 Major revision for OPC/A log processing.

TYPEOPC 10.204 Support for Changes to OPC records.

TYPEOPC 10.302 RECFM= parameter removed so RECFM=U data can be read.

TYPEORAC 10.291 Support for Oracle 6.0.33.1.51.

TYPEPOOL 10.274 Support for Empact's POOL-DASD user SMF record.

TYPEQAPM 10.110 Support for AS400 V2R1M0 and restructured members.

TYPERMDS 10.102 RMDS messages INVALID DATA FOR RMDSMXVR eliminated.

TYPEROSC 10.022 Support for ROSCOE Release 5.7 changes to SMF data.

TYPEROSC 10.101 ROSCOE ADSFUN.. variables values corrected.

TYPEROSC 10.138 ROSCOE JCK and Documentview added to ROSCOVPE.

TYPERSxx 10.319 Support for RS6000 AIX VMSTAT,IOSTAT,PS commands.

TYPESFS 10.186 Support for XEROX Printer's SFS Status File System.

TYPESIM 10.180 Support for SIMWARE SIM/XFER VTAM user SMF record.

TYPESIM 10.222 SIMWARE initial support revised.

TYPESLRI 10.290 SLR-like IMS log processing for Fast Path.

TYPESMF 10.019 Header/Trailer messages on log were not always right.

TYPESPMS 10.011 SPMS R2.1.4 invalid record circumvented.

TYPESPMS 10.069 SPMS 1.2.13 inserted four byte field, causing errors

TYPESTC 10.105 STC 4400 decode used wrong bits of STC07TYP.

TYPESTC 10.116 STC4400 HSC SMF record for Release 1.2 incompatible.

TYPESTC 10.193 STC 4400 Silo HSC variables formatted.

TYPESTC 10.229 STC 4400 variables LSBECON1/2 incorrectly documented.

TYPESYNC 10.115 SYNCSORT variable COREREQ can be negative.

TYPETCP 10.184 Support for IBM's TCP/IP Version 2 Release 2 SMF.

TYPETIRS 10.181 Support for IBM type 96 SMF record from TIRS.

TYPETMNT 10.200 Legent's MIM corrupts MXGTMNT Tape Mount count.

TYPETMS5 10.060 TMS inactive DSNBs now deleted, caused wrong VOLSER.

TYPETMS5 10.082 TMS.TMS had DSNB fields, TAPEFEET calculation changed

TYPETMS5 10.185 DSNBs could have been skipped.

TYPETMS5 10.196 TMS Billing-by-dataset enhanced in DSNBRECD dataset.

TYPETMS5 10.289 "Dead" tapes no longer create DSNBRECD observation.

TYPETMVS 10.058 TMON/MVS "INVALID DATA for WKLCPURF" message.

TYPETPX 10.007 TPX variable TPXELAP has wrong value.

TYPEVM 10.233 VMSQLxxx datasets enhanced for SQL/DS under VM.

TYPEVMXA 10.036 VM/ESA 1.1.1 additions now supported.

TYPEVMXA 10.071 VM/ESA VXSYTCUP dataset has only 49 observations.