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



Yüklə 28,67 Mb.
səhifə73/383
tarix17.01.2019
ölçüsü28,67 Mb.
#98988
1   ...   69   70   71   72   73   74   75   76   ...   383

Feb 11, 2013 SYLVMT00='00*SYNC*LEVEL*MOUNTS'

AVLVMT00='00*AVERAGE*SYNC*LEVEL*MOUNT*TIME'

-BVIR32 documentation: IBM change how they count bytes:

"TVCSIZE: increments of 1000MB (1024*1024*1000). A TVC

that is 1.7TB in size will be reported as x000006A4

which is 1700 decimal."

MXG did not format TVCSIZE with MGBYTES but 6A4 is the

decimal TVCSIZE=1700 with the label "TVCSIZE IN GB".

-IBM confirmed that variable LIBSEQNR is now always

blank or nulls - see ADOCBVIR.

-Variable DLIBDEQN can contain hex rather than EBCDIC,

or it can be blank.

-BVIR32 variable AVGCPUSE is labeled as

AVGCPUSE 'CPU*USAGE*PERCENT*AT END OF*INTERVAL'

but it contains the AVERAGE CPU PER TAPE VOLUME CACHE

and its documentation clarified by IBM in the manual:

This 1 byte field indicates the larger of CPU usage

percentage OR Tape Volume (TVC) usage percentage at

the end of the interval. The TVC busy value is based

on IO activity where 100% is when the disks are being

accessed 100% of the time. This value can be used to

indicate how busy the system was during the interval.

It is updated every 30 seconds. The TVC percentage is

an average of 30 one second intervals.

-BVIR31 new variables are documented and created:

BYTESEXP='AMOUNT*OF DATA*EXPORTED'

BYTESIMP='AMOUNT*OF DATA*IMPORTED'

LOGVOLEX='LOGICAL*VOLUMES*EXPORTED'

LOGVOLIM='LOGICAL*VOLUMES*IMPORTED'

PHYVOLEX='PHYSICAL*VOLUMES*EXPORTED'

PHYVOLIM='PHYSICAL*VOLUMES*IMPORTED'

-BVIR33 has eight sets of new variables G1 thru G8 with

G1DEFRBY='1ST DATA*FROM*DEFERRED*COPY'

G1DEFRCY='1ST DATA*FROM*DEFERRED*COPIES'

G1IMEDBY='1ST DATA*FROM*IMMEDIATE*COPY'

G1IMEDBY='1ST DATA*FROM*SYNC MODE*COPY'

G1IMEDCY='1ST DATA*FROM*IMMEDIATE*COPIES'

G1IMEDCY='1ST DATA*FROM*SYNC MODE*COPIES'


Change 31.015 -These five DB2 V10 SMF 101 Subtype 1 DB2ACCTP variables

VMACDB2 QPACLOCN,QPACCOLN,QPACPKID,QPACASHC,QPACAANM, can be

Feb 10, 2013 wrong, but only when they are "truncated":

"IBM-truncated" fields previously had a fixed length

(QPACLOCN was 16 bytes) but now can be variable length

for data like URLs and IPV6 addresses from our open

systems gurus. Each field has an offset to a one-byte

length field followed by that many bytes of the field.

These offsets are NOT populated when the value fits in

the original fixed length field that was already INPUT.


There are two independent errors, one mine, one not mine.
-The MXG code for the offsets to LOCN COLN PKID and AANM

used OFFQPAC+offset, but LOCQPAC should have been used as

it is incremented for each QPAC segment; OFFQPAC isn't.

So those four variable's values were only valid for the

first DB2ACCTP observation in each SMF 101 record.
-One site sent SMF data with invalid values for the offset

to those "truncated" fields. The offset values for each

field is 10 more than it should be. Decimal values:

Segment 5 out of 7 in record 3222:


OFFQPAC LENQPACX Len of PACX Next QPAC

@1777 451 +2 2228

@2228 451 +2
But the two-byte OFFSET to QPACAANM is @2169 with a

'01B8'x or 440 decimal. Adding 1777+440 is 2217, but

the field's length and text are visible in 2207, and

the static portion of this segment ended in 2206.


This change compares the location of the first offset to

the end of the static fields and corrects the offset by

subtraction when they are different.
-Variable QPACRUSM was not reset to blank after it was

set to 'Y' in an SMF record because it was coded as RUSN.

Change 31.014 One user claims MXG's SMF HEADER/TRAILER messages printed

VMACSMF on the SASLOG have caused LINES EXCEEDED messages that he

VMXGINIT doesn't like. I disagree COMPLETELY, and would NEVER turn

Feb 8, 2013 them off, since they can be EXTREMELY useful (albeit in

only rare cases) in problem determination: they print the

begin and end time of each "data chunk" in each SMF Dump.

But it is trivial to create a macro variable SMFPUTHD

that will suppress their printing, using:

//SYSIN DD *

%LET SMFPUTHD=NO;

%INCLUDE ....

And, if after turning them off you realize you need them,

you can read the same SMF file and print them, using:

//SYSIN DD *

%LET SMFPUTHD=YES;

%INCLUDE SOURCLIB(VMACSMF);

DATA _NULL_; _SMF; RUN;

Clearly, my MXG default is %LET SMFPUTHD=YES;


Change 31.013 Variables NDMCNF1, NDMCNF2, & NDMCPEA were set to '00'x

VMACNDM when they should not have been (and I have no notes as to

Feb 7, 2013 why I set them to null).

Thanks to Randy Schlueter, First Data, USA.


Change 31.012 Change 30.170 output CICLDR observations only when LDRFC,

EXCICLDR Fetch count, is non-zero, but with interval statistics,

Feb 6, 2013 a program can be fetched after the region starts up and

then be continually used afterwards, with LDRFC=0, so

those observations were not output. The CICLDR dataset

exit member EXCICLDR is changed to output when LDRTU, the

Times used Since Last Reset, is non-zero, as that is a

better indicator that the program was used.

Thanks to Tony Hirst, Wells Fargo, USA.
Change 31.011 If you specified WEEKKEEP=TYPE42: that colon caused the

BLDSMPDB the length of the compare to detect what data sets should

Feb 5, 2013 be kept to be incorrectly set to &complen, which was the

length of the input name, but instead is now set to &dlen

which is the correct length for comparison with or

without the colon modifier.

Thanks to Jim Horne, Lowe's, USA.
Change 31.010 MXG 30.08-MXG 30.30. If you selected SYSLOG MSGIDs to be

VMACTMNT written as SMF Subtype=9 by MXGTMNT (Tape Mount Monitor),

Feb 2, 2013 reading them caused zero obs in TYPESYSL and log messages

MSGID NOT FOUND IN RECORD N= . . . .

Change 30.230 enhanced ASMTAPE to write some JES3 event

SYSLOG messages as Subtype=8 so they would be output to

TYPESYMT, but for testing they were created as subtype 9

with the old ASMTAPE, and my test in VMACTMNT to output

them to TYPESYMT was temporarily changed to read them

with ELSE IF TMNTTYPE=8 OR TMNTTYPE=9, but that should

have been changed back to just ESLE IF TMNTTYPE=8.

Thanks to Paul Naddeo, Fiserv, USA.


Change 31.009 The _STYBETF dataset sort macro was not in the _SBETA

VMACBETA product sort macro, so dataset BETA25 was not copied into

Jan 31, 2013 the PDB data library when TYPSBETA was used.
Change 31.008 -Change 30.250 replaced hardcoded "PDB." with "&PDBMXG.."

ANAL120 (so MXG default DDNAME is used by also easily changed,)

Jan 30, 2013 but ANAL120 was wrong before and after, as some of its

datasets were expected to be in //PDB while others were

read from //WORK. This change expects ALL of the TYPE120

datasets will be in the //PDB DD data library before the

%INCLUDE SOURCLIB(ANAL120);

is executed, but new examples in comments show how to

read SMF data to create just reports or to create both a

WebSphere PDB and these example reports. But these are

all simple PROC PRINTs and PROC MEANS and the primary

value is the suggested variables that might be useful as

a STARTING POINT for your own reports

(which I'd be happy to add to the ANAL120 member if

you have a contribution to share with other MXGers).

Thanks to Scott Barry, SBBWorks, Inc., USA.


Change 31.007 -VMACVMXA and VMAC113. The HIS CPU Counter variables in

VMAC113 z/VM dataset VXPRCMFC should match those variables in the

VMACVMXA z/OS HIS TYPE113/ASUM113 dataset, but new counters

Jan 28, 2013 EXTND157-EXTND207 in VMACVMXA were not labeled, weren't

deaccumulated with DIF() function, and weren't tested for

RESETCTR+1, and the INPUT thru 255 was changed to the

known maximum counter EXTND207. But then in VMAC113, I

discovered that variables EXTND183-EXTND207 were not

tested for RESETCTR+1. So the MXG QA now ensures counters

match in TYPE113, ASUM113 and VXPRCMFC datasets.


Change 31.006 Support for OAM SMF ID=85 Subtypes 90,91,92 and 93 create

EXTY8590 DDDDDD DATASET DESCRIPTION

FORMATS TY8590 TYPE8590 LCS FILE SYSTEM ACTION

IMAC85 Variable R859SUB contains the subtype and is formatted to

VMAC85 identify 90:WRITE, 91:READ, 92:DELETE, 93:CLEANUP events.

VMXGINIT


Jan 28, 2013

Thanks to Neil Ervin, Wells Fargo, USA


Change 31.005 -Cosmetic. These percentage variables in TYPE72GO

VMAC7072 PCTDLACO PCTDLAPR PCTDLAXM PCTDLCCA PCTDLCDE PCTDLCHS

Jan 26, 2013 PCTDLHSP PCTDLIDL PCTDLIOD PCTDLMPL PCTDLNDI PCTDLPDE

PCTDLPQU PCTDLQ PCTDLSHS PCTDLSMP PCTDLSPV PCTDLSSW

PCTDLSVI PCTDLSWI PCTDLTDQ PCTDLTOT

are now formatted 5.1 to print pretty.


Change 31.004 -RMF III, z/OS 1.13, but only with APAR OA38660, all ASI

ASMRMFV extensions (Service Class, Report Class, Resource Group

VMACRMFV and Workload) are incorrect, because that APAR inserted

Jan 28, 2013 72 at the end of the base segment; record version is now

'16'x, but only '12'x is in RMF Programmers Guide, so it

took SYS1.EYEBALL of a hex record dump to determine what

had been added. Adding data at the end of a segment is

INCOMPAT in this case in MXG because ASMRMFV appends the

extensions to its record, and those new bytes moved the

offset to the extensions. This circumvention corrects:

IF ASIVERG3='16'x THEN INPUT +72 @;

but it requires a code change and a new member.

-But, we see a better way: ASMRMFV will put ASIBASNL, the

base segment length, into the top two bytes of ASIENTMX,

with ASIENTMX in the low two bytes, so that VMACRMFV can

use ASIBASLN to locate the extensions and a future insert

won't require an updated MXG code member nor a new value

for the record version test. Using the length fields are

almost always more robust than using product or record

version values in tests for existence.

-NOTE: It is still possible to have missing values for

variables from one or more of these extensions for

some address spaces. For example, address spaces with

no Reporting Class defined will have variable ASIRNM

missing and those with no Resource Group defined will

have variable ASIGNM missing (blank).

Thanks to Warren Cravey, FMR Corporation, USA
Change 31.003 Message UNINITIALIZED VARIABLE SM1132MM: minimal impact.

ASUM113 A test for SM1132MM was added by Change 30.274 to detect

VMAC113 single book machines so negative values could be zeroed,

Jan 25, 2013 IF SM1132MM='M10' OR L4RP LE 0 THEN DO; /*SINGLE BOOK*/

but SM1132MM was only added to ID= in VMAC113, it was not

added in ASUM113 so it was uninitialized when referenced.

But, as I just discovered in assessing the actual impact

of my error, even when SM1132MM is uninitialized, that OR

in that IF statement causes the expression to be TRUE if

L4RP is zero or a missing value, which is actually a

stronger test for single book than the "Machine Model."

Thanks to Chris Weston, SAS ITRM Development, USA.


Change 31.002 The CICTSQ dataset is merged into PDB.CICINTRV dataset

VMXGCICI but these "newish" variables in CICTSQ were not included:

Jan 24, 2013 A12SHPDF A12SHPCN A12SHRDS A12SHWTS

A12TSLHT A12TSMLM A12TSMUS A12TSMAX

A12TSQDL A12TSCTR

Thanks to Doug Medland, IBM Global Services, CANADA.


Change 31.001 Variable QW0141OT='AUTHORIZATION*ID*TYPE', L for ROLE or

FORMATS blank for User ID or Secondary Authorization ID is INPUT

VMAC102 and kept in T102S141 Audit dataset and formatted.

Jan 23, 2013 Formats $MGD140O now has all $MGD361O entries and formats

MGD140P and MGD361P have the union of separate values.

Thanks to Tommy Grace, Nationwide Insurance, USA.


LASTCHANGE: Version 31.

=========================member=CHANGE30================================

/* COPYRIGHT (C) 1984-2013 MERRILL CONSULTANTS DALLAS TEXAS USA */
MXG Version 30.30 was dated Jan 21, 2013, thru Change 30.292.

MXG Newsletter SIXTY-ONE was dated Jan 21, 2013.

MXG Version 30.10 was dated Jan 3, 2013, thru Change 30.274.

MXG Version 30.09 was dated Dec 4, 2012, thru Change 30.253.

First MXG Version 30.09 was dated Dec 3, 2012, thru Change 30.252.

MXG Version 30.08 was dated Nov 7, 2012, thru Change 30.235.

First MXG Version 30.08 was dated Nov 5, 2012, thru Change 30.230.

MXG Version 30.07 was dated Oct 3, 2012, thru Change 30.200.

Second MXG Version 30.07 was dated Oct 2, 2012, thru Change 30.199.

DONTUSE MXG Version 30.07 dated Oct 1, 2012, thru Change 30.198.

MXG Version 30.06 was dated Sep 1, 2012, thru Change 30.177.

Second MXG Version 30.05 was dated Aug 8, 2012, thru Change 30.153.

First MXG Version 30.05 was dated Aug 6, 2012, thru Change 30.151.

MXG Newsletter SIXTY is dated Aug 6, 2012.

MXG Version 30.04 was dated Jul 4, 2012, thru Change 30.124.

First MXG Version 30.04 was dated Jul 2, 2012, thru Change 30.122.

MXG Version 30.03 was dated May 30, 2012, thru Change 30.096.

MXG Version 30.02 was dated Apr 15, 2012, thru Change 30.062.

MXG Version 30.01 was dated Feb 13, 2012, thru Change 30.021.

Annual MXG Version 29.29 was dated Jan 23, 2012, thru Change 29.307.


Instructions for ftp download can be requested by using this form:

http://www.mxg.com/Software_Download_Request

Your download instructions will be sent via return email.
Contents of member CHANGES:
I. Current MXG Software Version 30.30 is available upon request.

II. SAS Version requirement information.

III. WPS Version requirement information.

IV. MXG Version Required for Hardware, Operating System Release, etc.

V. Incompatibilities and Installation of MXG 30.30.

VI. Online Documentation of MXG Software.

VII. Changes Log
Member NEWSLTRS contains Technical Notes, especially APARs of interest

and is updated with new notes frequently. All Newsletters are online

at http://www.mxg.com in the "Newsletters" frame.
Member CHANGES contains the changes made in the current MXG version.

Member CHANGESS contains all changes that have ever been made to MXG.

All MXG changes are also online at http://www.mxg.com, in "Changes".
=======================================================================

I. MXG Version 30.30 dated Jan 21, 2013, thru Change 30.292.


Major enhancements/corrections added in MXG 30.30, dated Jan 21, 2013:
ANALCOMP 30.286 Graphic comparison of values over time.

TYPE110 30.278 TASZIPTM and TASELGTM documented, TASELGTM corrected.

TYPETMO2 30.277 Support for TMON CICS 3.4 for CICS/TS 5.1 INCOMPAT.

TYPEMVCI 30.276 Support for Mainview CICS 6.5 for TS 5.1 COMPATIBLE.

TYPEBETA 30.285 Support for BETA93 subtype 51.

TYPETAPR 30.284 Support for additional PHYSVOL/VOLUME file fields.

UTILEXCL 30.278 MXGNOTE on log identifies create date of IMACEXCL.

JCLSPLIT 30.287 Examples DECOMPRESS CICS/DB2 on z/OS for ASCII MXG.

UTILEXCL 30.283 Better support for UNKNOWN FIELDS to prevent 180.

READDB2 30.280 MXG 30.10 IFCID=STATS could still fail.

VFMT102 30.279 VFMT102 mapping DBID/OBID/PSID safer algorithm.

MXGNAMES 30.275 MXGNAMES/CONFIMXG supports a USER FORMAT library.


Major enhancements/corrections added in MXG 30.10, dated Jan 3, 2013:
VMXGALOC 30.273 SERIOUS ERROR if MONTH is used with VMXGALOC/UTILBLDP

TYPE7072 30.264 Support for APAR OA39562 new TYPE70Y3 PKCS11 CEX4P.

TYPE99 30.259 Support for SMF 99 Subtype 12 and 14 HiperDispatch.

TYPEVMXA 30.254 Support for zVM new CRYPTO TYPE PRCAPMCT=10.

TYPEVMXA 30.254 Support for zVM new HIS (SMF113) counters, zEC12.

TYPE102 30.265 Support for DB2 Trace IFCIDs 361 and 362 populated.

TYPEIDMS 30.270 Support for IDMS PERFMON Version 17 and 18.

READDB2 30.257 IFCIDS=STATS fixed, use instead of IFCIDS=STATISTICS.

BUILDPDB 30.260 PDB.JOBS variable ABENDS count included some RETURNs.

BLDSMPDB 30.255 WEEKKEEP, WEEKDROP now work as documented.

ASUM70PR 30.266 Variable LFARIFLS added to ASUM70PR datasets.

TYPE113 30.274 Correction to DWINSORM/DWDASORM for one book CEC.

SMFSRCH 30.269 Incorrectly tried to write to USERID.SMFOUT.DATA.

TYPE80A 30.268 RACF317 detect BPX.DEFAULT.USER, invalid in z/OS 2.1.


Major enhancements/corrections added in MXG 30.09, dated Dec 3, 2012:
TYPE120 30.244 Support for WebSphere Version 8 ID=120 Subtype 10.

TYPECIMS 30.245 Support for BMC Mainview IMS 4.6 a/k/a IMF, CIMS.

TYPEEJES 30.238 Support for Phoenix Software (E)JES SMF record.

TYPEBETA 30.237 Support for BETA93/97 Version 4.3.0 (INCOMPATIBLE).

TYPE119 30.249 SMF ID-119 SUBTYPE=51 INPUT STATEMENT EXCEEDED.

TYPEDB2 30.246 DB2STATS QWOSxxxx wrong if ZOSMETRICS=YES not set.

VMXG2DTE 30.242 New CRITERIA= parameter inserts selection SAS code.

ANALDB2R 30.241 Revised mapping of DBID and OBID objects to names.

VFMT102 30.241 Revised mapping of DBID and OBID objects to names.

GRAFDB2B 30.240 Graphic/tabular DB2 Buffer Size reports, ODS or GRAPH

VMXGCOPY 30.243 VMXGCOPY copies SAS datasets from multiple LIBNAMEs.

TYPE113 30.236 Spurious DEACCUMULATION RESET message not printed.


Major enhancements/corrections added in MXG 30.08, dated Nov 7, 2012:
If you downloaded MXG 30.08 dated Nov 5, please refresh with Nov 7:
Change 30.234 is REQUIRED with APAR OA37826 (z/EC12 TYPE74); it was

NOT in MXG 30.08 dated Nov 5. Use only the Nov 7 Version 30.08 if

you have installed that APAR:
TYPE74 30.234 ERROR: INVALID DATA FOR CHAR4, STOPOVER, APAR OA37826
TYPE110 30.228 Support for CICS/TS 5.1 INCOMPATIBLE - 30.08 REQUIRED

TYPEDB2 30.229 Support for DB2 NETEZZA optional data corrections.

TYPE113 30.201 Support for HIS zEC12 new Extended Counters, calcs.

TYPE7072 30.212 Support for zEC12 CRYPTO EXPRESS4S APAR OA37016.

TYPE74 30.209 Support for APAR OA37826 Channel Path Types CIB, CFP.

TYPE70 30.208 Support for APAR OA37803 Warning Track Interrupt.

TYPE74 30.207 Support for APAR OA39993 Interrupt Delay Time

TYPE79 30.207 Support for APAR OA39993 Interrupt Delay Time

TYPE71 30.206 Support for APAR OA38660 eC12 SCM and Pgbl Large.

TYPE78 30.206 Support for APAR OA38660 TYPE78PA additions.

TYPEDCOL 30.204 Support for APAR OA38980 ZFS dataset flag, FREEs.

ASUMTAPE 30.203 Support for JES3 Main Device Scheduler IAT5210/5918.

ASUMTAPE 30.203 INCOMPATIBLE: PDB.ASUMTAPE SORT ORDER CHANGED.

TYPENMON 30.226 Support for MEMAMS Memory Object, French text.

TYPENDM 30.220 Support for NDM-CD Subtype CX creates NDMCX dataset.

TYPE110 30.213 MXG 30.07 only. CICS STID=30 WARNING message fixed.

TYPEDB2 30.210 DB2 V10 APAR PN29124 detects IBM BIF INCOMPATIBLE.

TYPETPMX 30.216 MVS Solutions Thruput Manager SMF subtype 5 updates.

ASMRMFV 30.202 RMF III Enhancements and Fixes.

TYPERMFV 30.217 Reading RMF III data on ASCII - INVALID date message.

TYPEVMXA 30.215 z/VM BROKE CONTROL record when MONWRITE concatenated.

TYPEDB2 30.211 QISTCOLS now deaccumulated again.

TYPEDB2 30.222 IFCID=239 DB2ACCTP sets DB2PARTY, QPACROLL, QPACRUSM.

VFMT102 30.219 NODUPKEY temp circumvention for overlapped range.

TYPE70 30.233 TYPE70 CPUWAITM incorrect, greater than CPUUPTM

TYPETMS5 30.205 Variable ACTVOL added to TMS.TMS dataset.

ANALDB2R 30.219 Mapping of dBID/OBID values to names revised.

ANALDB2R 30.218 INTERVAL=xxxx wasn't supported, VMXGUM MXGERROR.

VMXGFIND 30.214 VMXGFIND to print all datasets had wrong title.

Many 30.225 New MXGEXIMSG macro variable for diagnostics.


Major enhancements/corrections added in MXG 30.07, dated Oct 3, 2012:
TYPE7072 30.182 Support for zNEXT EC12 processors with 101 engines.

ASMTAPEE 30.193 MXGTMNT Tape Mount Monitor no longer PINs UCBs.

TYPEVMXA 30.192 z/VM Linux Processor VXAPLSL0 dataset wrong values.

TYPEVMXA 30.190 z/VM 6.1 BROKEN CONTROL RECORD if STSI is 152 bytes.

TYPEDB2 30.194 QMDAACCT field LENACCT=246 caused INVALID 3rd SUBSTR.

TYPE119 30.188 Support for SMF 119 subtype 48 thru 52 (SMTP).

ANALDB2R 30.185 Redesign to execute VFMT102 only once per ANALDB2R.

ANALDB2R 30.186 New "MXG" DB2 reports MXGACC01 and MXGACC02.

VFMT102 30.183 30.05/30.06 VFMT102 could have overlapped range.

VMAC113 30.179 Formula changes from John Burg's SHARE presentation.

BLDFORMT 30.191 JCL Example using CONFIMXG to create FORMAT library.

VMXGSUM 30.189 Use of %CMPRES replaced by %SYSFUNC which is in base.


Major enhancements/corrections added in MXG 30.06, dated Sep 1, 2012:
TYPE120 30.155 Support WebSphere Asynchronous Section 120 Subtype 9.

TYPETAPR 30.164 Support for Tandem Prognosis data files.

TYPEZVPS 30.154 Support XAM/ZVPS VCPU Virtual CPU segment XMUSVCPU

TYPE102 30.175 Support for IFCID=271 DB2 AUDIT PERMISSIONS trace.

TYPE102 30.169 Invalid IFCID=145 QWT02R1L=0 caused ABEND & LOOP.

TYPENTSM 30.159 Support MicroSoft Exchange 2010 incompat changes.

TYPENMON 30.137 Updates to NMON/TOPAS Monitor for AIX and LINUX.

UTILEXCL 30.157 New REPORT THREE-A IMACICEZ, IMACICE1, and IMACICE2.

TYPERACF 30.162 RACF AUDITFID is RACF264 (TYPE80A) or AUDITID (RACF)

TYPE120 30.155 Variable SM1209CX incorrect in TYP1209E.

ASUMUOW 30.166 Optional add PROGRAM and PROG1-PROGnn to PDB.ASUMUOW.

TYPEWWW 30.163 Windows IIS Server Log, strange URIQUERY, looped.

TYPENTSM 30.156 Terminal Service object fields reversed, 2003vs2008R.

ASMRMFV 30.161 RMF III protection/messages for VSAM read I/O error.

TYPERMFV 30.172 RMF III Enhancements.

TYPEDB2 30.173 Spurious INVALID QMDA SEGMENT message eliminated.

VMXGINIT 30.171 Macro variables &PCICMNR and &WCICMNR reinstated.

TYPE110 30.170 Obs count in CICLDR reduced from 1.7M to 70,000.

VGETOBS 30.177 SAS 9.2 z/OS ONLY VGETOBS didn't recognize tape dset.
Major enhancements/corrections added in MXG 30.05, dated Aug 8, 2012:
EXITCICS 30.130 DB2 V10 compressed records "enhanced": NOW WORKS!

(And this VERSION 3 DOES NOT NEED CICS MACRO LIBRARY).

ANALDB2R 30.147 DB2 AUDIT reports updated for DB2PM Version 4.2

TYPE102 30.140 Support for IFCID 269,270 Audit, decodes uniques.

TYPEDB2 30.133 Support for (optional) DB2 Netezza Accelerator data.

TYPEDB2 30.138 ASG TMON/DB2 PTF TE03737 corrects INVALID DB2 RECORD.

VGETALOC 30.135 Dynamic allocation of AUTOALOC=YES LIBNAMEs.

VMXGALOC 30.131 New READONLY and CLEARLL parameters.

TYPE21 30.132 Corrections to SMF 21 calculations of compression.

ANALGRID 30.126 Date range selection did not work.

TYPERMFV 30.151 Additional Enhancements for RMF III processing.
Major enhancements/corrections added in MXG 30.04, dated Jul 4, 2012:
UTILEXCL 30.100 DO NOT USE UTILEXCL in MXG 30.03, "NON-FIRST" error.

TYPE30 30.119 Support for APAR OA39629 HICPUPCT/HICPUPGM TYPE30.


Yüklə 28,67 Mb.

Dostları ilə paylaş:
1   ...   69   70   71   72   73   74   75   76   ...   383




Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©muhaz.org 2024
rəhbərliyinə müraciət

gir | qeydiyyatdan keç
    Ana səhifə


yükləyin