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

EXTY4224 24 and 25, and to subtypes 20, 21, 24 and 25, the fields

EXTY4225 defined by IBM's ICHRUTKN DSECT are added to the record.

EXTY422A These new datasets are created:

EXTY424A DDDDDD DATASET DESCRIPTION

FORMATS TY422A TYPE422A SUBTYPE 21 DELETE MEMBER ALIAS

IMAC42 TY4224 TYPE4224 DFSMS MEMBER ADD/REPLACE ST24

VMAC42 TY42A4 TYPE42A4 DFSMS SUBTYPE 24 DELETE ALIAS

VGETUTKN TY4225 TYPE4225 DFSMS MEMBER RENAME ST25

VMXGINIT These MXG variables are created by VGETUTKN:

Aug 19, 2008 UTKNFLG1='UTKNFLG1*MISCELLANEOUS FLAGS'

Bit values, not (yet?) decoded by MXG:

TOKENCR X'80' TOKEN IS ENCRYPTED

TOKLT19 X'20' TOKEN CREATED BY PRE RACF 1.9 CALL

TOKVXPRP X'10' VERIFYX PROPAGATION OCCURRED

TOKUNUSR X'08' NJE UNKNOWN USER

TOKLOGU X'04' LOG USER INDICATOR

TOKRSPEC X'02' RACF SPECIAL INDICATOR

UTKNFLG2='UTKNFLG2*MISCELLANEOUS*FLAGS'

Bit values, not (yet?) decoded by MXG:

TOKDFLT X'80' DEFAULT TOKEN

TOKUDUS X'40' UNDEFINED USER

TOKERR X'10' TOKEN IN ERROR

TOKTRST X'08' PART OF TRUSTED COMPUTER BASE

TOKSUS X'04' SURROGATE USERID

TOKREMOT X'02' REMOTE JOB INDICATOR

TOKPRIV X'01' PRIVILEDGED USER INDICATOR

UTKNFLG3='UTKNFLG3*MISCELLANEOUS*FLAGS'

TOKDGRP X'80' DEFAULT GROUP ASSIGNED

TOKDSEC X'40' DEFAULT SECLABEL ASSIGNED

TOKNETF X'20' NETWORK NAME SPECIFIED

TOKIPV X'10' IP VALUE FOR SERVAUTH POE

TOKWDWN X'08' WRITE-DOWN IS ALLOWED

UTKNGRUP='SESSION*OWNER*GROUPID'

UTKNLEN ='UTOKEN*RTOKEN*LENGTH'

UTKNNETW='REMOTE*NETWORK*NAME'

UTKNPOE ='PORT*OF*ENTRY'

UTKNPOEX='PORT OF ENTRY*CLASS*INDEX'

Decimal values not (yet?) decoded by MXG:

TOKTERM EQU 1 TERMINAL CLASS

TOKCON EQU 2 CONSOLE CLASS

TOKJESI EQU 3 JESINPUT CLASS

TOKAPORT EQU 4 APPCPORT CLASS

TOKSERV EQU 5 SERVAUTH CLASS

UTKNSCL ='SECLABL'

UTKNSGRP='SUBMITTING*GROUPID'

UTKNSNOD='SUBMITTER*NODE'

UTKNSTYP='SESSION*TYPE'

Decimal values decoded by MGUTKNT format:

1=' 1:SYSTEM ADDRESS SPACE'

2=' 2:COMMAND'

3=' 3:CONSOLE OPERATOR'

4=' 4:STARTED PROCEDURE'

5=' 5:MOUNT'

6=' 6:TSO LOGON'

7=' 7:INTERNAL READER BATCH JOB'

8=' 8:EXECUTION BATCH MONITOR'

9=' 9:RJE OPERATOR'

10='10:NJE OPERATOR'

11='11:VERIFYX UNKNOWN USER TOKEN'

12='12:EXTERNAL READER BATCH JOB'

13='13:RJE BATCH JOB'

14='14:NJE BATCH JOB'

15='15:NJE SYSOUT'

16='16:EXTERNAL XBM'

17='17:RJE XBM'

18='18:NJE XBM'

19='19:APPCTP'

20='20:OMVSSRV'

21='21:IPLOOKUP VALUE'

UTKNSUSR='SUBMITTING*USERID'

UTKNUSER='SESSION*OWNER*USERID'

UTKNVERS='UTOKEN*RTOKEN*VERSION*NUMBER'

UTKNXNOD='EXECUTION*NODE'

APAR OA25068 is the Parent APAR for APAR OA25205, and

this change supports both APAR numbers.

Change 26.186 WPS did not tolerate a FORMAT statement between an END

VMACVMXA and an ELSE IF statement. The FORMAT statement should

Aug 18, 2008 normally have been prior to that END statement in MXG, so

it was relocated to eliminate the WPS-only error.

Change 26.185 Mostly zero observations in TMDBDB2 dataset, because no

EXTMDDB2 one had use the TYPETMDB code to read the native Landmark

IMACTMDB for DB2 records with TYPETMDB code since 2004. Change

VMACTMDB 22.121 corrected MXG handling of DB2 Rollup records for

Aug 16, 2008 IBM DB2 SMF records, but that change had not been applied

to the Landmark DB2 records. This change removed the DO

group in EXTMDDB2 that deleted most observations, added

the logic that creates DB2PARTY='R' for rollups, and also

removed the _TMDBVER macro that is no longer required, as

only Version 4+ records now exist.

Thanks to Charles Savikas, DCF, State of Florida, USA.
Change 26.184 Circumvention for defective SMF 101 subtype 0 record from

VMACDB2 Landmark reconstructed SMF records. Their error is in

Aug 13, 2008 the QPAC segment, which caused INPUT STATEMENT EXCEEDED

error because the offsets to the "truncated" name fields

are less than the QPACLEN value, and the offset should

not have been populated, since the name fields are not

"truncated". In addition, these fields prior to those

offsets are trashed, as the record contains character

text where these numbers are input (but since any text

is a valid PIB value, there was no error, only bad data

values in the DB2ACCP dataset):

QPACAWTK QPACAWTM QPACAWTN QPACAWTO QPACAWTQ

QPACARNK QPACARNM QPACARNN QPACARNO QPACARNQ

The MXG circumvention detects the record is created by

Landmark rather than IBM (by the location of the Product

segment, which Landmark puts at the beginning of the

SMF record, while IBM puts it at the end), and the

data starting at QPACAWTK is not input, so the variables

listed above will be missing, rather than wrong, until

a correction is available from Landmark.

Thanks to Howard Curtis, Progress Energy, USA.
Change 26.183 This change was rescinded by Change 27.039 as wrong.

Aug 13, 2008 The QBAC and QTXA variables have always existed in the

Mar 16, 2009 DB2ACCTP dataset in DB2 V8.1 or later. Change 27.039

restored those variables to the ASUMDB2P and TRNDDB2P

programs. Mar 16, 2009.
Below is the original (AND INCORRECT) change text:

Summary and trending of DB2ACCTP Package Dataset revised.

ASUMDB2P The QBACxxxx and QTXAxxxx variables are always missing in

TRNDDB2P DB2ACCTP (ever since DB2 V7.1, which moved Package Data

Aug 12, 2008 to IFCID 239 (SMF 101 Subtype 1) records, so they have

been removed from both ASUMDB2P and TRNDDB2P summaries.

They can be removed from your DB2ACCTP dataset, but I

can not remove them without risk of causing a failure

if any of your reports reference them in DB2ACCTP.

You can copy this macro definition into your IMACKEEP

member and they will no longer exist in your DB2ACCTP.

MACRO _KDB2ACP

QBACGET QBACSWS QBACRIO QBACSEQ QBACIMW QBACLPF

QBACDPF QBACNGT QBACSIO

QTXACHG QTXACHUS QTXACLMT QTXACLNO QTXACLUN QTXADEA

QTXADRNO QTXADRUN QTXAFLG1 QTXAILMT QTXAIRLM QTXALES

QTXALEX QTXALOCK QTXANPL QTXANRUN QTXAPREC QTXAQRY

QTXARLID QTXASLAT QTXASLMT QTXASLOC QTXASOTH QTXATIM

QTXAUNLK

%

Thanks to Chuck Hopf, Bank of America, USA.

Change 26.182 Support for MACRO4 INSYNC SMF user record creates new

EXINSYDB datasets:

EXINSYDI DATASET DDDDDD DESCRIPTION

EXINSYDS

EXINSYDU INSYDB2 INSYNC DB2

EXINSYZO INSYDBDI INSYNC DB2 - D OR I

EXINSYZC INSYDBDS INSYNC DB2 - SQL TEXT

EXINSYZF INSYDBDU INSYNC DB2 - U

FORMATS INSYZOS INSYNC ZOS

IMACINSY INSYZOSC INSYNC ZOS FORMAT

TYPEINSY INSYZOSF INSYNC ZOS SELECTION CRITERIA

TYPSINSY This is the first iteration and further investigation is

VMACINSY needed with the vendor, as there are invalid SMF records

VMXGINIT (the number of segments exceeds the physical record size)

Aug 13, 2008 and there are unexpected numerous duplicate records that

need to be investigated).

Thanks to Josep Miquel Oliver, La Caixa, SPAIN.
Change 26.181 Accidentally skipped change number

Thanks to Brent Turner, CitiGroup, USA.

Change 26.180 -The circumvention for invalid UWD record to avoid a USER

ASMRMFV ABEND, by skipping over it, is now permanent.

Aug 8, 2008 -Warning RMFV106W was incorrectly issued, and CPD table

entries could be not-processed, but only if GEI records

were selected. The SSH register pointer was not reloaded

but now are.

Thanks to Jerry Urbaniak, Acxiom, USA.
Change 26.179 The typo in VMAC7072 that had a nine-character variable

VMAC7072 ELSE IFAHONRPR=' ';

Aug 8, 2008 is corrected to

ELSE IFAHONPR=' ';

This does not cause an error with MXG's CONFIGV9, which

sets SAS option VALIDVARNAME=V7 to permit long names, but

if the SAS option VALIDVARNAME=V6 is used, error message

VARIABLE NAMED IFAHONRPR CONTAINS MORE THAN 8 CHARACTERS

is printed. The typo was introduced in MXG 26.03.

Thanks to Brian Cummings, Federal Reserve Information Technology USA

Change 26.178 z/OS 1.9 changed length of RMF III ASI segment, adding

VMACRMFV eight bytes, which caused ASICNM (Service Class Name)

Aug 8, 2008 and subsequent ASI variables to be wrong. The added

eight bytes are now decoded and kept in ZRBSI as

ASILMEMO='MEMORY*OBJECTS*ALLOCATED'

ASILPGSZ='LARGE PAGE*BYTES BACKED*IN REAL*STORE'

While ASILPGSZ is in pages in the raw record, MXG has

converted it to bytes and formatted it with MGBYTES to

display that size in KB/MB/etc.

Thanks to Jerry Urbaniak, Acxiom, USA.

Change 26.177 Cleanup of MXG as a result of ITRM Dictionary build:

ASUMTAPE -ASUMTAPE: Dataset HELDMOUN was not deleted from //WORK.

VMXGRMFI -RMFINTRV: New RMFWKLRV dataset had these variables

VMAC85 WKLDCPU WKLDHPT WKLDIFA WKLDIFE WKLDIIP WKLDRCT

VMAC99 WKLDSRB WKLDTCB WKLDZIE WKLDZIP.

Aug 7, 2008 that are now FORMATed TIME12.2;

-TYPE85RE: Variables R85BT R85MT R85RCDY R85TKN R85VT

were unlabeled.

R85BT ='BACKUP*TYPE'

R85MT ='VOLUME*MEDIA*TYPE*OF FROM'

R85RCDY ='DAYS*SPECIFIED*FOR OBJECT*RECALL'

R85TKN ='VOLUME*LOCATION*TOKEN OF*FROM'

R85VT ='VOLUME*TYPE'

-TYPE99: Variable S99BPDTM is FORMATted TIME12.3.

Thanks to Chris Weston, SAS ITRM Development, USA.
====== Changes thru 26.176 were in MXG 26.06 dated Aug 8, 2008=========
Change 26.176 First MXG 26.06 of Aug 6 worked fine on PCSAS but FORMATS

FORMATS failed on z/OS with one specific line in MGTNGVN that is

Aug 6, 2008 to be investigated with SAS Technical Support, but this

iteration split the line and the FORMATS member now does

successfully execute on z/OS and PC SAS.

Thanks to Jerry Urbaniak, Acxiom, USA.

Thanks to Christian Hodel, SWISScom, SWITZERLAND.
Change 26.175 Support for NMON BBBP configuration records creates new

EXNMONBP NMONBBBP dataset. The LSCONF and LPARSTAT-I entries are

IMACNMON stored in variables BBBP001-BBBP047, with their labels

VMACNMON as the identifier of the item.

VMXGINIT

Aug 22, 2008

Thanks to John Keenam, Boeing, USA.
Change 26.174 First MXG 26.06's only. TYPE99_1 DATASET NOT FOUND in

TESTIBM2 JCLTEST8/JCLTEST9 because the TYPE99 code now writes to

VMACNMON //PDB (because the data must be deaccumulated) but the

Aug 5, 2008 TESTIBM2 member had PROC PRINT/PROC MEANS that expected

Aug 6, 2008 those data to be in the //WORK file.

-NMONBBBP By list had ENDTIME, now has STARTIME.

Thanks to Mike Rounceville, Blue Cross Blue Shield of NC, USA.
====== Changes thru 26.173 were in MXG 26.06 dated Aug 4, 2008=========
Change 26.173 Support for Omegamon Tivoli Data Warehouse (TDW) data for

EXSUSELC z/Linux (SUSE 9.3) creates seven new datasets:

EXSUSELE DDDDDD DATASET Description Filename

EXSUSELI SUSELC SUSELCPU SUSE LINUX CPU SUSELCPU

EXSUSELN SUSELE SUSELNET SUSE LINUX NETWORK SUSELNET

EXSUSELP SUSELI SUSELIOE SUSE LINUX IO EXTERNAL SUSELIOE

EXSUSELS SUSELN SUSELNFS SUSE LINUX NFS STATISTICS SUSELNFS

EXSUSELV SUSELP SUSELPRO SUSE LINUX PROCESS SUSELPRO

IMACSUSE SUSELS SUSELSWA SUSE LINUX SWAP RATE SUSELSWA

TYPESUSE SUSELV SUSELVMS SUSE LINUX VM STATS SUSELVMS

TYPSSUSE Comments in member VMACSUSE show how to set up the

VMACSUSE FILENAME statements and then %INCLUDE SOURCLIB(TYPSSUSE);

VMXGINIT

Aug 4, 2008

Thanks to Jim Flanagan, ISO, USA.
====== Changes thru 26.172 were in MXG 26.06 dated Aug 1, 2008=========
Change 26.172 -Support for new NSM data fields NTCACHE, NTLOGICALDISK,

FORMATS NTMEMORY, NTPAGING FILE, NTPHYSICAL DISK, NTPROCESS and

VMACTNG NTSYSTEM datasets.

EXTNT133 -Support for new VMwares objects by Active Dictionary and

EXTNT134 VMware Virtual Center 2.5 Servers, VMware ESX 3.5.5 host

EXTNT135 servers and VM guest servers creates new datasets:

EXTNT136 TNT133 NT133 NSM CA INTERFACE GROUP

EXTNT137 TNT134 NT134 NSM VMWARE VC CLUSTER

EXTNT138 TNT135 NT135 NSM VMWARE VC DATASTORE

EXTNT139 TNT136 NT136 NSM VMWARE VC ESX HOST

EXTNT139 TNT137 NT137 NSM VMWARE VC ESX HOST C

EXTNT140 TNT138 NT138 NSM VMWARE VC ESX HOST D

EXTNT141 TNT139 NT139 NSM VMWARE VC ESX HOST M

EXTNT142 TNT140 NT140 NSM VMWARE VC ESX HOST N

EXTNT143 TNT141 NT141 NSM VMWARE VC EXX HOST P

EXTNT144 TNT142 NT142 NSM VMWARE VC RESOURCE P

EXTNT145 TNT143 NT143 NSM VMWARE VC SERVER

EXTNT146 TNT144 NT144 NSM VMWARE VC VM

EXTNT147 TNT145 NT145 NSM VMWARE VC VM CPU

EXTNT148 TNT146 NT146 NSM VMWARE VC VM DISK

Aug 2, 2008 TNT147 NT147 NSM VMWARE VC VM MEMORY

Aug 4, 2008 TNT148 NT148 NSM VMWARE VC VM NETWORK

Aug 6, 2008 TNT149 NT149 NSM AD EVENTS

Aug 24, 2008 TNT150 NT150 NSM AD PERFORMANCE

TNT151 NT151 NSM AD UTILIZATION

TNT152 NT152 NSM DNS

TNT153 NT153 NSM FILEREPLICACONN

TNT154 NT154 NSM FILEREPLICASET

TNT155 NT155 NSM NTDS

Added Aug 24 in 26.07:

TNT156 NT156 NSM VMWARE VC COMPUTE RE

Thanks to Michael Kynch, International Paper, USA.

Change 26.171 Protection so that ANALDB2R doesn't fail with USER=PDB.

ANALDB2R While USER=PDB is dis-recommended for BUILDPDB, and has

VMXGINIT caused errors with other programs, this change protects

Aug 2, 2008 but ONLY for ANALDB2R. DO NOT USE OPTIONS USER=PDB.

Thanks to Herbert Sweeney, Verizon Data Services Inc, USA.
Change 26.170 Circumvention for zero length VBS record in OPC Log file.

VMACOPC

Jul 31, 2008

Thanks to Andrew Davis, Produban, ENGLAND.

Change 26.169 Circumvention for 24 byte PRCAPM segment.

VMACXAM

Jul 29, 2008

Thanks to Tony Curry, BMC, USA.

Change 26.168 Support for DB2 SMF 102 IFCID=342 adds these variables:

VMAC102 QW0342TY ='DATABASE TYPE'

Jul 29, 2008 QW0342AT='AGENT TOKEN'

QW0342CI='CURRENT*INDEX*SPACE*USAGE'

QW0342CT='CURRENT*TABLES*SPACE*USAGE'

QW0342DB='DATABASE*DBID'

QW0342MI='MAXIMUM*INDEX*SPACE*USAGE'

QW0342MT='MAXIMUM*TABLES*SPACE*USAGE'

QW0342PS='TABLE/INDEX*SPACE*PSID'

QW0342PT='PARENT TOKEN'

Thanks to Steven Olmstead, Northwestern Mutual, USA.
Change 26.167 Debugging version for invalid UWD record segments will

ASMRMFV avoid the USER ABEND and write defective records to the

Jul 29, 2008 //RMFSKIP DD (which needs to be added). ASMRMFVX, delete.

Thanks to Robert Carballo, Office Depot, USA.

Change 26.166 Support for AS/400 Version 6 Release 1 adds 3 variables

VMACQACS to the QAPMDISK dataset:

Jul 29, 2008 DSSECT ='DISK*UNIT*SECTOR*SIZE'

DSIOARN ='STORAGE*ADAPTER*RESOURCE*NAME'

DSSRLN ='DISK*UNIT*SERIAL*NUMBER'

and new variable to QAPMCONF dataset:

GDESXP ='PM*AGENT*DATA*OBTAINED?'

Thanks to David Bixler, FISERV, USA.

Change 26.165 A new "RMF Interval - WORKLOAD " dataset RMFWLKRV is now

EXRMFWKL also created when RMFINTRV is created; the new dataset

VMXGRMFI contains only the workload variables from RMF72, but

Jul 26, 2008 with one observation per workload, and only one set of

variables created, making workload analysis much easier.

The RMFWKLRV dataset has the same interval duration that

you chose for your RMFINTRV dataset; these are the

variables and labels in the new PDB.RMFWKLRV dataset:

DURATM DURATION*OF*INTERVAL

STARTIME START OF*INTERVAL

SYSNAME SYSNAME*FROM*IEASYSXX

SYSPLEX SYSPLEX*FROM*IEASYSXX

SYSTEM SYSTEM*ID

WKLDACTV WORKLOAD*ACTIVE*TIME

WKLDCPU WORKLOAD*CPU*TIME

WKLDDESC WORKLOAD*DESCRIPTION

WKLDEXCP WORKLOAD*EXCP*RATE

WKLDFRTM WORKLOAD*FRAME*TIME

WKLDHPT WORKLOAD*HPT*TIME

WKLDID WORKLOAD*ID

WKLDIFA WORKLOAD*IFA*PROCESSOR*TIME

WKLDIFE WORKLOAD*IFA*ELIGIBLE*PROCESSOR*TIME

WKLDIIP WORKLOAD*IIP*TIME

WKLDIOTM WORKLOAD*IO*CONNECT*TIME

WKLDMEMR WORKLOAD*MEMORY*USAGE

WKLDPGIN WORKLOAD*PAGEIN*RATE

WKLDRCT WORKLOAD*RCT*TIME

WKLDRESD WORKLOAD*RESIDENT*TIME

WKLDRESP WORKLOAD*AVG*RESPONSE

WKLDSERV WORKLOAD*SERVICE*UNITS

WKLDSRB WORKLOAD*SRB*TIME

WKLDSVRT WORKLOAD*SERVICE*RATE

WKLDSWAP WORKLOAD*SWAP*RATE

WKLDTCB WORKLOAD*TCB*TIME

WKLDTRAN WORKLOAD*TRANSACTIONS

WKLDTRRT WORKLOAD*TRANSACTION*RATE

WKLDWKST WORKLOAD*WORKING*SET

WKLDZIE WORKLOAD*ZIP*ELIGIBLE*PROCESSOR*TIME

WKLDZIP WORKLOAD*ZIP*PROCESSOR*TIME

Thanks to Don Goulden, SAS ITRM Development, USA.

Change 26.164 For the JES3 PDB, i.e., BUILDPD3, variable JOBCLASS was

BUIL3005 not kept from the SMF 30 subtype 1 and subtype 5, causing

Jul 26, 2008 it to be blank in some cases. It is now kept in both.

Aug 12, 2008 Additionally, it is now correctly kept as 8-bytes in the

PDB.SMFINTRV dataset, as well as being non-blank.

Thanks to Keving McCandlish, IBM Global Services, USA.

Thanks to Scott Barry, SBBWorks, Inc, USA.
Change 26.163 Support for TPF PUT22 changes, and corrections to current

VMACTPF code.

Jul 21, 2008 New variables added by PUT22:

Dataset TPFDX:

DXNSDIN DXLMTRKS DXLMRSTT DXTSWB DXMODL DXCRYP

Dataset TPFSX:

SX4KFRMS

Corrections:

-The first SLOTNR was always re-read for all eight slots,

so dataset TPFMG never had data from the 2nd-8th slots.

-STARTIME was not populated for TPFMG dataset.

-The INPUT of SPXDISA1-4 and SPXRTRA1-4 were relocated to

the end of the SPX record; those variables were always

wrong until now.

Thanks to Bob Wilcos, EDS, USA.
Change 26.162 Reserved Change Number.

Jul 21, 2008

Change 26.161 New variable BESKEY='TAPE*ENCRYPTION*KEY*INDEX' is added

TYPETMS5 to dataset TMS to identify CA-1 encrypted tapes. This is

VMACTMS5 a reference/index into the CA Tape Encryption Data base

Jul 21, 2008 where the actual keys are stored, and it allows TMS to

determine when a key is no longer needed and can be

retired; TMS scans for non-scratch tapes that reference

a key, and if none are found for a specific index, that

key can then be safely retired.

Thanks to Jeff Harder, Indiana Farm Bureau, USA.
Change 26.160 Support for Omegamon User SMF records in SMF 112.

VMAC112 See Change 25.257, which replaced this text.

VMACOMCI

Jul 20, 2008

Thanks to Art Cuneo, Blue Cross Blue Shield of Illinois, USA.
Change 26.159 TYPE77 QUEUE1 thru QUEUE4 were wrong and could be GT 100.

VMAC77 The correct denominator TOT77QUE=SUM OF (QUEUE1-QUEUE4)

Aug 13, 2008 is now used to calculate those percentages, and is kept.

The calculation of Average Queue Length now matches IBMs

reports, using AVG77QUE=WAITS/TOT77QUE, where WAITS is

SMF77AQL, the total waiting requests, and new TOT77QUE

is the total number of waiters.

New variable RNAMEHEX is the printable hex value of the

first MINORQCB bytes of RNAME, so those RNAMEs that have

hex values can be seen when printed as plain text.

Thanks to Chuck Hopf, Bank of America, USA.
Change 26.158 Cosmetic, but confusing. PDB.TYPE70 offline zip/zap

VMAC7072 engines had CAIxx='20'x instead of '00'X, had PCTIFBYx

Jul 17, 2008 and PCTZIPBx both 100%, had IFAWAITx and ZIPWAITx both 0,

and IFAWAITM and ZIPWAITM were also both zeros if all of

the zIIP and zAAP engines were offline during interval.

The IFAUPTM and ZIPUPTM were both correct (missing) when

all of these engines were offline. the NRIFAS and

NRZIPCPU variables still count the number of engines

available to this MVS system, even when all are offline.

Thanks to Christine DeClercq, Dexia, BELGIUM.

Change 26.157 Change 26.115 made consistent the BY lists for RMF sorts,

MONTHASC but only for the first three common variables. The

MONTHBL3 TYPE70 sort order was still inconsistent between BUILDPDB

MONTHBLD and WEEKBLD/MONTHBLD. Now, those combining jobs all have

MONTHBLS been updated to match the BUILDPDB order, which is:

MONTHDSK SYSPLEX SYSTEM SYSNAME SMF70GIE GMTOFFTM STARTIME

MONTHWEK

WEEKBL3D

WEEKBL3T

WEEKBLD

WEEKBLDD

WEEKBLDT

Jul 15, 2008

Thanks to Tom Kelman, Commerce Bank of Kansas City, USA.

Change 26.156 Hex variable FSRDORG is decoded in new character variable

VMACHSM FSRDSORG using the same logic used for DCOLLECT, except

Jul 15, 2008 that DCOLLECT provides bits to identify PDSE vs PDS.

Thanks to James J. Byrnes, ???, ???

Change 26.155 Support for SMF 99 Subtype 11 (Group Capacity Limits)

EXTY99BG creates two new datasets:

EXTY99BS DDDDDD DATASET SUBTYPE DESCRIPTION

IMAC99 TY99BG TYPE99BG 99-11 CAPACITY GROUP

VMAC99 TY99BS TYPE99BS 99-11 SERVICE DATA

VMXGINIT

Jul 23, 2008

Thanks to Scott Chapman, American Electric Power,USA.

Change 26.154 If an offline LPARNUM preceded this PARTISHN, SMF70LAC

VMAC7072 was missing in PDB.TYPE70PR and PDB.ASUM70LP/PDB.ASUMCELP

Jul 10, 2008 and the corresponding LPnLAC in PDB.ASUM70PR/PDB.ASUMCEC.

Thanks to Barry T. Mueller, RiteAid, USA.

Change 26.153 -Using ANALRMFR from MXG 26.01+ with PDB=PDB where that

ANALRMFR input PDB was created with an earlier MXG version caused

Jul 18, 2008 a series of error messages that variables suffixed Y, Z,

ZA ... are missing; those new variables for CPs up to 64

were expected by ANALRMFR; rerun with PDB=SMF to correct.

-ERROR: NO DATA SET OPEN TO LOOK UP VARIABLES corrected;

caused by hardcoded TYPE70SP instead of _WTY70SP.

-Updated to support 64 CP engines.

Thanks to Bill Cheng, Toyota, USA.
Change 26.152 New utility to remove duplicate SMF records from VBS data

UNDUPSMF file.

Jul 9, 2008

Thanks to Larry Stahl, IBM Global Services, USA.

Change 26.151 Support for APAR OA24416, which corrects overflow in

VMAC28 GBLCRPSA by adding a four byte "high part" at the end of

Jul 8, 2008 the 'D6'x NPM record.
Change 26.150 A typo caused the values of three SPG variables to be

VMACRMFV one tenth of their true value; the three variables

Jul 6, 2008 SPGTOTSP SPGFRESP SPGLGBLK are now multiplied by the

correct value of 1048576 instead of 104856.

Thanks to Roger Rush, Navistar, USA.
Change 26.149 Protection so that if SMF 21s and TYPETMNT were not added

UTILBLDP ASUMTAPE, ASUMTMNT and ASUMTALO are NOT included, but if

Jul 6, 2008 TYPETMNT is created, the ASUMTMNT and ASUMTALO are.

Thanks to Charles Savikas, State of Florida, USA.

Change 26.148 Enhancement to ASMTAPEE/MXGTMNT's capture of SYSLOG info,

ASMTAPEE now at ML-43 with this change, some revisions to ASUMTAPE

ASUMTAPE processing logic that improves the accuracy of several