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

TRANCOST PIB4. /*transmission*cost*/

@;

Thanks to John Astle, National Australia Bank, AUSTRALIA.

Change 11.031 TYPE37 LAND segment has 2 fields after BRFDNADR that were

VMAC37 not documented in NETVIEW Admin Reference Manual but are

Apr 13, 1993 in IFASMFR macro and are now INPUT by MXG:

BRFSMADR $CHAR6. /*single mac address*/

BRFSMNAM $CHAR16. /*single mac name*/

Additionally, several variables are now formatted:

BRFALTID $HEX8.

BRFDNADR BRFSMADR BRFLMADR BRFRMADR BRFUPADR $HEX12.

Thanks to Wanda Prather, Johns Hopkins Applied Physics Lab, USA.
Change 11.030 Variable DSIVTOC in the KEEP= list was misspelled, and it

VMXGVTOF should be changed to DS4IVTOC.

Apr 13, 1993

Thanks to Pino Todesco, Western Australia Police, AUSTRALIA.

Change 11.029 NSPYACCT variable SNITIME is incorrect because DSNIMM was

VMACNSPY used for both the month and the minutes. Change DSNIMM to

Apr 13, 1993 DSNIMO in the INPUT for month, in the IF statement and in

the MDY function calculating SNITIME.

Thanks to Aubrey Tang, Government Insurance Office, AUSTRALIA
Change 11.028 TCP/IP address variables FPTLCLAD,FTPRMTAD,TELLCLAD and

VMACTCP TELRMTAD are four-byte character fields, which display

Apr 12, 1993 as $HEX8: "8681800C"x for example. However, TCP/IP users

expect these to be displayed as decimal values separated

by periods: 134.129.128.12 for the above value. Four new

address variables FTPLOCAL,FTPREMOT,TELLOCAL,TELREMOT are

now created with the expected format, using this logic:

INFORMAT FTPLOCAL $15.;

FTPLOCAL=PUT(INPUT(SUBSTR(FTPLCLAD,1,1),PIB1.),3.)

!!'.'!!

PUT(INPUT(SUBSTR(FTPLCLAD,2,1),PIB1.),3.)

!!'.'!!

PUT(INPUT(SUBSTR(FTPLCLAD,3,1),PIB1.),3.)

!!'.'!!

PUT(INPUT(SUBSTR(FTPLCLAD,4,1),PIB1.),3.);

Thanks to Sharon Jacobson, North Dakota Higher Education, USA.

Change 11.027 Variable LP0MGTTM was left out of the RETAIN list. Since

ASUM70PR LPAR=0 is only used by Amdahl's MDF, only those sites

Apr 6, 1993 need add LP0MGTTM to the RETAIN statement.

Thanks to Tom Parker, Hogan Systems, USA.

Change 11.026 The test IF OFFPRCS+LENPRCS*NRPRCS GT LENGTH+1 THEN DO;

VMAC7072 should be NRPRCSS vice NRPRCS, but as this is insurance

Apr 6, 1993 for a bad record, there's no real impact.

Thanks to Tom Parker, Hogan Systems, USA.

Change 11.025 You can create the PDB on tape with BUILDPDB, but it is

PDB to tape not normally recommended because it takes too long due to

Apr 6, 1993 rewinds (after the PDB.TYPE70s are written, they are read

back in to create RMFINTRV). It is much more efficient to

point the PDB DDname to a temporary DASD file, create the

PDB, and then use a PROC COPY IN=PDB OUT=PDBTAPE; to build

your PDB on tape. If you simply do not have enough temp

DASD for the PDB library, you can write the PDB directly

to tape, but you will need to tailor members IMACCICS,

IMACDB2, and EXPDBOUT. The instructions for tailoring

IMACCICS are contained in comments in that member. In

member IMACDB2, you must remove the "PDB." qualifier for

the DB2 datasets in the "_L" macro definitions, and then

in member EXPDBOUT you must add PROC COPY IN=WORK OUT=PDB;

SELECT DB2: ; if you want the DB2 datasets in your PDB

library.
Change 11.024 RMF-like reporting failed if PDB=SMF was specified, but

ANALRMFR works if PDB=PDB is used. This correction is extensive,

Apr 6, 1993 and a replacement member is available upon request. Also,

LET REQUEST should have been %LET REQUEST.
Change 11.023 Omegamon V550 creates invalid type 110 record, which MXG

VMAC110 detects and deletes, with a VMAC110.ERROR.1 message (with

SECTLLBB=0, TEMPLEN non zero, and LENGTH=32400) on the SAS

Apr 5, 1993 log. Candle's fix QOC0451 was the original fix for their

Aug 30, 1993 error, but in August fix QOC0534 superceded QOC0451.

This noted added June 20, 1994: Same error has occurred

with LENGTH=32320 instead of 32400, same fix.

Thanks to Khin Zaw, Nordstrom, USA.

Thanks to Andrew Lockyer, South Wales Electricity Board, WALES.
Change 11.022 If you have some MVS systems under PR/SM and some not and

ASUM70PR if you invoke ASUM70PR after BUILDPDB, your PDB.RMFINTRV

Apr 5, 1993 dataset may have missing data for some systems, because a

BY statement was missing. Change 10.335 added logic to

re-write PDB.RMFINTRV and add PLATBUSY/PLATCPUS variables

from ASUM70PR dataset, but the BY statement for the MERGE

was left out. If all systems are under PR/SM, then there

will be equal observations in ASUM70PR and PDB.RMFINTRV,

and the BY statement is not required, but if only some of

your systems are PR/SM, RMFINTRV is corrupted. To correct,

you must insert BY SYSTEM STARTIME; after the statement

MERGE TEMPINTV (IN=RMF) PLATBUSY (IN=INPRSM);

Thanks to Steve Clausing, Employers Health, USA.
Change 11.021 The new TYPE42DS (SMS data set statistics, subtype 6) has

FORMATS GMT values in SMF42PTE and SMF42PTS in the INTERVAL record

VMAC42 but MXG expected local values (as are in CLOSE record).

Apr 4, 1993 Correct by inserting these lines after the "@;" that

follows the input of variable LENJDIOL:

IF INTVCLOS=1 THEN DO; /* INTERVAL RECORD */

GMTOFF42=100*FLOOR((SMFTIME-SMF42PTE)/100);

SMF42PTE=SMF42PTE+GMTOFF42;

SMF42PTS=SMF42PTS+GMTOFF42;

END;

STARTIME=SMF42PTS;

ENDTIME =SMF42PTE;

DURATM =SMF42PTE-SMF42PTS;

Unrelatedly, the values for S42DSTYP are now decoded by

new format MG042DS., which has these values:

0='0:OTHER' 16='16:KSDS DATA'

1='1:PS' 17='17:KSDS INDEX'

2='2:PDS' 18='18:VARIABLE RRDS DATA'

3='3:PDSE' 19='19:VARIABLE RRDS INDEX'

4='4:DA' 20='20:FIXED LENGTH RRDS'

5='5:ISAM' 21='21:LINEAR DATA SET'

6='6:EXCP' 22='22:ESDS'

Change 11.020 ASTEX variable RMLFLAG2 was added to the KEEP= list of

VMACDMON DMONVOL data set, but it does not exist in the VOL record!

Apr 4, 1993 Instead, it should have been added to the KEEP= lists for

the DMONJOBS and DMONDSN datasets.

Thanks to John Rosza, Depository Trust Company, USA.
Change 11.019 The DIFFHSM member (which deaccumulates the HSM data) did

DIFFHSM not use the "_L" macro names. Each PROC SORT now has the

Apr 4, 1993 syntax of PROC SORT DATA= _LHSMxxx OUT=HSMyyyyy using

member IMACHSM to match the xxx with the yyyyy strings.

Thanks to Sudman Arik, Bezeq, ISRAEL.
Change 11.018 SAS Boolean bit tests of 32-bit strings does not work, as

VMAC30 Usage note V6-SYS.DATA-6047 discusses. The 32-bit test of

Apr 4, 1993 SMF30MFL has been replaced with IF SMF30MFL='1.......'B

and the SMF30MFL PIB4. input was replaced with

SMF30MFL PIB1. +3 to cause IOTMERR to be correctly set.

Thanks to G. W. Shanks, British Rail, ENGLAND.

Change 11.017 New TYPE80A fails with INPUT STATEMENT EXCEEDED if the

VMAC80A LOGSTR= string is more than 16 bytes (my default length).

Apr 3, 1993 I thought that SAS would skip over the extra data with:

RACFDLNN=MAX(16,RACFDLN);

INPUT LOGSTR $VARYING16. RACFDLNN @;

but it doesn't work that way, causing this error! Those

lines in the WHEN (46) clause must be replaced by these:

WHEN (46) DO;

IF RACFDLN GT 32 THEN DO;

SKIP=RACFDLN-32;

INPUT LOGSTR $CHAR32. +SKIP @;

END;

ELSE DO;

INPUT LOGSTR $VARYING32. RACFDLN @;

END;

END;

Note that I also increased LOGSTR's default length to $32.

Thanks to Diane Eppestine, Southwestern Bell, USA.

Change 11.016 TYPE72MN contains only one PERFGRP from each type 72 RMF

VMAC7072 subtype 2 record, because MXG assumed one record for each

Apr 3, 1993 PERFGRP, but there are multiple PERFGRP segments in each

record. Subtype 2 processing logic was restructured

significantly. In addition, MXG logic was changed so that

TYPE72MN is output only if VALDSAMP GT 0 (i.e, actual

samples exist for this workload). Note that there can be

multiple observations with the same PERFGRP value in an

interval, because TYPE72MN contains a segment for each

combination of PERFGRP and DOMAIN. A replacement VMAC7072

member with this change is available upon request.

Thanks to Mike Skopec, Platinum Technology, USA.

Change 11.015 Change 10.259 implemented IBM APAR II06736 2nd algorithm

VMAC73 but that algorithm is wrong! As a result TYPE73 contains

Apr 3, 1993 an observation for every CHPID from 00 to FFx! Only the

1st algorithm (test SMF73VLD for valid CHPID) can be used

to discard dummy CHPID entries. The statement

IF CHANIND GT 0 OR CHANINDX GT 0 OR CHANINDY GT 0 OR

PCHANBY GT 0 OR SMF73PBY GT 0 OR SMF73PTI GT 0 THEN DO;

is now replaced with

IF VALIDPTH='Y' THEN DO;

Also, the CTC bit is now decoded to set CHANTYPE='CTC' if

the CHPID is actually a CTC, and CHANTYPE is now reset:

IF CHANIND ='..1.....'B THEN CHANTYPE='BLOCK MUX';

ELSE IF CHANIND ='...1....'B THEN CHANTYPE='BYTE MUX';

ELSE IF CHANINDY='.1......'B THEN CHANTYPE='CTC';

ELSE CHANTYPE=' ';

Thanks to Tom Parker, Hogan Systems, USA.

Thanks to Diane Eppestine, Southwestern Bell, USA.
Change 11.014 The JCL for installation example has a UNIT= coded twice

JCLINSTL in the third step. Use either the UNIT=3380 or UNIT=3390,

Apr 3, 1993 but remove the UNIT=SYSDA from that JCL example.

Thanks to Mark Robbins, Jaguar Cars, ENGLAND.

Change 11.013 Change 10.175 documents how to use the new "_L" and "_K"

DOC macros, but the paragraph beginning 'The "_L" macro lets

Mar 28, 1993 you ...', (first paragraph on page 67 of Newsletter 23)

has two occurrences of _KTY0 that should have been _LTY0.

Thanks to Ron Becham, Southern California Edison, USA.
Change 11.012 JCLTEST with SAS 5.18 has failed at 2 sites with the old

JCLTEST "data set WORK.#DIRMACR is out of space" condition that is

Mar 28, 1993 discussed in Change 8.025 (but neither site used IMACKEEP)

and my SAS 5.18 JCLTEST does not fail! Splitting TESTIBM

into two pieces will circumvent the problem, but since it

only occurs in JCLTEST, it can be ignored. (The primary

purpose of JCLTEST6 is to verify your MXG format library

was correctly built, and that your IMAC tailoring did not

cause a syntax error. Since JCLTEST got to TYPE74, both

sites knew they had tested the important IMACs, so they

proceeded to run JCLPDB, which did not fail. This does

not apply to SAS Version 6 - use JCLTEST6 and JCLPDB6 and

this 5.18 error does not occur!
Change 11.011 FOCUS SMF record 12-byte reserved field FOCUFRS0 was

VMACFOCU changed to @69+OFFSMF FOCUSRV $CHAR8. @77+OFFSMF

Mar 17, 1993 FOCUFRS0 $CHAR4. , and FOCUSRV was labeled 'FOCUS*SERVICE'

and added to the KEEP= list. The value of new variable

FOCUSRV is "FOCUS" in the data observed thus far!
Change 11.010 Dataset TYPETSWP (tape swaps from MXG Tape Mount Monitor)

BUILDPDB is created in the WORK file by BUILDPDB, but was not then

BUILDPD3 sorted into the PDB library. After the BY statement for

Apr 3, 1993 the PROC SORT NODUP DATA=TYPETMNT OUT=PDB.TYPETMNT ...,

replicate that PROC and BY statements, change TYPETMNT to

TYPETSWP, and change the BY statement to read

BY SYSTEM SHIFT DEVFROM TSWPTIME;

Additionally, in the PROC DATASETS following these sorts,

add TYPETMNT and TYPETSWP to the DELETE statement.

Thanks to Tracy Blackstone, Kaiser Permanente, USA.

Change 11.009 NETSPY "Invalid argument to function DATEJUL" might occur

VMACNSPY with NSPYREC='U' because STOPTIME fields TMEE/DTEE added

Apr 3, 1993 by NETSPY R4.3 used previously reserved fields that are

non-zero in R4.2! DTEE is input as packed decimal, and if

the non-zero value happens to end with Fx or Cx, the error

occurs. To correct, find the following statement (it is

the first "IF DTEE" test, 21 lines after the DO group test

for NSPYREC='S' or 'T' or 'U'):

IF DTEE GT 0 THEN STOPTIME=DHMS(DATEJUL(DTEE),0,0,TMEE);

and change it to read:

IF NSPYREL GE 'R4.3' AND DTEE GT 0 THEN

STOPTIME=DHMS(DATEJUL(DTEE),0,0,TMEE);

Thanks to Bob Butchco, The Genix Group, USA.

Thanks to Norbert Korsche, OMV-AG, AUSTRIA.

Change 11.008 MXG 10.10 only, and only if you write type 74 RMF records

RMFINTRV for tape devices. If so, RMFINTRV variables DEVACTTM,

Apr 3, 1993 DEVCONTM DEVDISTM, DEVPNDTM and AVGRSPMS include both DASD

and TAPE statistics (instead of DASD-only), due to Change

10.299. To correct RMFINTRV, find "SIO74CNT=.;", and then

insert this line after that line:

DEVACTTM=.;DEVCONTM=.;DEVDISTM=.;DEVPNDTM=.; AVGRSPMS=.;

Thanks to Tom Parker, Hogan Systems, USA.

Change 11.007 Using ANALDB2R with PDB=SMF failed when accounting report

READDB2 were suppressed and statistics reports were not. Using

Apr 3, 1993 PDB=PDB does not fail. The error is in READDB2, which is

invoked by ANALDB2R when PDB=SMF is specified. Change the

line (this is the third and last test for LENGTH(&PDBOUT):

%IF %LENGTH(&PDBOUT) NE 0 %THEN %DO;

to read:

%IF %LENGTH(&PDBOUT) NE 0 AND &NUMIFC GT 0 %THEN %DO;

Thanks to Ed Lau, Lucky Stores, USA.
Change 11.006 DB2STAT0 variable QDSTQDBT is incorrectly input. There's

VMACDB2 two occurrences of OFFQJST=OFFQJST-3+OFFSMF; but the last

Apr 3, 1993 one should have been OFFQDST instead of OFFQJST.

Thanks to Tom Parker, Hogan Systems, USA.

Change 11.005 DB2ACCT records cause "INVALID 3rd ARGUMENT IN SUBSTR"

VMACDB2 error because account fields were not protected for zero

Apr 3, 1993 length fields. In addition, variable JOB is blank.

Delete the statement JOB=' '; (just before %INCLUDE for

IMACACCT) to prevent blank JOB name. To protect for zero

length account fields, the nine statements of the form

ACCOUNTn=SUBSTR(QMDAACCT,BEG,LENACCTn);

must each be changed to read

IF LENACCTn GT 0 THEN

ACCOUNTn=SUBSTR(QMDAACCT,BEG,LENACCTn);

where n=1,2,...9.

Thanks to Tom Parker, Hogan Systems, USA.

Change 11.004 TYPE30 variable DSSIZHWM incorrectly changed by Change

VMAC30 10.261, and is much too large. Change the multiplier from

Mar 28, 1993 16777216 to 1048576.

Thanks to Tom Parker, Hogan Systems, USA.

Change 11.003 MVS/ESA 4.3 only. TYPE30_V and PDB.SMFINTRV timestamps

VMAC30 INTBTIME and INTETIME were not converted from GMT to local

Apr 3, 1993 time correctly (however, SMFTIME is valid and can be used

to approximate the interval end local time until this

change is made). Change INTBTIME-SMF30IST to read instead

SMF30IST-INTBTIME.

Thanks to Jim Nissen, Principal Financial Group, USA.
Change 11.002 Processing VSAM SMF type 30 records can produce "INVALID

VMAC30 OMVS TRIPLET" message and no observations in TYPE30xx data

Apr 3, 1993 sets. The three lines reading "IF OFFPROD-3-COL GE ...."

must be changed to "IF OFFPROD-3+OFFSMF-COL GE ...." if

you want to process VSAM SMF data directly. There is no

error in processing SMF data which has been dumped.

Thanks to Jonathan E. Paley, Massachussets Mutual, USA.
Change 11.001 Type 37 can cause INPUT STATEMENT EXCEEDED RECORD LENGTH

VMAC37 error.

Apr 3, 1993 First, replace the following eight lines:

Apr 27, 1993 IF OFFSELD GT 0 AND NRSELD GT 0 THEN DO;

SUBSTR(FND37OFF,9,1)='S';

OFFLAND=OFFLAND-3+OFFSMF;

INPUT @OFFLAND

BRFTEXT $CHAR200. /*SELF DEFINING*TEXT*MESSAG*/

BRFTEXTA $CHAR75. /*SELF DEFINING*TEXT*MESSAG*/

@;

END; /* END SELD SECTION TYPE 37 */

with the following twelve lines (note that the first three

lines are unchanged):

IF OFFSELD GT 0 AND NRSELD GT 0 THEN DO;

SUBSTR(FND37OFF,9,1)='S';

OFFSELD=OFFSELD-3+OFFSMF;

INPUT @OFFSELD @;

IF LENSELD GE 275 THEN INPUT BRFTEXT $CHAR200.

BRFTEXTA $CHAR75. @;

ELSE IF 201 LE LENSELD LT 275 THEN DO;

SKIP=LENSELD-200;

INPUT BRFTEXT $CHAR200. BRFTEXTA $VARYING75. SKIP @;

END;

ELSE INPUT BRFTEXT $VARYING200. LENSELD @;

END; /* END SELD SECTION TYPE 37 */

Second, in the "IF OFFDETT GT 0 ..." DO group that follows

the above "IF OFFSELD GT 0 ..." DO group, change all three

occurrences of OFFLAND to OFFDETT.
Third, the INPUT of OFFDETT must be PIB4. instead of PIB2.
Thanks to Larry Doub, R J Reynolds Tobacco USA.

Thanks to Rod Fernandes, Albert Heijn B.V., HOLLAND.

LASTCHANGE: Version 11
=========================member=CHANGE10================================

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

This is the Production MXG Version 10.10, dated March 15, 1993.
Changes through:

Change 10.336 are included in MXG Version 10.10, Mar 15, 1993

Change 10.323 were printed in Newsletter TWENTY-THREE, Mar 15, 1993

Change 10.304 are included in MXG PreRelease 10.6, Feb 23, 1993

Change 10.265 are included in MXG PreRelease 10.5, Jan 28, 1993

Change 10.251 are included in MXG PreRelease 10.4, Jan 8, 1993

Change 10.241 are included in MXG PreRelease 10.3A, Dec 17, 1992

Change 10.235 are included in MXG PreRelease 10.3, Dec 13, 1992

Change 10.208 are included in MXG PreRelease 10.2, Oct 18, 1992

Change 10.199 were included in Early PreRelease 10.2, Oct 12, 1992

Change 10.113 were included in MXG PreRelease 10.1, Jul 10, 1992

Change 10.104 were printed in Newsletter TWENTY-TWO, Jul 10, 1992

Table of Contents:
I. MXG Software Status and Enhancements:

II. Incompatibilities, Installation, and Space Requirements.

III. Documentation of MXG Software.

IV. MXG Technical Notes - see NEWSLETTER TWENTY-THREE

V. MVS Technical Notes - see NEWSLETTER TWENTY-THREE

VI. VM Technical Notes - see NEWSLETTER TWENTY-THREE

VII. CICS Technical Notes - see NEWSLETTER TWENTY-THREE

VIII. SAS Technical Notes - see NEWSLETTER TWENTY-THREE

IX. Change Log

I. MXG Software Status and Enhancements:

MXG 10.10 is the Production Version of MXG 10 (i.e., the version that

we "Produce" for all sites), dated March 15, 1993.

MXG 10.10 is a major revision, with many latent enhancements, and near

transparent installation. Sites with normal MXG tailoring should need

less than 2 hours to unload, tailor, and submit the test jobstreams.

Make sure you read the COMPATIBILITY warning in Installation notes.

These enhancements are in MXG 10.10, but were not printed in the MXG

Technical Newsletter number TWENTY-THREE:

Note: There are 1965 members in MXG 10.10, not the 2000+ I thought

there would be. MXG now creates 47,292 variables in 1195 data

sets with its 533,759 lines of source code.
Support for type 30 OpenEdition/MVS measurements

NETSPY Average Host Response calculation corrected

Major enhancements added in MXG 10.10, that were not in MXG 10.6:
Support for OpenEdition MVS, OMVS, RMF record enhancements.

Preliminary RS6000 AIX VMSTAT,IOSTAT,PS command processing

GMT offset, GMTOFFTM, available in MVS/ESA 4.3 RMF records.

DCOLLECT options SMSDATA creates nine new SMS construct datasets.

RMF reports can be produced from MXG TYPE70xx datasets.

Additional online MXG documentation members (ADOC and ACHAP).

Major enhancements added in MXG 10.6, that were not in MXG 10.5:
Support for Empact's Hipercache SMF record.

Support for IMF Release 2.8.

Support for Oracle 6.0.33.1.51.

Support for IBM 3495 Tape Library Dataserver's type 94 SMF record.

Support for (incompatible) Omegamon/CICS DATACOM SPE PTF QOC0109.

Support for STOPX37 Release 3.5.

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

Support for Candle's IMS Transaction Reporting Facility, ITRF.

Support for Landmark for CICS's Release 9 and Release 1.0.

IBM-like RMF reports can be created with new ANALRMFR.

Additional HOGAN application fields added in CICSTRAN

HP's MPE data or HP/UX Unix data are both supported by TYPEHPCS

SLR-like IMS processing for sites with heavy fast-path in TYPESLRI

Additional CMF "type 240" subtypes supported in TYPECMF

Major enhancements added in MXG 10.5, that were not in MXG 10.4:
Support for MVS/ESA 4.3 and RMF 4.3.

Support for NPM Release 1.6.

Support for NETSPY Release 4.3 and LANSPY 1.1.

Support for IDMS Release 12 PM records confirmed.

Major enhancements added in MXG 10.4, that were not in MXG 10.3:
Support for ESCOM Multi-Image Facility (EMIF)

Support for VM/ESA 2.0

Validation of support for Velocity Software's XAMAP History files.
Major enhancements added in MXG 10.3, that were not in MXG 10.2:
Support for NPM 1.5.1 incompatible changes.

Correction of MXG-10.2-only error in ASUM70PR

Support for DFSORT Release 12 new fields.

Cleanup of all reported errors in prior prereleases.

Toleration support for VM/ESA 2.0 MONWRITE data.
Major enhancements added in MXG 10.2:
Powerful new "_L" and "_K" macro architecture allows full tailoring

of MXG datasets (variables kept/dropped, compression, blocksize,

the DDNAME to which the dataset is written, etc.).

Support for DB2 Trace IFCID 172/ 177 added, Audit/SQL reports fixed.

Support for FACOM AIM Version 12 type 116 SMF record changes.

Support for FACOM PDLF Type 127 for MSP/EX.

Support for HP Unix (HP/UX) PCS Performance Collection System data

Support for IBM TCP/IP Version 2 Release 2 SMF record.

Support for IBM TIRS type 96 SMF record coded.

Support for Network Alert APAR OY49717 in SMF Type 37.

Support for OMEGAMON II for VTAM V150 user SMF record coded.

Support for OPC changes.

Support for SAP Accounting data in CICS type 110 or journal file.

Support for SIMWARE SIM/XFER VTAM user SMF record.

Support for TMS Billing-by-dataset using enhanced DSNBRECD dataset.

Support for VSE DOS POWER Version 4.2

Support for Xerox Printer's SFS Status File System records.

Support for XCOM 6.2 Version 2.2.2G SMF record.

Alert that Legent's MIM can corrupt MXG Tape Mount counting.

"Appended" IMS Log enhancements; has now been tested with IMS 2.2.

Continued enhancement of ANALDB2R for DB2 reports.
Major enhancements added in MXG 10.1 but not listed in Newsletter 22:
OPC/A log processing major revision, additional datasets created.

Verstand's product, TTX, is now included in MXG Software.

Support for AS400 V2R1M0 added, and AS400 support was revised.

NPM 1.5.1 subtypes 144-150 (NPMEVX25 dataset) errors were corrected.

Sample IEFU83 exit to filter type 40 records for tape-only added.
Major enhancements added in MXG 10.1 that were listed in NL 22:
Required for CICS/ESA 3.3,

Required for VM/ESA 1.1.1,