* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
-The Nov 9 change increased arrays from 1999 to 2999 but the correction eliminated the need for the increase, and on site encountered a record too long to sort with the Host sort on z/OS; using the SAS Sort circumvented but the arrays were reset to 1999 on Dec 14.
VMAC117 record (INCOMPATIBLE) that inserted two 26-byte datetime Oct 22, 2016 fields that do NOT match the existing start/end times. IBM Support is being contacted. Change 34.242 If you specified multiple datasets in the INDATA= and VMXGSUM one of those datasets was also the OUTDATA= and there Oct 22, 2016 was no OUTCODE= specified AND YOU had told VMXGSUM to use CLASSNWAY rather than a BY, VMXGSUM would fail with an error message that you could not open the output dataset because it was part of SASDSVX. Now if VMXGSUM sees that the INDATA is not the same as the OUTDATA but the OUTDATA is part of the INDATA and the length of OUTCODE is 0 it turns off CLASSNWAY.
VMACZCOS -Dataset ZCOS01 New Variables Oct 21, 2016 ZCOS01CMAX='CPCMAX' ZCOS01CMIN='CPCMIN' -Dataset ZCOS02 New Variables ZCOS02PMAX='MSUMAX' ZCOS02PMIN='MSUMIN' -Dataset ZCOS04CP New Variables ZCOS04CMAX='CPCMAX' ZCOS04CMIN='CPCMIN' -Dataset ZCOS04GP New Variables ZCOS04MODE='MODE*MESSAGES*ACTIVE*REPORT?' -Dataset ZCOS04PL New Variables ZCOS04ACAP='ABSOLUTE*CAP*TO SET' -These subtype 4 variables are no longer available and are blank:
ZCOS04CCAP ZCOS04CAIP ZCOS04CPIP ZCOS04PAIP ZCOS04PORT ZCOS04CFAM ZCOS04CMOD ZCOS04CSID Change 34.240 New SMF 42 Subtype 27 had JCTJOBID containing HEX zeros VGETJESN which VGETJESN did not like, printing WARNING TYPETASK Oct 19, 2016 NOT DECODED. TEST for nulls in JCTJOBID and SUBSYS of 'SMS' protects this subtype and possible future ones. Thanks to Joe Babcock, General Motors, USA.
VMAC7072 LCPUADDR/SMF70CIN values, which could impact the Dispatch Oct 20, 2016 (CPU) time and other fields in ASUMCELP/ASUMCEC datasets, if "THIS SYSTEM" is in SMT MODE, but ONLY if there were NO type 70 records for this "OTHER SYSTEM". Each RMF 70. record has the details for THIS SYSTEM (70) and for THIS LPAR (70PR), but only incomplete data in TYPE70PR for each of the "OTHER LPARs" on the CEC this LPAR reports. For ASUMCELP/ASUMCEC/TYPE70PR to be perfect, you must read SMF 70 records for ALL SYSTEMS, so there will be a "THIS SYSTEM" obs for every LPAR with complete data, and if you do your own reporting from PDB.TYPE70PR you then must select the "THIS SYSTEM" obs in TYPE70PR using:
dataset has only "OTHER SYSTEM" incomplete data, where these variables always have missing values: SMF70LAC SMF70PAT SMF70WTS SMF70WTU SMF70WTI SMF70WLA and where these variables have incorrect values: LPARCPUS LPARDUR SMF70ONT LPCTBY LPCTOV SMF70WST PCTZIPBY ZIPCPUS ZIPUPTM ZIPPATTM ZIPWSTTM. Variable PARTISHN was not kept in PDB.ASUMCELP, but to select only the "THIS SYSTEM" from PDB.ASUMCELP, use
the number of CP engines ONLINE AND NOT PARKED, the true capacity available, in the "THIS SYSTEM" LPAR obs. But in "OTHER SYSTEM" obs, NRCPUS is the number of ONLINE CPs, because the Parked time is not in the OTHER SYSTEM data. (In RMF Partition Reports, IBM only reads THIS SYSTEM so they have to use the ONLINE count, incorrectly, to calculate the LPAR CPU utilization.) -ARRAY statements with braces changed to parenthesis to avoid character translation issues from ASCII to EBCDIC. Thanks to Peter Sisak, T-SYSTEMS, GERMANY. Thanks to Gabor Markon, T-SYSTEMS, GERMANY. Thanks to Lorinc Homor, T-SYSTEMS, GERMANY.
ANAL3CPC
Oct 19, 2016 Change 34.237 New variables added to STCVSM11 dataset: VMACSTC STC11NHW='BYTES*WRITTEN*HOST*INTERFACE' Oct 12, 2016 STC11NHR='BYTES*WRITTEN*RTD*INTERFACE' STC11NRR='BYTES*WRITTEN*IP*INTERFACE' STC11NRW='BYTES*READ*HOST*INTERFACE' STC11NIR='BYTES*READ*HTD*INTERFACE' See Change 36.084 which corrected these variables. Change 34.236 -If you have multiple SYSPLEX values on a single CEC or VMXG70PR multiple capacity groups then ASUM70LP/ASUMCELP could Oct 12, 2016 have invalid value unless you read all of the data from all of the LPARs involved in the CEC. VMXG70PR now will detect these conditions, WARN you about them and drop the observations that are bad. There are two distinct cases involved. -If the LPAR is not part of the same plex as the system that wrote the 70PR record then that OBS is dropped since the weights will reflect the weights from the LPAR that created the TYPE70PR record. -If the LPAR is not found in the TYPE70 data you will get a WARNING that there is missing data and some may be erroneous for those LPARs that are missing but the OBS are kept. Change 34.235 Cosmetic. Variables DSGNAME and DVLSTGRP had '00'x pad VMACDCOL characters if the name was less than eight bytes that are Oct 11, 2016 now changed to blanks, and variable DSGCSMSS is labeled. Thanks to Scott Barry, SBBWorks Inc., USA. Change 34.234 MQ Series TYPE116 variable WQUSECNT, USE_COUNT, can be a VMAC116 negative value (-1) to represent a CLOSE with (+1) OPEN, Oct 11, 2016 so the INFORMAT &IB.4. is now used instead of &PIB.4. Oct 19, 2016 Variable WTASPRCT is now correctly divided by 4096. Thanks to Scott Barry, SBBWorks Inc., USA.
FORMATS the VALUE statement. Oct 10, 2016 Thanks to Jim Horne, Lowe's Companies, Inc., USA. ======= Changes thru 34.232 were in this MXG 34.07 dated Oct 7, 2016=== Change 34.232 MXG 34.07 first iteration ERROR:ARRAY SUBSCRIPT OUT OF VMAC7072 RANGE due to insufficient testing with enough data in Oct 7, 2016 the TYPE70 Processing. My apology. Thanks to Robert B. Richards, OPM, USA. Change 34.231 MXG 34.07 first iteration lost an "@;" causing STOPOVER. VMAC87 Datetimestamps are now converted to local, $CHARx fields Oct 6, 2016 fields are properly $HEXxx formatted and SMF70DUR valid. Thanks to Keith McWhorter,IBM Global Technology Services, USA. ======= Changes thru 34.230 were in this MXG 34.07 dated Oct 5, 2016=== Change 34.230 Corrections for CDHW support, INVALID DATA messages from. VMACCDHW unprotected PD and PK fields. Oct 5, 2016 -Oct 24. The INPUT of JULDATE was deleted causing missing Oct 24, 2016 and/or wrong values. Change 34.229 Support for DB2 V12 QWHS_MOD_LVL,_REC_INCOMPAT,REC_COMPAT VMACDB2H variables INPUT in DB2 Header but not kept, and adjacent VMACDB2 variable QWHCJOBSTEP that is kept, only in DB2ACCT. VMAC102 -New variables added to DB2STATS: Oct 5, 2016 Q9STCTDA='DISPLAY*ACCEL*COMMANDS' Q9STCTSA='START*ACCEL*COMMANDS' Q9STCTXA='STOP*ACCEL*COMMANDS' Q9STLEN altered to match data, 220 read, Q9STLEN=256. -New Contiguous Buffer Pool variables in DB2STATB QBSTAGET='OVERFLOW*TOTAL*RANDOM*GETPAGES' QBSTASGE='OVERFLOW*TOTAL*SEQUENTIAL*GETPAGES' QBSTASYN='OVERFLOW*TOTAL*SYNC READ*RANDOMS' QBSTASSE='OVERFLOW*TOTAL*SYNC READ*SEQUENTIAL' -QJSTLEN test changed to 256 from 268, +116 VS avail128. -LENQISE test GE 232 changed from 32. -New variables in T102S053 and T102S058: QW0053SECTN='RDI*SECTION*NUMBER' QW0058SECTN='RDI*SECTION*NUMBER' -New variables in T102S199, microsecond resolution. QW0199S1='AVERAGE*SYNC*I/O*DELAY' QW0199S2='MAXIMUM*SYNC*I/O*DELAY' QW0199A1='AVERAGE*ASYNC*I/O*DELAY' QW0199A1='MAXIMUM*ASYNC*I/O*DELAY' -Five new DSNDQXST variables are kept in DB2ACCT and in DB2STATS: QXREFTBL ='REFRESH TABLES' QXTRNOWN ='TRANSFER*OWNERSHIP*AVAILABLE' QXRSDMAD ='DM NOT CALLED RAI PREDETERMINE' QXR1BOAD ='FETCHED ONE BLOCK AN NEVER MORE ' QXSTSFND ='PREPARE SATISFIED FROM SYSDYNQRY' -New fields are added to the end of QW0018 segment QW0018SK='DATA ROWS SKIPPED*INCOMPATIBLE*LOCK HELD' QW0018FI='DATA ROWS INSERTED*VIA*FAST INSERT' QW0018FS='DATA ROWS*COULD NOT*USE FAST INSERT' QW0018FA='DATA FAST INSERT*PIPE*REFILLS' QW0018FW='DATA DB2 WAITS*FOR FAST*INSERT' QW0I18SK='INDEX ROWS SKIPPED*INCOMPATIBLE*LOCK HELD' QW0I18FI='INDEX ROWS INSERTED*VIA*FAST INSERT' QW0I18FS='INDEX ROWS*COULD NOT*USE FAST INSERT' QW0I18FA='INDEX FAST INSERT*PIPE*REFILLS' QW0I18FW='INDEX DB2 WAITS*FOR FAST*INSERT' -The below TYPE 102 IFCID updates can't be made until test SMF data is available; DB2 DSECTS do not document the internal format (TODSTAMP?/SMFSTAMP?/DB2INTERNAL?) nor the epoch date, showing then as only CHAR8 in the DSECT. -New IFCIDS: 389 380 404 413 414 477 -Changed IFCIDS: 018 125 316 401 53 58 with these notes: IFCID 018 Statistics Class 1 Insert Algorithm 2 IFCID 058 Statistics Class 1 Insert Algorithm 2 IFCID 316/401 new wait times for Child/Page/L-Locks/P- IFCIDs 53/58 statement level section for PREPARE Change 34.228 Support for APAR OA48688, ABSOLUTE MSU LPAR GROUP CAPPING VMAC7072 -TYPE70 new variable SMF70ABSMSU='Y' from SMF70HHF bit if Oct 4, 2016 active for this partition. -TYPE70PR new variables CAPLIMCH='HARDWARE GROUP CAPACITY LIMIT CHANGED?' SMF70HGWGRNAME='HARDWARE GROUP OF THIS PARTITION' SMF70HWGR_CAP_LIMIT='HARDWARE*GROUP*ABSLIMIT'
ANALID enhanced to identify which product creates the record and FORMATS with better descriptions, and a footnote added that the Oct 1, 2016 MXG member IMACAAAA contains the MXG Product Suffix XXXX each SMF Record Type, so you know what TYPEXXXX member to use to process that SMF record. (Each IMACxxxx member has the list of datasets that will be created for each XXXX.) Thanks to MP Welch, Bank of America, USA. Change 34.226 -Support for alternate SYSIN ddname input, user control ADOCRMFV of VSAM CLOSE=FREE for RMF III data sets, and other ASMRMFV improvements. Oct 3, 2016 -A new keyword SYSIN=ddname allows ASMRMFV to input parameters from a file with a ddname other than SYSIN. This may be useful if ASMRMFV is executed under another program such as SAS. -The ddname must be a valid ddname for use in JCL and must be present in the execution JCL or an error is flagged. -SYSIN=ddname may ONLY appear in the JCL PARM= field NOT in the SYSIN stream itself. Otherwise an error is flagged.
-The SYSIN=ddname value must NOT be a reserved DDNAME used by z/OS, JES2/JES3, or other important programs. If such a ddname is used an error is flagged. For a full list of these ddnames see documentation Section 5 "Input Data Control Parameters" by SYSIN=ddname. -The OPEN of the DCB for SYSIN or an alternate ddname now validates that DSORG=PS, RECFM=FB or RECFM=F, and LRECL=80 are attributes for the input file to prevent I/O errors and other undesirable behavior. If these criteria are not met ASMRMFV abends during parameter processing. -VFREE (alias VF) and NOVFREE (alias NOVF) are a pair of new parameters that control how RMF Monitor III VSAM data sets are processed when closed. -VFREE deallocates each RMF III data set thus releasing the SHR enqueue for each data set as processed before the entire ASMRMFV step ends while NOVFREE keeps the enqueues for all RMF III data sets until the complete step end. -For step program names ASMRMF* or IKJEFT* (*=any valid program name characters), the default is VFREE. NOVFREE is the default for other step program names. -VFREE/NOVFREE has been tested successfully under z/OS 2.2 but may not necessarily have effect in other z/OS releases. -A new RMFV037I message displays the status of Input Control parameters SYSIN=ddname and VFREE/NOVFREE. -The RMFV035* message did not fully support the TABERR=WARN option. All table errors were counted as Severe Errors rather than as Warnings. -When the only table errors are SPG Internal Problem errors the final return code will now be 0008 instead of 0016. -SPG Internal Problem errors occur when a coded Storage Group name is misspelled or is nonexistent in the RMF III SGSPACE start up parameter. These are NOT fatal to the MXG PDB build process. There simply are no observations in the result ZRBSPG SAS data set in the PDB. The SGSPACE Storage Group name(s) must be corrected for ZRBSPG to have observations. -TIOT ddname search performance is improved. -There is a new Abend Reason Code 40 for a GETDSAB service failure. -Additional descriptive problem text is added for OPEN, CLOSE, and RDJFCB service failure RMFV007S messages. -ASMRMFV could Abend S0C4 if a non-VSAM data set was coded with an RMFV*, RMFC*, or RMFD* DDNAME and then opened as a VSAM data set. Now this condition will be detected and an error flagged. -A new additional RMFV008I message will now display the PDS member name or GDG relative generation if coded in JCL for a file. -The MXG00 record version is raised from X'05' to X'06' and a new Input Options section is added. -SYSIN=ddname and VFREE/NOVFREE features are not supported by ASMRMFV versions prior to MXG Change 34.226. If specified a parameter error will be flagged. -Documentation Section 20 is retitled as "FREE=CLOSE for VSAM Data Sets". -Following documentation sections are updated: Section 5 "Input Data Control Parameters" Section 8 "Error Handling Parameters" Section 12 "Messages" Section 14 "Skipped Records" Section 16 "Return Codes" Section 17 "Abend Reason Codes" Section 20 "FREE=CLOSE for VSAM Data Sets" Section 29 "Summary"
ANALHSM SAS 9.2 or earlier, some graphic statements that should Sep 30, 2016 have been bypassed caused error messages,
FORMATS field's values, from which MXG variable SMF14DSTYPE using VMAC1415 the $MG014EF format, updated by this change. There was Sep 30, 2016 no change made to VMAC1415; listed here for impact only. Change 34.223 Support for APAR OA49415 for SuperPAV Support, adds data: VMAC74 -Added to TYPE74 dataset: VMAC78 2016 SUPERPAV='SUPERPAV*MODE?' Sep 30, 2016 SMF74AGC='CONTROLLER*ALIAS*MANAGEMENT*GROUP*NUMBER' SMF74AGS='ASSOCIATED*ALIAS*MANAGEMENT*GROUP*NUMBER' -Added to TYPE78IO dataset: R783GFLX='IOQ*GLOBAL*FLAGS*EXTENDED' -Added to TYPE78CF dataset: R783AMGC &PIB.1./*CONTROLLER*ALIAS*MGMT*GROUP*NUMBER*/ R783AMGS &PIB.4./*ASSOCIATED*ALIAS*MGMT*GROUP*NUMBER*/ -Added to TYPE78CU dataset: R783XANC='ALIAS*NEEDED*TO START*AN I/O' R783XAUC='ALIAS*USED*TO START*AN I/O' R783XNHC='ALIAS*NEEDED*NONE*AVAILABLE' R783XABC='ALIAS*BORROWED*FROM*PEER LCU' R783XCBC='CONCURRENTLY*BORROWED*ALIAS' R783XHBC='HWM*CONCURRENTLY*BORROWED*ALIAS' R783XALC='ALIAS*LOANED*TO A*PERR LCU' R783XCLC='CONCURRENTLY*LOANED*ALIAS' R783XHLC='HWM*CONCURRENTLY*LOANED*ALIAS' R783CNAG='BORROW*ATTEMPTS*NONE*AVAILABLE' R783XCQD='CUM I/O*QUEUED*WHERE*ALIAS*NEEDED' R783XCIU='CUM ALIAS*DEFINED*AND IN USE'
VMAC42 weren't in the SMF manual for SMF type 42 subtype 19. Sep 30, 2016 Variables added to TYPE42X2 dataset: SMF42JUC='LOW FIXED 4K PAGES IN USE' SMF42JUD='HIGH FIXED 4K PAGES IN USE' SMF42JUE='AVG FIXED 4K PAGES IN USE' SMF42JUF='MAX FIXED STORAGE' SMF42JUG='PCT REAL*CAN BE USED*FOR FIXED' Variables added to TYPE42X4 dataset: SMFA2JUC='LOW FIXED 4K PAGES IN USE' SMFA2JUD='HIGH FIXED 4K PAGES IN USE' SMFA2JUE='AVG FIXED 4K PAGES IN USE' SMFA2JUF='MAX FIXED STORAGE' SMFA2JUG='PCT REAL*CAN BE USED*FOR FIXED' Change 34.221 Support for new SMF Type 29 IMS JAVA CPU and Garbage Coll EXTY29GC creates new datasets EXTY29JA DDDDDD MXG MXG IMAC29 DATASET DATASET DATASET TYPE29 SUFFIX NAME LABEL SUBTYPE TYPS29
VMAC29 TY29GC TY29GC IMS JVM GARBAGE COLLECTION 2 VMXGINIT TY29JA TY29JAVA IMS JVM CPU USAGE 2 Sep 30, 2016 These members were added in MXG 34.01 Change 34.039 but only now has VMAC29 been corrected and validated with data records. Thanks to Tony Curry, BMC, USA. Change 34.220 WARNING R749PCIPAKTR in DROP KEEP RENAME never referenced VMAC74 because it should have been spelled R749PCIPAKT. Warning Sep 27, 2016 is printed only when the MXG OPTION DKROCOND=NOWARN is changed to WARN; MXG expects/exploits DKROCOND=NOWARN as it permits variable names in the KEEP= list that are not output if their optional code is not enabled (especially in CICSTRAN with its many possible optional variables. Thanks to Andrew Krink, Northern Territory Government, AUSTRALIA. Change 34.219 -Variables GDGCOMPL and GDGNOEXT and GDGLIMIT kept. VMAC6156 -New undocumented catalog record '07' has two fields that Sep 24, 2016 are input and kept for investigation. Thanks to Scott Barry, SBBWorks Inc., USA. Change 34.218 Arrays were incorrectly being initialized causing the ASUM4HRS 4HR Averages to not be calculated and the resultant value Sep 24, 2016 for each interval was the interval's value rather than the average value. Note that if you request 4 Hours then there will be no average calculated until the 5th Hour. You may have to read TWO day's SMF to populate the 4 Hour Average for all hours of today. Thanks to Tony P. Steward, CSC, ENGLAND. Change 34.217 -Dataset BVIR30 variables USDCACHE and USDFLASH were INPUT VMACBVIR but were not kept. Sep 22, 2016 -Datasets BVIR301 and BVIR302 were both wrong, having too Sep 26, 2016 few observations and keeping wrong variables. BVIR301 now has one observation for each CACHEPARTNR (0 thru 7) and BVIR302 one for each CONTAINER and Performance Group. Thanks to Pierre Pascal Joulin, SOCGEN, FRANCE.
EXTY9801 HFTS record creates nine new datasets. The TYPE9801 data EXTY98EE set contains all of the segments that occur only once per EXTY98LD record; the eight TYPE98SD-TYPE98SL data sets contain the EXTY98LL segments that can occur more than once per record: EXTY98LS
EXTY98PB DDDDDD MXG MXG EXTY98SD DATASET DATASET DATASET EXTY98SL SUFFIX NAME LABEL EXTY98WU
FORMATS TY9801 TYPE9801 TYPE 98 HFTS SUBTYPE 1 IMAC98 TY98SD TYPE98SD HFTS SPINLOCK DETAIL TYPE98 TY98LS TYPE98LS HFTS LOCK SUSPEND SUMMARY TYPS98 TY98LD TYPE98LD HFTS LOCK SUSPEND DETAIL VMAC98 TY98LL TYPE98LL HFTS LOCK LOCAL CML DETAIL VMXGINIT TY98PB TYPE98PB HFTS PRIORITY BUCKET Sep 20, 2016 TY98EE TYPE98EE HFTS CONSUME EXECUTION EFFICIENCY Aug 17, 2016 TY98WU TYPE98WU HFTS CONSUME WORK UNITS TY98SL TYPE98SL HFTS CONSUME SPIN LOCK SUMMARY Thanks to Nicholas Jones, IBM, USA. Thanks to Daniel V. Rosa, IBM, USA.
VMACPROS which INCOMPATIBLY replaced 60 bytes after PROCSTEP with Sep 22, 2016 102 bytes, causing misalignment of all subsequent fields but only impacting the PRORECOV dataset. Thanks to Robert Chavez, Florida Power and Light, USA.
VMAC30 -VMAC30, datasets TYPE30_V/TYPE30_4/TYPE30_5/TYPE30_6: VMAC42 new variable SMF30SLM='MEMLIMIT*ACTION*TAKEN*FLAGS' VMAC74 -VMAC42, dataset TYPE42S1: was wrong, 16-bytes skipped. VMAC79 new variable SMF42FY3='VALID*COUNTS*FLAGS' VMAC90A Initially, I thought IBM had inserted 16 bytes but they VMXGINIT have been there at least since z/OS 1.13. But, when I EXTY9038 thought I was going to have to test for version, users EXTA9038 found these values in their data: EXTB9038
EXTY9039 PRODUCT SUBTYPES PRODLVL Sep 18, 2016 CA PDSMAN 24 7.7.0 MVS/OS390 10 HDZ1D10 MVS/OS390 10 HDZ2220 Z/OS18 15/17/18/19 DFSMVS18 DFSMS/MVS 1/5/6 HDZ1D10 DFSMS/MVS 1/5/6 HDZ2220 DFSMS/MVS 4 1.3.0 MVS/DFP 2 HDZ1D10 MVS/DFP 2 HDZ2220 Z/OS DFSMS 9 1.12.0 Z/OS DFSMS 20/21/24 V01R13M0 Z/OS DFSMS 20/21/24/25 V02R02M0 Z/OS DFSMS 27 HZD2220 -VMAC42, dataset TYPE42S2 new variables: SMF42FSH='COMP1*CLASS4*LOCKS' SMF42FSI='COMP1*CLASS4*TRUE*CONTENTION' SMF42FSJ='COMP1*CLASS4*FALSE*CONTENTION' SMF42FSK='COMP1*CLASS4*RELEASE*LOCKS' -VMAC42, dataset TYPE42S3 new variables: SMFA2FPHA='COMP1*CLASS4*LOCKS' SMFA2FPIA='COMP1*CLASS4*TRUE*CONTENTION' SMFA2FPJA='COMP1*CLASS4*FALSE*CONTENTION' SMFA2FPKA='COMP1*CLASS4*RELEASE*LOCKS' -VMAC74, dataset TYPE74CA new variable R745CFDV='FAILING*DEVICE' -VMAC77, dataset TYPE77 new variables SMF77CSC='CONTENTION*STATUS*CHANGE*EVENTS' SMF77NOD='NO*SEPARATE*CONTENTION*DETAIL' -VMAC79, variables R79ETCMW/R79ECTRD could be missing values, test for APAR additions revised. -VMAC90A, Support for new datasets from new subtypes: TY9038 TYPE9038 38:SET IEFOPZ TYA038 TYPE9038A 38A:OLD NEW DSNAME TYB038 TYPE9038B 38A:DD JOBNAME TY9039 TYPE9039 39:SET SMFLIM
EXT11981 Service creates new dataset FORMATS DDDDDD DATASET DESCRIPTION IMAC119 T11981 TYP11981 INTRUSION DETECTION SERVICE VMAC119 VMXGINIT
Sep 16, 2016 Thanks to Nathan Loewenthal, CitiGroup, USA. Change 34.212 The ANALID report value for MVSLEVEL was incorrectly read VMACSMF when the VSAM SMF file was input; an +OFFSMF was needed. Sep 16, 2016 Thanks to MP Welch, Bank of America, USA. Change 34.211 Support for SMF 80 TOKDANAME='TOKMFILEPROCMAX' adds new VMAC80A variable TOKMFILEPROCMAXNR. Yüklə 28,67 Mb. Dostları ilə paylaş:
|