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

are often found in comments in the source members.

Alphabetical list of important changes in MXG 25.06 after MXG 24.24:

Dataset/

Member Change Description

Many 25.140 Support for z/OS 1.9 (COMPAT, minor SMF additions).

Many 25.179 %UPCASE,%LOWCASE,%STR,%BQUOTE,%QUOTE, etc.

ADOCDB2 25.172 Example to process DB2 datasets to separate DDNAMES.

ADOCDB2 25.148 Doc. How to create DB2ACCTB/DB2ACCTP in separate DDs.

ADOCITRM 25.149 Doc. Maps ITRM dataset names to MXG name.

ANALACTP 25.254 Sample report summarizes DB2 Package data to UOW.

ANALDB2R 25.202 VARIABLE QBnTDPIO NOT FOUND error corrected.

ANALDB2R 25.189 New PDBOUT=YES, old PDBOUT= changed, writes to WORK.

ANALDB2R 25.068 SQL Text QW0141TX was not printed, coding error.

ANALFIOE 25.026 Divide by zero message protected.

ANALRMFR 25.146 ERROR: NO DATASETS TO LOOKUP correction.

ANALRMFR 25.032 IRD corrections to RMF reports.

ASMTAPEE 25.033 Support for ASMTAPEE ML-40 assembly under z/OS 1.8.

ASUM70PR 25.303 Extraneous PROC PRINT from testing was removed.

ASUM70PR 25.270 INTERVAL=DURSET cannot be used.

ASUM70PR 25.163 Capacity Group summarization, PDB.ASUM70GC/ASUM70GL.

ASUM70PR 25.150 ASUM70PR created PCTCPUBY GT 100%, final fix?

ASUM70PR 25.150 ASUM70PR now supports INTERVAL/CECINTRV=SHIFT.

ASUM70PR 25.001 NRICFCPU,NRIFLCPU were wrong if there was more than 1

ASUMCEC 25.053 PDB.ASUMCEC, PCTCPUBY GT 100%, DURATM LT CECINTRV.

ASUMCELP 25.209 Duplicate observations in PDB.ASUMCELP eliminated.

ASUMHSM 25.113 HSM Summary enhanced with "HSM COMPLEX" HSMPLEX.

ASUMTAPE 25.300 Blank SYSTEM, missing DEVNR in PDB.ASUMTAPE fixed.

ASUMTAPE 25.040 Uncompress read/write SMF21DBR/DBW kept in ASUMTAPE.

ASUMUOW 25.121 Enhanced to keep each CICS segment response time.

ASUMUOW 25.054 QWACSPCP,QWACTRET added to PDB.ASUMUOW for OTE.

BLDSMPDB 25.048 Corrections to BLDSMPDB, new SORTEDBY= option.

COMPINTV 25.302 Capture/Compare ALL CPU times in 30/70/72/100/101/110

CONFIGV8 25.037 SORTEQUALS should NOT have been in CONFIGV8, V9 only.

CONFIGV9 25.267 VALIDVARNAME=V7 added to SAS CONFIGs.

CONFIGV9 25.101 MEMLEAVE=10M SORTBLOCKMODE now set in CONFIGV9

CONFIGV9 25.028 OPTION NOSORTEQUALS caused errors in ASUM70PR.

CONFIGW2 25.252 MXG updates for testing MXG Execution under WPS.

DALYTAPE 25.072 Sample tape reports from STC VTS SMF + MXGTMNT.

Doc 25.179 Use %LET MACxxxx= %STR( text ) ; to pass text.

Doc 25.078 List of MXG-issued USER ABEND values & source member.

EXITCICS 25.240 MCTSSCRL now tested vs MCTMNOPN for CICS Compressed.

EXITCICS 25.017 SAS INFILE EXIT for compressed CICS SMF 110-1 data.

FORMATS 25.063 Additional SWAP reason codes added to $MG079SR.

IHDRIDMS 25.112 CA IDMS PerfMon support enhanced with "IHDR" exit.

IMACICMR 25.007 CMRDATA, CMDUDATA/CMDDBCCP reversed.

IMACICOB 25.238 OMEGAMON did NOT increase time-duration to 12 bytes.

IMACICOB 25.008 OMDBDB2LN now spelled as OMBDB2LN.

IMACICOM 25.008 OMMLN now spelled as OMMQLN.

ITRMTNG 25.262 233 DDU files to create ITRM definitions for TYPETNG.

MXGWPSV2 25.252 Revised JCL Procedure for MXG Execution under WPS.

READDB2 25.189 New PDBOUT=YES, old PDBOUT= changed, writes to WORK.

RMFINTRV 25.199 SMF70GIE now reset to 00/15 if SYNC59=YES is used.

RMFINTRV 25.177 ARRAY SUBSCRIPT OUT OF RANGE, 9999 LIMIT externalized

SYSLOG 25.070 Major revisions to SYSLOG program, will be renamed.

TIMEBILD 25.209 Optional SYNC59 timeshifting using TIMETABL.

TYPE102 25.306 Support for APAR PK38803 INCOMPAT SMF 102 IFCID 22.

TYPE102 25.306 IBM SMF 102 IFCID 22 APAR PK38803 wrong, supported.

TYPE102 25.129 IFCID=224 updated with QW0224PN and QW0224CI.

TYPE110 25.240 MCTSSCRL now tested vs MCTMNOPN for CICS Compressed.

TYPE119 25.119 SMF 119 from z/OS 1.8 caused INVALID DATA messages.

TYPE119 25.119 Support for SMF 119 for z/OS 1.8 (INCOMPATIBLE).

TYPE120 25.247 SM120SNT=2 (two heap ids) caused INPUT EXCEEDED.

TYPE122 25.287 Support for SMF 122, Tivoli Tape Allocation Manager

TYPE1415 25.047 Support for APAR OA19502, SMF14KET Key Exchange Time

TYPE21 25.083 Actual support for APAR OA20077 Device Bytes TYPE21.

TYPE21 25.040 Support for APAR OA20077, uncompress read/write byte

TYPE22 25.276 Support for APAR OA20043 Dynamic Volume Expansion

TYPE30 25.304 Support for APAR OA23679, BLKSIZE might be wrong.

TYPE30 25.260 MXG 25.10, INTRVLTM missing for TYPETASK='OMVS'

TYPE30 25.116 MXG 25.05, negative EXECTM, INTRVLTM, GMTOFF30 wrong.

TYPE30 25.089 GMTOFF30 calculation corrections and problems.

TYPE42 25.153 MXG 25.06 only, false INVALID TYPE42 SUBTYPE 5 error.

TYPE42DS 25.030 TYPE42DS had carried-forward IOCOUNT and other vars.

TYPE50 25.269 Support for OSA-MPC VTAM SMF 50 subtype 4 record.

TYPE70 25.211 ZIPACTTM, PCTZIPBY corrected for Dedicated zIIPs.

TYPE70 25.028 IORATEn per-engine I/Os corrected for IRD.

TYPE7072 25.237 LCPUWAIT was accidentally not kept in TYPE70.

TYPE7072 25.227 Variable RPRTCLAS now kept in TYPE72DL dataset.

TYPE7072 25.224 CPUTYPE tests are replaced with ZARCHMDE tests.

TYPE7072 25.205 Support for z/OS 1.9 54 CP engines per MVS, INCOMPAT

TYPE7072 25.176 Support for APAR OA18244, Blocked Workload z/OS 1.9.

TYPE7072 25.163 Support for Capacity Groups variables in TYPE70.

TYPE7072 25.135A LCPUCAP/LCPUCAPC Labels include "Hard CAP".

TYPE7072 25.013 PCTMVSBY in PDB.TYPE70PR was wrong if IRD was active.

TYPE70PR 25.051 NRIFACPU now populated for z990/2084 CPUTYPE.

TYPE71 25.143 SWAPrates were set missing if zero, now can be zero.

TYPE71 25.109 UIC variables changed meaning in z/OS 1.8.

TYPE74 25.140 APAR OA17070 supports CF Level 15 measurements.

TYPE74 25.140 Support for APAR OA17070 RMF 74-4 Coupling Facility

TYPE74 25.108 R748CSER/CTYP/CDML now kept in TYPE748 dataset.

TYPE74 25.003 NREXPOSR was wrong for HyperPAV devices.

TYPE78 25.236 Zero obs in TYPE78IO with Change 24.171 if z/OS 1.7.

TYPE78 25.141 APAR OA21799 prevents ABEND, SMF78HIX invalid.

TYPE80A 25.137 Support for unknown TOKDANAMs, prevents ABEND.

TYPE80A 25.131 Support for CRL PUBLISH and SET UID RACFEVNT 52, 79.

TYPE80A 25.131 Support for TOP SECRET (INCOMPAT) '90'x,'00'x VRSN.

TYPE80A 25.111 TYPE80xx variable TYPSTRNG wrong after Change 25.024.

TYPE82 25.257 Support for ISCF HCR7750 TKE Logging update.

TYPE85 25.279 Support for subtypes 38, 39 and 40 for ID=85 OAM.

TYPE85 25.234 New variables in OAM subtype 32-35 records.

TYPE89 25.198 SMF89HOF,SMF89DTO were incorrect due to typo.

TYPE89 25.138 Support for APAR OA20314 new SMF89LPN/SMF89ZNA.

TYPE92 25.192 New ID=92 ST=14 INPUT EXCEEDED if not a RENAME.

TYPE99 25.012 SMF 99 with only Trace, INPUT STATEMENT EXCEEDED.

TYPEAIXT 25.039 Support for AIX Tapas-C performance data files.

TYPEBTE 25.107 Support for CA Brightstor Tape Encryption SMF.

TYPEBVIR 25.011A Support for TS7700 SMF records.

TYPECIMS 25.230 IMF 4.2 PTF BQI0129 caused INPUT EXCEEDED error.

TYPECIMS 25.139 Support for IMF Version 4.3 (INCOMPATIBLE).

TYPECLAR 25.130 Support for Clarion Disk Array flat files.

TYPECSM 25.050 Support for CrossSysplexManager user SMF record.

TYPEDB2 25.291 DB2ACCT variable QWACUDCP CPU time added in DB2TCBTM.

TYPEDB2 25.265 DB2TCBTM Correction for DB2 V9.1, REQUIRED.

TYPEDB2 25.169 _RDB2ACC DB2 Parallel event "analysis" example.

TYPEDB2 25.097 Variable THREADTY blank if non-DDF transaction.

TYPEDB2 25.090 Support for PK37354 SMF 101 Subtype 4 in DB2 9.

TYPEDB2 25.064 Several QISE variables were wrong.

TYPEDB2 25.020 DB2STATS, QWS3, QWS4 may have reversed contents.

TYPEEVTA 25.255 Support for Action Software's EventAction user SMF.

TYPEEVTA 25.255 Support for Action Sofware's EventAction SMF record.

TYPEFERT 25.133 Support for Williams Data FERRET product user SMF.

TYPEHSM 25.042 Process HSM with different SMF IDs/different SYSTEMs.

TYPEIMS7 25.006 Support for IMS Version 10 (INCOMPATIBLE) IMS log.

TYPEITRF 25.286 Support for ITRF DCR77/DCR78 additions.

TYPEITRF 25.103 Support for IBM OMEGAMON TRF ITRF V550 and V560.

TYPEMQLG 25.280 Support for MQ V6 System Admin Accounting Queue Log.

TYPENDM 25.242 NDM record 'UC' is now output in NDMAE dataset.

TYPENDM 25.081 NDM-CD type 'NM' records now decided into NDMNM.

TYPENDM 25.014 No observations in NDMRT due to incomplete comment.

TYPENMON 25.229 NMON for AIX CPUnn records vary in number.

TYPENMON 25.110 Support for DISKBUSYn for all NMON Disk Monitoring.

TYPENMON 25.104 Full support for NMON, Nigel's Monitor for AIX/unix.

TYPENMON 25.073 Support for LPAR and IOADAPTR Nigel's NMON data.

TYPENTSM 25.282 Support for new NTSMF Objects, Database Mirroring.

TYPENTSM 25.253 Support for new NTSMF objects for MSSQL.

TYPENTSM 25.015 INCOMPATIBLE MXG CHANGE for NTSM WEEK/MONTH BUILDs.

TYPEORAC 25.127 No change in Oracle Version 10, but data is trash.

TYPEPDSM 25.245 CA PDSMAN diagnostic trace records filled //WORK.

TYPEPSYC 25.277 Support for PSYNCH/390 SMF record.

TYPEQACS 25.178 AS400 APAR QAPMDISK with LRECL=456 added new data.

TYPEQACS 25.132 Revisions to AS400 TYPECONF GDES variables.

TYPERACF 25.244 IRRDBU00 Unload '0200' record has two lengths.

TYPERACF 25.134 Support for IRRDBU00 record types 0560,0561,0562.

TYPERMFV 25.309 Support for RMF III CPD, Channel Path Data Table.

TYPERMFV 25.246 Updates for CPU Segmentation changes.

TYPERMFV 25.225 Variable ENCCPUT corrected with zIIP time removed.

TYPERMFV 25.204 CFI Segmentation eliminates RMF III skipped CF data.

TYPERMFV 25.191 Support for RMF Monitor III CFI table enhancements.

TYPERMFV 25.145 RMF III dataset ZRBLCP missing obs for many LPARs.

TYPERMFV 25.079 ZRBLCP dataset had only first LPARs observations.

TYPESAMS 25.055 Support for SAMS objects 2151,2226,2229 and 2231.

TYPESRDF 25.195 Support for EMC's SRDF/A user SMF record.

TYPESYNC 25.117 INVALID ARGUMENT due to incorrect HEX4/HEX3 formats.

TYPETDS 25.052 Support for TDSLink Version 630 ZCOST datasets.

TYPETIMS 25.271 Revisions for TMON/IMS support

TYPETMS5 25.126 Circumvention skip new TMC 'FF20'x Vol Def record.

TYPETMS5 25.084 FILSEQ in TMS.DSNBRECD could be wrong, mult-vol-file.

TYPETNG 25.243 Automatic PROC DELETE of UNKNOWN dataset removed.

TYPETNG 25.235 New Solaris, AIX, and many RedHat objects added.

TYPETNG 25.221 Support for VM Ware VSX Systems in CA NSM records.

TYPETNG 25.181 Support for CA NSM RedHat 4.01 Linux perf cube.

TYPETNG 25.181 Support for CA Unicenter NSM is in MXG "TNG" product.

TYPETPMX 25.239 Support for Thruput Manager SLM and DB2 data.

TYPEVMXA 25.151 180 Error _MPRCAPC not found, DEBUG prints removed.

TYPEVMXA 25.043 Reserved Change Number.

TYPEXAM 25.307 Extraneous PUT from testing removed.

TYPEXAM 25.115 Incorrect memory variables in XMUCDSYS in MXG code.

TYPEXAM 25.082 Support for XAM Release 3.6, many new data.

TYPSCOCR 25.034 Support for CopyCross (now VTF Mainframe 2.1.0) SMF.

UCICSCNT 25.120 CICS record counting separates Resource segments.

UCOMPSOE 25.028 Utility to compare SORTEQUALS and NOSORTEQUALS output

UPCMEMDZ 25.144 ASCII utility to determine memory available to MXG.

UPRINDOC 25.226 Utility prints NAME and LABEL of all variables.

UTILBLDP 25.196 Large &MACKEEP string caused strange results.

UTILBLDP 25.098 %UTILBLDP(BUILDPDB=JES3 ... enhancement.

UTILBLDP 25.071 Products that need deaccumulation now protected.

UTILBLDP 25.065 Default list of ASUMxxx to be included, MXGINCL=.

UTILCSV 25.197 %UTILCSV creates a CSV (or TAB) Delimited flat file.

UTILEXCL 25.256 Macro variable &MXGDEBUG revised for IMACEXCL plus!

UTILEXCL 25.193 MXG 25.08 ONLY: LABEL IMACICU3 NOT FOUND.

UTILLPDS 25.136 Utility to count used/defined PDS Directory Blocks.

VMAC110 25.041 Reserved Change Number.

VMACDB2 25.075 QBGL variables in DB2 V8.1 supported, were wrong.

VMXG70PR 25.293 SMF70GIE is now set from STARTIME=DURATM after shifts

VMXG70PR 25.028 OPTION NOSORTEQUALS caused errors in ASUM70PR.

VMXGDUR 25.044 Interval= QUARTER, SEMIANN, ANNUAL now supported.

VMXGINIT 25.231 Unresolved &ARRAYRMF is SAS V8.1 or WPS was used.

VMXGINIT 25.143 New MXGMISS macro variable changes TYPE71 SWAPrates.

VMXGPRAL 25.028 Print All utility now compares all datasets in LIBs.

VMXGRMFI 25.069 Service Class Names can be "wild-carded"

VMXGSUM 25.248 New &LNSUMOUT=8 will make all output to length 8.

VMXGUSE 25.067 Revised to invoke _STY70; UTILBLDP recommended.

See member CHANGESS for all changes ever made to MXG Software.

Inverse chronological list of all Changes:

NEXTCHANGE: Version 25.

====== Changes thru 25.309 were in MXG 25.25 dated Jan 28, 2008=========

Change 25.309 Support for RMF III CPD, Channel Path Data Table, creates

ASMRMFV new ZRBCPD dataset.

CLRMFV

ADOCRMFV The RMFV documentation in DOCRMFV and the documentation

EXZRBCPD in the CLRMFV CLIST (without any code changes in CLIST)

IMACRMFV have been updated to match ASMRMFV's updated.

VMACRMFV

VMXGINIT

Jan 28, 2008

Thanks to Jerry Urbaniak, Acxiom, USA.

Change 25.308 SAS V8.2-V9.1 %MACRO compiler accepts %ELSE %THEN %DO;

ANALDB2R syntax, but the documented syntax is only %ELSE %DO;

VMACMVCI The SAS Language compiler never accepted ELSE THEN DO;

VMXGSUM In early tests of SAS V9.2, its %MACRO compiler rejected

Jan 28, 2008 the extra %THEN, so all three accidental, unintended MXG

Sep 16, 2008 %ELSE %THEN %DO statements have been corrected.

If you have an old member in your "USERID.SOURCLIB", the

error message you will get with SAS V9.2 will be:

ERROR: THERE IS NO MATCHING %IF STATEMENT FOR THE %THEN.

A DUMMY MACRO WILL BE COMPILED.

Thanks to MP Welch, SPRINT, USA.
Change 25.307 Debugging PUT printed _N_= COL=nnnn PRCAPM for every one

VMACXAM of those segments, but had no impact on output data.

Jan 25, 2008 Remove the PUT statement after WHERE ('PRCAPM').

Thanks to Rodger Foreman, TransUnion, USA.

Change 25.306 Change was in error, did not support PK38033, and was

VMAC102 replaced by Change 26.011 which does support the APAR.

Jan 23, 2008 And the original change text was WRONG, as there was

Feb 8, 2008 NOTHING wrong with IBM SMF 102 IFCID 22 with PK38803

records; the records matched the DSECT which I misread.
Change 25.305 Error in %UTILBLDP with USERADD=TMNT/nnn + BUILDPDB=YES.

UTILBLDP Because TMNT processing is already in BUILDPDB, there was

Jan 23, 2008 special handling in the USERADD= logic, but in this case

Jan 27, 2008 it incorrectly didn't create the MACRO _IDTMNT nnn % that

it should have, so, while all TMNT datasets were created,

they all had zero observations, unless you had defined

your TMNT Record ID _IDTMNT in IMACKEEP/IMACTMNT.

The logic in UTILBLDP is corrected for all USERADDs,

whether or not they are already in BUILDPDB:

USERADD=TMNT/nnn, creates MACRO _IDTMNT nnn %

which will override any IMAC tailoring.

USERADD=TMNT, does not create _IDTMNT, but ensures

TMNT records are processed.

-Jan 27: Added support for USERADD=100 101 alias for DB2.

-In testing the UTILBLDP invocation in the new COMPINTV, I

had %MACRO errors about non-numeric in a %EVAL, (whose

clarity may be a separate SAS issue!), but which were the

result of incorrect code ordering in my COMPINTV program.

When %UTILBLDP has MACKEEPX= argument text with old-style

macros that you want to redefine AND execute in this one

step, then your MACRO _XXXXXXX ... % statements must

be located after the %UTILBLDP(); statement and before

the %INCLUDE statement that executes the UTILBLDP output:

statement that executes the UTILBLDP output:

%UTILBLDP(MACKEEPX= MACRO _ETY70 _SETTIME %, .... );

RUN:

MACRO _SETTIME STARTIME=FLOOR(STARTIME/900); %

RUN;

%INCLUDE INSTREAM;
If the old style macros are defined before %UTILBLDP is

executed, then they are expanded inside the macro

language when the %MACRO UTILBLDP is being compiled,

which can result in unexpected failures. If you move the

definition to after %UTILBLDP, only the name of the macro

is passed to the UTILBLDP output which works as expected.

Thanks to Jim Horne, Lowes', USA.
Change 25.304 APAR OA23679 documents possible errors in BLKSIZE in SMF

VMACEXC1 30 records when DDCONS=YES is specified. Since MXG has

Jan 23, 2008 ALWAYS recommended DDCONS=NO and NEVER to use DDCONS=YES,

this shouldn't have impact. But when YES is specified,

IBM now says the consolidated SMF 30 record contains the

first non-zero BLKSIZE value from those DDs in SMF30BSZ,

the original 4-byte blocksize field, but the newer 7-byte

SMF30BXS blocksize field, contains the BLKSIZE value from

the last DD in the consolidation, which could be valid or

zero. MXG stored SMF30BSZ into BLKSIZE, but then INPUT

BLKSIZE from SMF30BXS when it existed, even when zero.

Now, BLKSIZE is set to SMF30BXS ONLY when it is larger

than SMF30BSZ.
Change 25.303 -Extraneous PROC PRINT from testing was removed.

VMXG70PR -Calculation of LPARCPUS could be non-integer value, for

Jan 22, 2008 example, 11.99995682 instead of 12. Algorithm refined.

Jan 28, 2008

Thanks to Clayton Buck, UniGroup, USA.

Thanks to William Wai Lun WONG, HSBC, HONG KONG.

====== Changes thru 25.302 were in MXG 25.25 dated Jan 21, 2008=========
Change 25.302 Compare all CPU variables from SMF 30,70,72,100,101,110s.

COMPINTV Single pass of SMF creates only the needed datasets with

UTILEXCL a "fast read" of SMF records keeping only the CPU and key

Jan 21, 2008 variables to minimize the run with a tailored %UTILBLDP

Jan 27, 2008 and MACKEEPX overrides to create two summary datasets:

Jan 30, 2008 PDB.INTVSRVC by SYSTEM STARTIME SRVCLASS 30+72

PDB.IN307072 by SYSTEM STARTIME 30+70+72

PDB.INALLCPU by SYSTEM STARTIME 30+70+72+100+101+110

Fast read: 6 GB SMF data, 2 Minutes CPU, 10 Min Elapsed
The type 30 SMF interval and type 72 RMF service class

create the PDB.INTVSRVC with CPU times by service class.

Those data and the CPUACVTM from TYPE70 are combined into

the PDB.IN307072 SMF+RMF CPU time for each interval. Then

the CICSTRAN and DB2ACCT transaction CPU times plus the

interval CICDS dispatcher and DB2STATS statistics CPU

times are added from the 100, 101, and 110 records to

create the PDB.INALLCPU with ALL possible CPU variables,

summed for each SYSTEM for each STARTIME.
Several PROC MEANS summary output reports are printed.
The SRVCLASS-level SMF30 and RMF72 summary CPU times

should match closely for most service classes, but there

can be significant differences in which "SRVCLASS" CPU

time is recorded. For example Enclave CPU time in SMF

may be in the SRVCLASS of the address space that started

the enclave, but in RMF that same enclave CPU time gets

put in the SRVCLASS where that enclave was classified.

And we've seen enclaves in two SRVCLASS in SMF30 while

spread across three SRVCLASS in RMF72. It can get messy!
The STARTIME-level interval summary should match RMF and

SMF totals, for the CPU fields that we expect to match,

and will show how much of that CPU time is captured in

the DB2 and CICS interval data as well, but its accuracy,

and the accuracy of the SRVCLASS-level data is dependent

on the synchronization of your SMF and RMF data.

The MACRO _SETTIME default expects 15 minute intervals

and SYNC(0), but can be tailored to your intervals.

You can get the totals of all CPU times for all of SMF

records in a single output observation per SYSTEM by

setting STARTIME to a single value for all records.

But the summary of the CICSTRAN and DB2ACCT times

can always be skewed by a long-running transaction,

or if SYNC59 is in the data (because not all CPU

records obey SYNC - RMF/SMF 30 does, CICS doesn't.

Jan 30: If you use COMPINTV and have an IMACEXCL member,

COMPINTV fails when it sees the second _VCICTRN

definition in your IMACEXCL. If you will insert

MACRO _VCICTRN _VCICTRN %

immediately before the existing MACRO _VCICTRN,

then COMPINTV will not fail. And, fortunately,

by accident, the MACRO _VCICTRN defined in the

MACKEEPX in UTILBLDP will be used for CICSTRAN,

(and it's required for the rename of STRTTIME to

STARTIME and to minimize disk space), because

MACKEEPX is instanced after IMACEXCL was read.

Syntax corrected in Change 26.020.

Thanks to Chuck Hopf, Bank of America, USA.

Change 25.301 Due to typos that had DB where OB should have been, all

VMAC102 of the QW1145OB-QWF145OB variables were wrong (they had

Jan 21, 2008 the DB database value instead of the OB Object value).

Thanks to Giuseppe Giacomodonato, E.P.V. Technologies, ITALY.

Change 25.300 PDB.ASUMTAPE could have blank SYSTEM and VOLSER, DEVNR

ASUMTAPE missing when the SYSLOG Mount and Keep messages had the

Jan 21, 2008 same timestamp, and the Keep was seen first. Adding the

variables SMFTIME SYSLTEXT forces the KEEP to be first

to complete the prior event, but adding .001 seconds to

IF SYSLTMNT GT . THEN EVENTIME=SYSLTMNG+.001;

was also needed to force the correct sequence.

Thanks to Scott Barry, SBBWorks, Inc, USA.

Change 25.299 Type 42 Subtype 18 CF Cache Partition Summary Section for

EXTY42P3 Directory/Element Ratio Data now creates new dataset:

IMAC42 DDDDDD DATASET Description

VMAC42 TY42P3 TYPE42P3 RLS CF DIRECTORY/ELEMENT RATIO

VMXGINIT which had been added in z/OS 1.8 but overlooked.

Jan 21, 2008

Thanks to Bruce Widlund, Merrill Consultants, USA.
Change 25.298 ADOCxxxx members that existed have been updated with new

ADOCs variables. New ADOCS member lists the VMACxxxx products

Jan 20, 2008 for which an ADOC member does not exist.
Change 25.297 Change 25.196 caused ERROR: CHAR OPERAND IN THE %EVAL ...

UTILBLDP when either or both MACFILE and MACKEEP were used and had

Jan 19, 2008 more than 65 characters of text.

Thanks to Scott Barry, SBBWorks, Inc, USA.

Change 25.296 All ADOCxxxx members were updated with current CONTENTS.

ADOCs

Jan 19, 2008

Thanks to Freddie Arie, Merrill Consultants, USA.

Change 25.295 The COMPALL program compiles all of the VMACs for all SMF

COMPALL records in a single data step, and is back in MXG's QA

VMACIPAC tests, now that it can be compiled! It was used in early

VMACOMCI MXG Versions, testing only the IBM SMF records, by about