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

Apr 1, 2018 time resolution, but the divide by 4096 produced false

digits in 3rd and 4th place that, coupled with these

very large 2-complement numbers, cause MXG to falsely

detect a break in deaccumulation. See also 36.052.

Change 36.061 Invalid SYTNLPS value in SYTCUP records prevented their

VMACXAM output; pending Velocity fix, SYTNLPS=(SEGLEN-28)/20; is

Mar 20, 2018 used to calculate the actual number of segments.
Change 36.060 Support for BMC Extended Buffer Manager XBM SMF Record.

EXXBMDS -The Data Set Statistics Record can have seven OIDs:

EXXBMCA OID Variables Segment

EXXBMCC 113 xbmDSSnn Dataset Statistics

EXXBMCE 113 xbmSDSnn Snapshot Data Set Statistics

EXXBMCS 154 xbmDB2nn DB2 Statistics

IMACXBM 158 xbmSUSnn Snapshot Utilities Statistics

TYPEXBM 199 xbmVSAnn VSAM Statistics

TYPSXBM 272 xbmEPSnn Extended Prefetch Statistics

VMACXBM 242 xbmIMSnn IMS Statistics

VMXGINIT and all seven segments are output in XBMDSET dataset.

Mar 21, 2018 DDDDDD Dataset Description

XBMDS XBMDSET XBM Data Set Record

(Only the first four OID's have been data-validated).

-The Cache Statistics Record can have four OIDs,

1 xbmCSSnn Configuration Start Section

2 xbmCEEnn Configuration End/Stop Section

3 xbmCCCnn Configuration Change Statistics

106 xbmCACnn Cache Statistics Section

and each is output in a separate dataset:

DDDDDD Dataset Description

XBMCA XBMCACHE XBM Cache Record

XBMCS XBMCSTRT XBM Configuration Start

XBMCE XBMCEND XBM Configuration End

XBMCC XBMCHG XBM Configuration Change

Thanks to Flavio Lima, MetLife, USA.

Change 36.059 -If you specified USERADD=ID a CHAR OPERAND FOUND IN %EVAL

UTILBLDP error indicated that a numeric was needed, which was due

Mar 21, 2018 to the compiler interpreting %STR(/VIEW=ID) as a formula.

Resolved by using %QUOTE rather than %STR, like the other

references in UTILBLDP.

-The SMF AUDIT report was not being produced, now is.

Change 36.058 Missing %END in PMAUD02 corrected and BEGTIME and ENDTIME

ANALDB2R parameters enabled for MXGDB2B1 report. MXG 36.02 only,

Mar 23, 2018 introduced by Change 36.048.

Thanks to Randy Hewitt, DXC, USA.

Change 36.057 Support for z/OS 2.3 RMF Changes (SHARE Sacramento 2018):

EXTY748S -Support for APAR OA53411 for more than 65535 devices adds

FORMATS SMF74SMF bit and populates existing SMF74LSN with a flag

IMAC74 when multiple logical SMF records were created, but these

VMAC7072 variables are not kept, and don't impact MXG's reading of

VMAC74 the individual physical SMF records; the variables are

VMXGINIT available in the EXTY74 exit, if ever of interest.

Mar 26, 2018 -Support for APAR OA50760 72.3/4, was in Change 35.125.

-Support for APAR OA50761 74.10, was in Change 35.273.

-Support for APAR OA52694 72.3 TYPE72TR+ in Change 36.050.

-Support for APAR OA50762 74.9 new bit existing R749FLAG.

-Support for APAR OA50693 70.2 CEX6C/CEX6A/CEX6P Crypto

updated $MGRMFCX/$MGRMFCY/MGRMFCZ formats.

-Support for APAR OA50755 74.1 was in Change 35.193.

-Support for APAR OA50755 74.9 was in Change 35.146.

-Support for APAR OA53411 adds 74.5 vars to TYPE74CA.

R7451SRR='SYNC I/O*CACHE*READ*REQUESTS'

R7451SRH='SYNC I/O*CACHE*READ*HITS'

R7451SWR='SYNC I/O*CACHE*READ*REQUESTS'

R7451SWH='SYNC I/O*CACHE*READ*HITSS'

-Support for APAR OA53411 74.8 adds new Synchronous I/O

Link Statistics Segment that creates new TYPE748S data

set with these variables:

R748SIID='SYNC*I/O*INTERFACE*ID'

R748STYP='SYNC*I/O*LINK*TYPE'

R748SSPD='SYNC*I/O*LINK*SPEED'

R748SWDH='SYNC*I/O*LINK WIDTH*LANES'

R748SSTE='SYNC*I/O*LINK*STATE'

R7451INC='BYTES*TIME*INDETERMINABLE'

R748SCBR='SYNC I/o*CACHE*BYTES*READ'

R748SCro='SYNC I/o*CACHE*READ*OPERATIONS'

R748SCRS='SUCCESSFUL*CACHE*READ*OPERATIONS'

R748SCRT='SYNC I/o*CACHE*READ*TIME'

R748SCBW='SYNC I/o*CACHE*BYTES*WRITE'

R748SCWO='SYNC I/o*CACHE*WRITE*OPERATIONS'

R748SCWS='SUCCESSFUL*CACHE*WRITE*OPERATIONS'

R748SNBW='SYNC I/O*CACHE*WRITE*TIME'

R748SNWO='NVS*BYTES*WRITTEN'

R748SNWS='NVS*WRITE*OPERATIONS'

R748SNWT='NVS*WRITE*TIME'

-Support for APAR OA51913, z14 physical core addresses

greater than 191, was protected in MXG 31.04, which

supports the maximum possible value of 255, even though

z/OS doesn't even support 191.

-Support for Jan 2018 SMF Manual and APAR OA52003 that

added these variables to TYPE74ST Structure dataset:

R744SIAD R744SADN R744SIXC R744SXSC R744SXST R744SXSQ

R744SADO R744SADR R744SQCH R744SXFL R744SWDR R744SWAC

R744SRDR R744SRAC R744SWEC R744SREC R744SWED R744SWES

R744SRED R744SRES

R744SIAD R744SADN R744SIXC R744SXSC R744SSXT R744SXSQ

R744SADR R744SQCH R744SXFL

R744SWDR R744SWAC R744SRDR R744SRAC R744SWEC R744SREC

R744SWED R744SWES R744SRED R744SRES

-Support for Jan 2018 SMF Manual which added to TYPE74DU:

R744RSST R744RIDP R744RCPI R744RCPN R744RSGS R744RSA1

R744RSA2 R744RSA3 R744RSA4 R744RSA5 R744RSA6 R744RSA7

R744RSA8 R744RSID R744RSC R744RAMC R744RAMS R744RAMS

R744RAMP R744RAMN
Change 36.056 zHyperwrite enables DB2 to perform parallel log writes to

VMAC74 PPRC primary and secondary volumes, but they are the same

VMAC79 4-hex-digit DEVNR, and because they can be concurrently

Mar 15, 2018 active, RMF Reports now display 5-hex-digit DEVNR, with

the first nybble containing the SubChannel ID, 'sdddd'X,

where the SubChannel ID is 0,1,2 or 3. No change was made

to the SMF 74/79 records, as the SubChannel ID is already

in those records, and the 5-hex-digit display is only in

RMF reports/data: they won't exist in other SMF records.

MXG variable DEVNR5HEX is created in TYPE74, TYPE74CA,

TYPE748 and TYPE796 as DEVNR5HEX=65536*SMF74SCS+DEVNR

with FORMAT DEVNR5HEX HEX5. format.

Change 36.055 New TYPE8231 dataset was misaligned and the VMXGINIT for

VMAC82 _WTY8231 thru _WTY8247 was corrected to write to WORK

VMXGINIT rather than to PDB.

Mar 13, 2018 -Mar 20: Invalid Subtype 31 with only 4 bytes for 0203 TAG

Mar 20, 2018 encountered, circumvented, and reported to IBM.

Apr 12, 2018 -Apr 12: MXG's problem was that the SMF82_TRIPL_LENGTH

field was presumed to be the length following it, but it

was 8 with when 4 bytes remained, so I presumed there was

truncated data for the TAG 0203 segment. IBM Support

responded with a very detailed decoding of the record

with their utility that matched MXG's values, concluding:

"To sum up, the length of 08 that you are referencing

does not mean that 8 bytes will follow. It means the

length in the record is composed of the length of the

data item (4 bytes) plus the length of the tag and

size info (another 4 bytes)."

While TAGs have different lengths, since each TAG's

length is fixed, MXG did not need to use that field,

so no MXG code change was required, and no data was

truncated.

Thanks to Andreas Menne, Finanz Informatik, GERMANY.

Thanks to David A. Hilliard, IBM Support, GERMANY.

Change 36.054 A missing paren caused BLDSMPDB to fail, and %macro

BLDSMPDB &PDBPATH was not initialized in PDBAUDIT. BLDSMPDB only

PDBAUDIT failed when MTD was used which then caused SAS to set

Mar 13, 2018 OBS=0 and caused PROC SQLs in PDBAUDIT to then fail.

PDBAUDIT is now protected for the 0 OBS case

Thanks to Harold Zbiegien, American Greetings, USA.

Change 36.053 INTBTIME and INTETIME variables are now all DATETIME25.6

BUIL3005 formatted, even though only those INPUT with TODSTAMP8

BUILD005 will have all six decimals populated, SMFSTAMP informat

SMFINTRV only has 2 decimals. INTETIME in SMF 91 with TODSTAMP8

VMAC30 informat forced the format change, since you can't have

VMAC91 different formats for the same variable name in datasets

Mar 8, 2018 created in the same DATA step.

Thanks to Randy Hewitt, DXC, USA.

Change 36.052 Revision to z/VM VXBYUSR logic to correct large values

VMACVMXA in many deaccumulated durations when there were multiple

Mar 7, 2018 logon values in CALTODON for the same user, and/or when

a guest has been relocated. Logic to recalculate DELTATM

from HFRATE*HFQCNT was causing output of first instances,

so it was removed. A heuristic was added to test that

the record DELTATM was not more than 2*INTERVAL since

that also detects a return of a relocate to delete.

See Change 36.062.

Thanks to Graham Harris, RBS, ENGLAND.

Change 36.051 Support for AS/400 Version 7.3 Collection Services.

VMACQACS -New GDES fields added to QAPMCONF dataset for keys

Mar 7, 2018 FL PM TY TZ T1 T2 T3 T4 U1 U2 U3 U4 XS

Mar 16, 2018 -New DATETIMECH,UTCTIMECH 26-character datetimes and

Mar 23, 2018 DSQUEOPS counter added to QAPMDISK record, which now

Mar 26, 2018 has LRECL=751 (YOU MUST SET IN YOUR JCL/FILENAME).

See change 36.065.
====== Changes thru 36.050 are in MXG 36.02 dated Mar 5, 2018=========
Change 36.050 TYPE72GO variables R723CPA_ACTUAL and R723CPA_SCALING

VMAC7072 added by APAR OA52694, were trashed because they were

Mar 2, 2018 input when they shouldn't have been; the test for INPUT

Mar 6, 2018 should have been GE 276 instead of repeated GE 268.

Mar 6: New variable ORG70CPA was added to TYPE70 and

TYPE70PR, but the label statement had OGT70CPA causing

a harmless UNINIT variable message on the log.

Thanks to Al Sherkow, I/S Management Strategies, Ltd.

Change 36.049 Change 35.200 left off the trailing / or ] on the

VGETALOC directory names if you did not supply it and it could

Mar 2, 2018 result in no allocations and a failure of a following

VMXGSET. Now if we don't find the / or \ we supply it.

Thanks to Richard Krueger, Sentry, USA.
Change 36.048 For PMAUD02 report SORTBY use is restored, but the first

ANALDB2R variable in the list must be QWHSSSID, and variables not

Mar 2, 2018 in the below list will terminate with error messages.

The default values are QWHSSSID QWHSSTCK; if that first

variable is not DB2 or QWHSSSID, QWHSSSID is inserted.

Allowed variables are:

DB2 - THE DB2 SUBSYSTEM ID

PLAN - THE DB2 PLAN NAME

AUTHID - THE AUTHORIZATION ID

CONNID - THE CONNECTION ID

CONNTYPE - THE CONNECTION TYPE

CORRID - THE CORRELATION ID

QWHSSSID - THE DB2 SUBSYSTEM ID

QWHCPLAN - THE DB2 PLAN NAME

QWHCAID - THE AUTHORIZATION ID

QWHCOPID - THE ORIGINAL AUTHORIZATION ID

QWHCCN - THE CONNECTION ID

QWACATYP - THE CONNECTION TYPE

QWHCCV - THE CORRELATION ID

QWHSSTCK - THE TIME OF THE EVENT

Thanks to Scott Swindling, PREMERA, USA.
Change 36.047 Support for XCOM Version 12.0 (COMPATIBLE) adds variables

VMACXCOM XCOMGWDP='GATEWAY*DPATH'

Feb 28, 2018 XCOMSSLT='SSL*VERSION'

XCOMCIPHN='SSL*CIPHER*NAME'

XCOMRCNT='RESTART*COUNT'

XCOMPLEXQ='ORIGIN*PLEXQ*GROUP*NAME'

Thanks to Alfredo Antonio Gonzalez Ortega, ITNOW, SPAIN

Thanks to Sergi Vilaseca Punti, ITNOW, SPAIN

Thanks to Miguel Fco. Monferrer Carvajal, ITNOW, SPAIN
Change 36.046 Support for NDM Version 5.2 corrects NDMCPU and adds

VMACNDM these variables to the NDMCT dataset:

Mar 1, 2018 NDMCLASS ='PROCESS*SESSION*CLASS'

Apr 6, 2018 NDMCTFLAG17='FASP17*OVERRIDE*TO FASP=NO'

NDMCTFLAG18='FASP18*OVERRIDE*TO FASP=NO'

NDMCTGPF ='GENERAL*PURPOSE*FLAG'

NDMDBLKSZ ='DESTINATION*BLKSIZE'

NDMDDSORG ='DESTINATION*DSORG'

NDMDLRECL ='DESTINATION*LRECL'

NDMDRECFM ='DESTINATION*RECFM'

NDMFASPBW ='FASP*BANDWIDTH*KBITS'

NDMFASPFT ='FASP*FILESIZE*THRESHOLD'

NDMFASPPL ='FASP*POLICY'

NDMPNRLS ='PNODE*C:D*VERSION'

NDMSBLKSZ ='SOURCE*BLKSIZE'

NDMSDSORG ='SOURCE*DSORG'

NDMSLRECL ='SOURCE*LRECL'

NDMSMFID ='SMFID*THAT*CREATED'

NDMSMRLS ='SNODE*C:D*VERSION'

NDMSRECFM ='SOURCE*RECFM'

NDMSTEPOS ='STEP*OFFSET*IN*TCQ'

NDMUSERN='USER*SENSE*FROM*FMH71'

NDMXDATE ='PROCESS*STOP*DATE'

NDMXTIME ='PROCESS*STOP*TIME'

NDMZFLAG='Z*FEATURE*FLAGS'

NDMZWINR ='COMPRESSION*WINDOW*SIZE'

-Apr 6: Reported Truncated CERI and CERT to IBM.

-Apr 16: IBM APAR PI24126 corrects the truncation,

but makes no mention of the truncation. That fix

required reassembly of DGMSMF.

Thanks to Heimir Hauksson, Barclays Technology Center, ENGLAND.

Thanks to Robert Richards, OPM, USA.

Thanks to Walter J Freeman, OPM, USA.

Thanks to Otto A. Burgess, OPM, USA.

Change 36.045 Support for enhanced Mobile Work 4HOUR MSU reporting.

FORMATS -New parameter, TYPE=, for the type of mobile work, to

MOBMWRT be added to your %MOBMWRT invocation in your MOBWRKxx

MOBWRK72 tailored members, where TYPE=DB2 CICS IMS WAS or MQ to

MOBWRK73 create the WORK.MWRT_BLD_SUM_&TYPE dataset that is then

MOBWRKMS used to create the new MOBILE.MSU_&TYPE dataset with the

Feb 28, 2018 4 hour rolling average MSU for that &TYPE of workload.

-MOBWRKMS provides reporting on the new &TYPE datasets.

-Some improvements in SMF70CPA calculation in MOBWRK73,

and ORIGCPUTM/CPUCPONLY/CICDSCPUTM are init to missing

in MOBWRK72.

-FORMAT mwrtdt is enhanced to support years beyond 2042.

Thanks to Al Sherkow, I/S Management Strategies, Ltd.
Change 36.044 The value you set in MACRO _IMSVERS mm.n % is now kept

VMACIMS in variable IMSVERS in IMS0708 and IMS07 datasets.

Mar 1, 2018 (The IMS56FA transaction dataset already has IMSVERSN

that is created from that IMS log record.)

Thanks to Alfredo Gonzalez, La Caixa, SPAIN.
Change 36.043 Initial support for NMON Nigel's Monitor for RHEL Release

EXRHELAA 14i with Red Hat Enterprise Linux 6.7.

EXRHELBP The data with 1 second interval is suspect as the times

EXRHELCI of the interval are often 2 or 3 seconds apart.

EXRHELME The developers page is at 'http://nmon.sourceforge.net'

EXRHELNS The BBBP fields are not currently decoded since the RHEL

EXRHELCD text is not consistent with the NMON contents.

EXRHELDS -Mar 6: FULLCOMD in RHELUARG expanded to 4096 bytes and

EXRHELIN WORK dataset CPUBUSY is deleted; the values of CPU_ALL

EXRHELJF variables are output in RHELINTV Interval Dataset.

EXRHELNT

EXRHELTO DDDDDD MXG MXG

EXRHELUA DATASET DATASET DATASET

EXRHELMT SUFFIX NAME LABEL

IMACRHEL

TYPERHEL RHELAA RHELAAA RHEL MONITOR AAA CONFIGURATION

TYPSRHEL RHELBP RHELBBBP RHEL MONITOR BBBP CONFIGURATION

VMACRHEL RHELCI RHELBBBPCPUINFO RHEL BBBP CPUINFO

VMXGINIT RHELME RHELBBBPMEMINFO RHEL BBBP MEMINFO

Mar 1, 2018 RHELMT RHELBBBPMOUNT RHEL BBBP MOUNT

Mar 6, 2018 RHELNS RHELBBBPNETSTAT RHEL BBBP NETSTAT

Mar 14, 2018 RHELCD RHELCPUD RHEL CPU DETAIL

Mar 28, 2018 RHELDS RHELDISK RHEL DISK

Apr 6, 2018 RHELIN RHELINTV RHEL MONITOR INTERVAL

RHELJF RHELJFSF RHEL JFSFILE

RHELNT RHELNETW RHEL NETWORK

RHELTO RHELTOP RHEL TOP PROCESS

RHELUA RHELUARG RHEL UARG PROCESS

-Apr 6: RHELAAA now output for each concatenated input

file; only the first was output previously.

Thanks to Harald Seifert, HUK-COBURG, GERMANY.

Thanks to Andreas Windisch, HUK-COBURG, GERMANY.

Change 36.042 ANALCAPD ERROR: FOUND "IF" when expecting ... when the

ANALCAPD CEC= options was used, due to a missing semicolon.

Feb 22, 2018

Thanks to Norbert T. Wagner, Deutsche-Boerse, GERMANY.

Change 36.041 The MXGERROR:MISSING TYPE70 message is now MXGWARN:MISS

VMXG70PR because it's only an alert to be examined (Change 36.026)

Feb 20, 2018 to see if the SYSTEMs listed are the systems of interest.

Only variables in dataset ASUMCELP observations for those

LPARs whose 70s were not read are impacted, and in many

cases the message is generated because the SMF data from

a sandbox LPAR was not present in that day's SMF input.

Thanks to Ed Wieszczek, Zions Bank Corporation, USA.

Change 36.040 Support for IMS 56FA Record APAR UI50912. COMPATIBLE as

VMACIMS it uses a reserved field for the new TPCEXTOF offset to

Feb 19, 2018 the TPCE DSECT, but TPCEXTOF is zero so the extension

is not populated by THIS APAR, so it is also not input.

Thanks to Heimir Hauksson, Barclays, ENGLAND.
Change 36.039 Enhancement to dataset TYPE70PR creates new LPARZIPS with

VMAC7072 the number of online ZIIP engines for each LPAR for each

Feb 19, 2018 interval.

Thanks to Kurt Gramling, TSYS, USA.

Change 36.038 The MXG "INVALID SMF 119 TYPE 81" message in MXG 36.01

VMAC119 bypassed an INPUT STATEMENT EXCEEDED LENGTH ERROR ABEND,

Feb 19, 2018 but I had misunderstood the DS_DOOFF offset to be the

offset into the SMF buffer to the DORU field; IBM L3

Support corrected me: it is the offset into the RU that

will be moved into the DORU field, if the DORU is larger

than 4096 bytes, so that the anomaly's data will be in

in the SMF record. The circumvention is removed and the

DORU variable is correctly populated.

-Variable IST119DS_SID was changed from numeric to char

with $HEX16. format.

Thanks to Gary Zaetz, IBM z/OS Communications Server Support, USA.

Thanks to David Campbell, SUNTRUST, USA.
Change 36.037 Variable QWHSACE was missing from the BY list for dataset

VMACDB2 ZZDB2SBP causing READDB2/TYPEDB2/BUILDPDB to ABEND with

Feb 19, 2018 INPUT STATEMENT EXCEEDED. This code has been executing

and accidentally working since MXG 35.10, last year,

before two site's data records with multiple QWHSACEs

exposed my coding error.

Thanks to Lori A Stratford,The Auto Club Group AAA Michigan, USA.

Thanks to Kare Martin Torsvik, IBM Services, NORWAY

Change 36.036 Support for new Subtype 31 SMF 82 JOB-level crypto stats.

EXTY8228

EXTY8229

EXTY8230

EXTY8240

EXTY8241

EXTY8242

EXTY8243

EXTY8244

EXTY8245

EXTY8246

EXTY8247

IMAC82

VMAC82

VMXGINIT

Feb 14, 2018

During testing of this update, Error Message UNDECLARED

ARRAY YPE8231 (note T is missing) was caused by VMXGINIT

typo setting PTY8231=DEFAULT instead of setting WTY8231.

Just a developers note as for that " YPExxxx" error text

shows up in testing from time to time.
Change 36.035 If the last engine type in an LPAR was an IFL, the MXG

VMAC7072 calculation of LPARSHAR/LPARSHAC and LZIPSHAR/LZIPSHAC

Feb 14, 2018 was incorrect in the TYPE70 dataset.

Thanks to Andrew Petersen, DXC, AUSTRALIA.

Change 36.034 Some debugging options added when MXGEXIMSG=YES and a bad

VGETOBS branch to end modified so that if the dataset you seek

Feb 14, 2018 does not exist and debugging is on you will get the

message that it did not exist.

Change 36.033 Analysis of different I/O counts between SMF 42 subtype 6

ANAL4274 and type74 subtype 1.

Feb 13, 2018
Change 36.032 WebSphere INVALID Subtype 9 messages were cause by the

VMAC120 absence of ELSE clauses that are now corrected.

Feb 12, 2018

Thanks to Jim Horne, Lowe's, USA.

Change 36.031 INVALID DB2 RECORD CREATED BY ASG/TMON is NOT an ASG

VMACDB2H issue, but rather is due to BMC APPTUNE SMF 102 records

Feb 11, 2018 with Data Sharing Group sections that were incorrectly

decoded by MXG logic, now corrected. The ERROR is real

in that observations were NOT output in some datasets.

Thanks to Jan Tielemans, KBC, BELGIUM.

Change 36.030 Old-style substitution macro _HSMINTV added so you can

ASUMHSM easily change the default HOUR interval to you choice.

Feb 6, 2018 If you want the interval to be QTRHOUR and the final

output written to dataset HSM.QTRHOUR, you would use:

%LET MACKEEP=%QUOTE(

MACRO _LSUHSM HSM.QTRHOUR % /* SETS OUTPUT DSN */

MACRO _HSMINTV QTRHOUR % /* SETS INTERVAL */

);

%INCLUDE SOURCLIB(ASUMHSM);

Thanks to Randy Hewitt, DXC, USA.
Change 36.029 Variables SM120RULEXFBOM/DEB/MON/FTRC are one-bit fields

VMAC120 that MXG incorrectly INPUT as one-byte variables.

Feb 8, 2018

Thanks to Paul Volpi, UHC, USA.

Thanks to Jack Hyde, UHC, USA.
Change 36.028 Change 35.124 introduced code that stopped PDBAUDIT with

PDBAUDIT a memory limitation problem with WPS when more than 20

Feb 8, 2018 LIBNAMEs were found. Change 35.201 then accidentally

circumvented that error by removing duplicate entries,

but the real error was that DICTIONARY.MEMBERS returned

all libname.member entries, (THOUSANDS in MXG QA JOB),

rather than the LIBNAME entries from DICTIONARY.LIBNAMES.

The error message is inactive.

Thanks to Earl Kline, Luminex, USA.
Change 36.027 More invalid LENSR=304 and 448 for SMF 42 Subtype 5;

VMAC42 IF LENSR IN(232,240,320,400,448,480) THEN LENSR=160;

Feb 8, 2018 The line was also moved up to after the DO because

those large values with lots of SR segments caused the

MXG test for INVALID SR Length exceeds record length.

The correcting APAR number is OA54663, but it did not

acknowledge the multiplicity of incorrect values when

it "Updated SMF42SRL to contain only length of SMF4205A".

Thanks to Luis Mendoza, Black Knight, USA.

Thanks to Lori A Stratford,The Auto Club Group AAA Michigan, USA.

====== Changes thru 36.026 are in MXG 36.01 dated Feb 6, 2018=========
Change 36.026 MXGERROR:MISSING TYPE70 RECORDS impacts ASUMCEC/ASUMCELP

VMXG70PR datasets, with some incorrect values in those datasets

Feb 5, 2018 when those messages are printed, not just SMF70LAC, when

either the data from a system is not input, or if your

LPARNAME/SYSTEM/SYSNAME/SMF70STN names are inconsistent.

Change 35.144 introduced the message and provided a way

if your SMF70STN matches LPARNAME, but you may need the

below logic to create consistent names.

%LET INCODE70FOR70PR=%QUOTE(

LENGTH SMF70STN $8;

IF SYSNAME='ZUT1ACP1' THEN SYSTEM='ACP1';

ELSE IF SYSNAME='ZUT1DEV1' THEN SYSTEM='DEV1';

ELSE IF SYSNAME='ZUT1PRD1' THEN SYSTEM='PRD1';

IF SYSNAME='ZUT1ACP1' THEN SYSNAME='ACP1';

ELSE IF SYSNAME='ZUT1DEV1' THEN SYSNAME='DEV1';

ELSE IF SYSNAME='ZUT1PRD1' THEN SYSNAME='PRD1';

IF SMF70STN='ZUT1ACP1' THEN SYSTEM='ACP1';

ELSE IF SMF70STN='ZUT1DEV1' THEN SYSTEM='DEV1';

ELSE IF SMF70STN='ZUT1PRD1' THEN SYSTEM='PRD1';

IF SMF70STN='ZUT1ACP1' THEN SMF70STN='ACP1';

ELSE IF SMF70STN='ZUT1DEV1' THEN SMF70STN='DEV1';

ELSE IF SMF70STN='ZUT1PRD1' THEN SMF70STN='PRD1';

IF SYSNAME='ZUT1ACP1' THEN SYSTEM='ACP1';

ELSE IF SYSNAME='ZUT1DEV1' THEN SYSTEM='DEV1';

ELSE IF SYSNAME='ZUT1PRD1' THEN SYSTEM='PRD1';