* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
VMACTMNT SYSLOG timestamps, and the creation of new SYLVTIME, Jul 6, 2008 which is then used to improve the accuracy of variables BEGTMNT, ENDTMNT, TOTMNTTM and TAPMTDTM values, some variable labels were revised, and a new MXG Technical Note to document what can still be missed by MXGTMNT. -ML-43 of ASMTAPEE/MXGTMNT now captures the IEF233D mount message in its subtype 8 records (output in TYPESYMT). The IEF233D message is issued for non-ATL, non-VTS first volume mounts from dynamic allocations that don't specify the DEFER option. This message should have been in the initial list (IEF233A, IEC501A, IEC501E) of mount events, but was never observed until now, perhaps because it is relatively infrequent. -ASUMTAPE's logic revises how SYLMTIME, the SYSLOG Mount time is populated; previously, if there was no SYSLOG mount event, the time of a SYSLOG verify message was used to populate SYLMTIME, but now, only mount event messages, IEF233A, IEF233D, IEC501A, or IEC501E, are used. -New logic in ASUMTAPE instead creates variable SYLVTIME, SYSLOG Verify time, using the maximum time value of he IECTMS6, IECTMS9, or IEC7095I SYSLOG messages. -And SYLVTIME is now used in the creation of the ENDTMNT mount event time variable in ASUMTAPE. -The logic for BEGTMNT, ENDTMNT, TOTMNTTM and TAPMNDTM are corrected, revised, and re-labeled: BEGTMNT='BEGIN TIME*OF TAPE*MOUNT EVENT' IF SYLMTIME GT 0 and TMNTTIME GT 0 THEN BEGTMNT=MIN(TMNTTIME,SYLMTIME); ELSE iF SYLMTIME GT 0 THEN BEGTMNT=SYLMTIME; ELSE IF TMNTTIME GT 0 THEN BEGTMNT=TMNTTIME; ELSE BEGTMNT=.; It is the minimum timestamp of the start of the mount event, from SYSLOG or MXGTMNT. ENDTMNT='END TIME*OF TAPE*MOUNT EVENT' IF SYLVTIME GT 0 AND TENDTIME GT 0 THEN ENDTMNT=MAX(TENDTIME,SYLVTIME); ELSE IF SYLVTIME GT 0 THEN ENDTMNT=SYLVTIME; ELSE IF TENDTIME GT 0 THEN ENDTMNT=TENDTIME; ELSE ENDTMNT=.; It is the maximum verification time or mount end, from SYSLOG or MXGTMNT. TOTMNTTM='TIME IT TOOK*TO MOUNT*TAPE VOLUME' IF ENDTMNT GT 0 AND BEGTMNT GT 0 THEN TOTMNTTM=ENDTMNT-BEGTMNT; It is the duration the job was delayed for this tape mount. TAPMTDTM='DURATION*TAPE WAS*MOUNTED*TO DISMOUNT' IF (SYLKTIME GT 0 OR TY21TIME GT 0) AND BEGTMNT GT 0 THEN TAPMTDTM=MAX(SYLKTIME,TY21TIME)-BEGTMNT; It is the duration that the tape volume was mounted on the device for this mount event. -VMACTMNT: New variables, decoded bits from TMNTFLAG, were added to make debugging a little easier: TMNTMSGI='MOUNT MESSAGE ISSUED' TMNTJOBI='JOB*ENDED*EVENT' TMNTJOBC='JOB*CANCELLED*BY*OPERATOR' Thanks to Yves Cinq-Mars, IBM Global Services, CANADA.
VMXG70PR of CP engines in the ASUM70PR and ASUMCEC datasets are Jul 2, 2008 now FORMATted 6.1 to match the LPARCPUS format that was made in Change 26.003. Thanks to Stan Dylnicki, Royal Bank of Canada, CANADA
FORMATS
VMACVMXA Jul 2, 2008 Thanks to Sharon Moir, JPMorgan Chase Bank, USA.
VMACMVCI The CMRTYPE=109 records are written for ABENDs; only the Jul 2, 2008 CMRTYPE=110 records were previously processed by MXG. Variable CMRTYPE was added to both datasets as well. Thanks to David Edge, Thompson Reuters, USA.
FTPSMF all corrected; the syntax /yourname.xxx are all now FTPVB changed to the syntax of just yourname.xxx; that leading JCLFTP slash tried to write to the root directory, which was not NEWSLTRS the desired target destination. SENDDATA
Jul 1, 2008 Thanks to Trevor Ede, EDS, NEW ZEALAND. Change 26.143 The Virtualization Engine TS7700 Statistical data in the VMACBVIR MXG BVIR32 dataset was trashed; these 4 one-byte fields Jun 30, 2008 were not INPUT, causing subsequent variables to be out of alignment: DVAVAD00='00*AVAILABLE*PHYSICAL*DEVICES' DVAVAD01='01*AVAILABLE*PHYSICAL*DEVICES' DVAVAD02='02*AVAILABLE*PHYSICAL*DEVICES' DVAVAD03='03*AVAILABLE*PHYSICAL*DEVICES' Thanks to Josep Miquel Oliver, La Caixa, SPAIN.
VMACDCOL DCDCKDSI='CHECKPOINT*DS*INDICATED?' Jun 30, 2008 DCDCPOIT='CHECKPOINTED*DATASET?' DCDGT64K='GT 64K*TRACK*DATASET?' and new values created for DCDDSORG for HFS and PDSE; unfortunately, DCEDSORT is only three bytes, so the text value for PDSE is set to PDS" DCDDSORG='HFS' for HFS dataset DCDDSORG='PDS' for PDSE dataset These two values are set based on IBM support's reply, as only the bits are documented in the IDCDOUT DSECT, but not the logic: IF DCDPDSE='Y' AND DCDPDSEX=' ' THEN DCDDSORG='PDS'; /*PDSE*/ IF DCDPDSE='Y' AND DCDPDSEX='Y' THEN DCDDSORG='HFS'; /*HFS*/ However, there are several hundred DCOLDSET observations that have DCDDSORG blank, because the three flag bytes whose bits are used to define DCDDSORG, MXG variables DCDSORG1, DCDSORG2 and DCDFLAG3, all contain hex zeroes; a new query back to DCOLLECT technical support is raised. These blank values are believed to be from datasets that were allocated but never opened. Thanks to Trevor Ede, EDS, NEW ZEALAND. Change 26.141 CICS STID=74 (SMF 110 Subtype 2 Statistics) length of 228 VMAC110 was incorrectly documented in DFHMQGDS, causing MXG to Jun 30, 2008 print ERROR (NEW DATA) SKIPPED message on the log. But, MXG's INPUT was off by 4 bytes (Queue Manager is only 4), The INPUT is corrected, the extra reserved bytes are now skipped, that ERROR message is now a WARNING message, and dataset CICIMQ (CICS MQ STATISTICS) is now corrected. Thanks to Ray Dunn, CIGNA, USA. Thanks to Murray Town, Suncorp, AUSTRALIA. Thanks to MP Welch, SPRINT, USA. Thanks to David J Schumann, Blue Cross of Minnesota, USA.
ANALPKGS
Jun 17, 2008 Thanks to Myles M. Reed, NS Corp, USA. Change 26.139 MXG's DOCVER and DOCVERnn members are limited to 72 bytes UTILXRF1 per line, which permitted only 8-byte variable names; MXG UTILVREF now creates some datasets with variable names longer than Jun 17, 2008 8-bytes, so the DOCVER and DOCVERnn members are revised; if the length of the variable is more than 8 bytes, the variable name is printed on a separate line. SAS itself limits variable names to 32 characters.
VMAC80A INPUT STATEMENT EXCEEDED RECORD length, because MXG Jun 17, 2008 didn't expect the changed record. Thanks to Yaohua Hu, ISO, USA. Change 26.137 For QA testing; setting TAPENGN to V9SEQ/V8SEQ is now VMXGINIT only done for MXG under z/OS; MONTHBLD died in QA tests Jun 17, 2008. because V9SEQ does not exist in ASCII versions of SAS.
VMACDB2 -Variable QW0225BB was mis-located in the MXG Input, and VMAC102 should not have been converted to bytes, it is blocks. Jun 17, 2008 Both VMACDB2 and VMAC102 process the IFCID=225 segment. Thanks to Steve Wood, DST Systems Inc, USA.
ASMTAPEE added in ML-41. Change 26.128 revised MXG TYPETMNT code Jun 16, 2008 to use JOB from the SYSLOG message text, while we still try to find the location of that second JOB name. Change 26.134 Cosmetic change; test for length remaining for optional IMACICRD DFHRMI segment for CICS/TS 3.2 added for length 96. Jun 16, 2008 Thanks to Paul C. Gordon, Bank of America, USA. Change 26.133 Complete rewrite of MXG support for CA SYSVIEW, replacing EXSVEV01 the partial support (2005) in TYPESYSV and TYPESYSI. EXSVEV02 The new support now creates seventy-four datasets: EXSVEV03
EXSVEV04 DDDDDD Dataset Description EXSVEV05 token Name EXSVEV06 EXSVEV07 SVEV01 SV01EV01 SVEV01: SYSVIEW AUDIT 01 NOOP EXSVEV08 SVEV02 SV01EV02 SVEV02: SYSVIEW AUDIT 02 START EXSVEV09 SVEV03 SV01EV03 SVEV03: SYSVIEW AUDIT 03 SHUTDOWN EXSVEV10 SVEV04 SV01EV04 SVEV04: SYSVIEW AUDIT 04 SESSION EXSVEV11 SVEV05 SV01EV05 SVEV05: SYSVIEW AUDIT 05 SESSION EXSVEV12 SVEV06 SV01EV06 SVEV06: SYSVIEW AUDIT 06 COMMAND EXSVEV13 SVEV07 SV01EV07 SVEV07: SYSVIEW AUDIT 07 COMMAND EXSVEV14 SVEV08 SV01EV08 SVEV08: SYSVIEW AUDIT 08 THRESHOL EXSVEV15 SVEV09 SV01EV09 SVEV09: SYSVIEW AUDIT 09 STATE MO EXSVEV16 SVEV10 SV01EV10 SVEV10: SYSVIEW AUDIT 10 MONITOR EXSVEV17 SVEV11 SV01EV11 SVEV11: SYSVIEW AUDIT 11 ASID ACT EXSVEV18 SVEV12 SV01EV12 SVEV12: SYSVIEW AUDIT 12 CONSOLE EXSVEV19 SVEV13 SV01EV13 SVEV13: SYSVIEW AUDIT 13 WEB MQ C EXSVEV20 SVEV14 SV01EV14 SVEV14: SYSVIEW AUDIT 14 IMS COMM EXSVEV21 SVEV15 SV01EV15 SVEV15: SYSVIEW AUDIT 15 CICS CEM EXSVEV22 SVEV16 SV01EV16 SVEV16: SYSVIEW AUDIT 16 DSN SERV EXSVEV23 SVEV17 SV01EV17 SVEV17: SYSVIEW AUDIT 17 LPA MODI EXSVEV24 SVEV18 SV01EV18 SVEV18: SYSVIEW AUDIT 18 SVCTABLE EXSVEV25 SVEV19 SV01EV19 SVEV19: SYSVIEW AUDIT 19 SUBSYS M EXSVEV26 SVEV20 SV01EV20 SVEV20: SYSVIEW AUDIT 20 PPT MODI EXSVEV27 SVEV21 SV01EV21 SVEV21: SYSVIEW AUDIT 21 WTOR REP EXSVEV28 SVEV22 SV01EV22 SVEV22: SYSVIEW AUDIT 22 LOGSTREA EXSVEV29 SVEV23 SV01EV23 SVEV23: SYSVIEW AUDIT 23 LOGSTREA EXSVEV30 SVEV24 SV01EV24 SVEV24: SYSVIEW AUDIT 24 PRODUCT EXSVEV31 SVEV25 SV01EV25 SVEV25: SYSVIEW AUDIT 25 LINKSET EXSVEV32 SVEV26 SV01EV26 SVEV26: SYSVIEW AUDIT 26 LINKLIST EXSVEV33 SVEV27 SV01EV27 SVEV27: SYSVIEW AUDIT 27 STORAGE EXSVEV34 SVEV28 SV01EV28 SVEV28: SYSVIEW AUDIT 28 AMRF ACT EXSVEV35 SVEV29 SV01EV29 SVEV29: SYSVIEW AUDIT 29 ESRTABLE EXSVEV36 SVEV30 SV01EV30 SVEV30: SYSVIEW AUDIT 30 TSOTABLE EXSVEV37 SVEV31 SV01EV31 SVEV31: SYSVIEW AUDIT 31 REGPROD EXSVEV38 SVEV32 SV01EV32 SVEV32: SYSVIEW AUDIT 32 DUMPDS M EXSVEV39 SVEV33 SV01EV33 SVEV33: SYSVIEW AUDIT 33 CICSTRAN EXSVEV40 SVEV34 SV01EV34 SVEV34: SYSVIEW AUDIT 34 CICS THR EXSVEV41 SVEV35 SV01EV35 SVEV35: SYSVIEW AUDIT 35 CICS STA EXSVEV42 SVEV36 SV01EV36 SVEV36: SYSVIEW AUDIT 36 MQ QUEUE EXSVEV43 SVEV37 SV01EV37 SVEV37: SYSVIEW AUDIT 37 USER EVE EXSVEV44 SVEV38 SV01EV38 SVEV38: SYSVIEW AUDIT 38 MQ CHAN EXSVEV45 SVEV39 SV01EV39 SVEV39: SYSVIEW AUDIT 39 CICS TS EXSVEV46 SVEV40 SV01EV40 SVEV40: SYSVIEW AUDIT 40 SET EXTN EXSVEV47 SVEV41 SV01EV41 SVEV41: SYSVIEW AUDIT 41 SET GRAN EXSVEV48 SVEV42 SV01EV42 SVEV42: SYSVIEW AUDIT 42 CICS STA EXSVEV49 SVEV43 SV01EV43 SVEV43: SYSVIEW AUDIT 43 CICS SHU EXSVPLOT SVEV44 SV01EV44 SVEV44: SYSVIEW AUDIT 44 DATA SET EXSVTHRE SVEV45 SV01EV45 SVEV45: SYSVIEW AUDIT 45 TASK STA EXSVSTAT SVEV46 SV01EV46 SVEV46: SYSVIEW AUDIT 46 TASK STO EXSVCEXC SVEV47 SV01EV47 SVEV47: SYSVIEW AUDIT 47 JES2 JOB EXSVTSUM SVEV48 SV01EV48 SVEV48: SYSVIEW AUDIT 48 JES2 OUT EXSVTRAN SVEV49 SV01EV49 SVEV49: SYSVIEW AUDIT 49 JES2 OUT EXSVPROG SVPLOT SV02PLOT SVPLOT: SYSVIEW PLOT EXSVFILE SVTHRE SV08THRE SVTHRE: SYSVIEW THRESHOLD EXCEPTI EXSVTMPS SVSTAT SV09STAT SVSTAT: SYSVIEW STATE EXCEPTION EXSVTDTA SVCEXC SV24CEXC SVCEXC: SYSVIEW EXCEPTION EXSVABND SVTSUM SV25TSUM SVTSUM: SYSVIEW CICS TRANS SUMMAR EXSVEXCE SVTRAN SV27TRAN SVTRAN: SYSVIEW CICS TRANSACTION EXSVMEMP SVPROG SV27PROG SVPROG: SYSVIEW CICS PROGRAMS EXSVDLI SVFILE SV27FILE SVFILE: SYSVIEW CICS FILES EXSVTHRS SVTMPS SV27TMPS SVTMPS: SYSVIEW CICS TEMPORARY ST EXSVRESM SVTDTA SV27TDTA SVTDTA: SYSVIEW CICS TRANSIENT DA EXSVDCOM SVABND SV27ABND SVABND: SYSVIEW CICS ABENDS EXSVEXIN SVEXCE SV27EXCE SVEXCE: SYSVIEW CICS EXCEPTIONS EXSVWBMQ SVMEMP SV27MEMP SVMEMP: SYSVIEW CICS MONITOR EMPS EXSVDB2 SVDLI SV27DLI SVDLI: SYSVIEW CICS DL/I EXSVMEIE SVTHRS SV27THRS SVTHRS: SYSVIEW CICS THRESHOLDS EXSVINTV SVRESM SV27RESM SVRESM: SYSVIEW CICS RESOURCE MAN EXSVIMST SVDCOM SV27DCOM SVDCOM: SYSVIEW CICS DATACOM CSF EXSVIMSP SVEXIN SV27EXIN SVEXIN: SYSVIEW CICS EXEC INTERFA EXSVMQRR SVWBMQ SV27WBMQ SVWBMQ: SYSVIEW CICS WEBSPHERE MQ IMACSVIE SVDB2 SV27DB2 SVDB2: SYSVIEW CICS DB2 TYPESVIE SVMEIE SV27MEIE SVMEIE: SYSVIEW CICS MEI EVENT TYPSSVIE SVINTV SV28INTV SVINTV: SYSVIEW CICS INTERVAL SUM VMACSVIE SVIMST SV32IMST SVIMST: SYSVIEW IMS TRANSACTION VMXGINIT SVIMSP SV33IMSP SVIMSP: SYSVIEW IMS PROGRAM SUMMA Jun 17, 2008 SVMQRR SV48MQRR SVMQRR: SYSVIEW MQ APP REGIONS
ASMRMFV RMFSKIP DD was present, ASMRMFV could fail with USER 998 Jun 14, 2008 when attempting to close the nonexistent RMFFILT DDname. Thanks to Jerry Urbaniak, Acxiom, USA. Change 26.131 The reports on MIPS/MSU usage for CP engine is enhanced ASUMMIPS to also report on zIIPs and zAAPs, by adding variables Jul 18, 2008 CPUIFATM CPUZIPTM NRIFAS NRZIPCPU IFAUSED ZIPUSED MIPSIFA MIPSZIP with _MIPSIFA and _MIPAZIP macros that define the factors in the same way as base CP conversion factors. Thanks to Robert Kuhne, Exelon Corporation, USA. Change 26.130 Notes for CICS IMACICEZ, IMACICE1, IMACICE2 tailoring. IMACICEZ These notes originated in Change 24.033, then 25.xxx and IMACICE1 are repeated here, as well as in comments in UTILEXCL IMACICE2 These members are required to be tailored if your CICS UTILEXCL records contain 'EZA01' or 'EZA01' optional segments: Jun 14, 2008 -IMACICEZ always has these 5 fields, identified by their CMODNAME='EZA01' and CMODTYPE='S': EZA01 S 001 12 ooo INIT EZA01 S 002 12 ooo READ EZA01 S 003 12 ooo WRITE EZA01 S 004 12 ooo SELECT EZA01 S 005 12 ooo OTHER
CMODLENG=8, but IMACICEZ supports both lengths, so you just remove the comment block to tailor IMACICEZ and it will process data with either or both lengths. -IMACICE1 can have up to 13 fields, identified by their CMODNAME='EZA01' and CMODTYPE='A' (yes, CMODNAME is the same 'EZA01' as IMACICEZ, but the CMODTYPE is different):
EZA01 A 002 4 ooo TREAD EZA01 A 003 4 ooo TWRITE EZA01 A 004 4 ooo TSELECT EZA01 A 005 4 ooo TOTHER EZA01 A 006 4 ooo REUSABLE EZA01 A 007 4 ooo ATTACHED EZA01 A 008 4 ooo OPENAPI EZA01 A 009 4 ooo TCBLIM EZA01 A 010 4 ooo TREUSABL EZA01 A 011 4 ooo TATTACHE EZA01 A 012 4 ooo TOPENAPI EZA01 A 013 4 ooo TTCBLIM
last CMODHEAD field 'EZA01' instead of the names shown) to know how many fields are in your data. If you have the expected 13 fields, then you just remove the one comment block. If you have fewer fields, then: - Change the IF xxxx GE 52 THEN DO; statement so its test value is 4 times the number of fields, e.g. with seven fields change the "52" to "28". - Change the INPUT statement's suffix from EZA01A13 to the number of fields you have; if there are seven: INPUT (EZA01A01-EZA01A07) (&PIB.4.) @; - Delete the LABELs for variables that don't exist. -IMACICE2 has 22 fields with z/OS 1.7 TCP/IP data, but had only 11 fields with z/OS 1.4, which are identified by the CMODNAME='EZA02' and CMODTYPE='A: EZA02 A 001 4 330 CONN EZA02 A 002 4 331 STARTED EZA02 A 003 4 332 INVALID EZA02 A 004 4 333 DISTRAN EZA02 A 005 4 334 DISPROG EZA02 A 006 4 335 GIVESOKT EZA02 A 007 4 336 SECEXIT EZA02 A 008 4 337 NOTAUTH EZA02 A 009 4 338 IOERR EZA02 A 010 4 339 NOSPACE EZA02 A 011 4 340 LENERR EZA02 A 012 4 341 TCONN EZA02 A 013 4 342 TSTARTED EZA02 A 014 4 343 TINVALID EZA02 A 015 4 344 TDISTRAN EZA02 A 016 4 345 TDISPROG EZA02 A 017 4 346 TGIVESOK EZA02 A 018 4 347 TSECEXIT EZA02 A 019 4 348 TNOTAUTH EZA02 A 020 4 349 TIOERR EZA02 A 021 4 350 TNOSPACE EZA02 A 022 4 351 TLENERR You will HAVE to look at UTILEXCL REPORT THREE to confirm if you have 22 or 11 fields, and remove only one of the two comment blocks in IMACICE2 to tailor it. -You create REPORT THREE with the _RPTEXCL macro run with or after your UTILEXCL execution: //SYSIN DD * %INCLUDE SOURCLIB(UTILEXCL); _BLDDICT; _BLDEXCL; _RPTEXCL;
FORMATS OTHER='UNKNOWN' value statement), and it was not applied VMACTAO to variable TAOTRMCD in VMACTAO until now. Jun 12, 2008 Thanks to Steve Clark, DHL IT Services Americas, USA.
VMACTMNT But you do NOT need to replace the MXGTMNT monitor task Jun 12, 2008 if it is already installed, as this circumvention will correct the error. You will need to reprocess the SMF records created with ML-41 with the new VMACTMNT from this change. The error impacts the PDB.ASUMTAPE dataset; the TYPETMNT data is correct with ML-41 monitor. However, to capture ALL tape mount events, you must use the ASUMTAPE program and then use PDB.ASUMTAPE dataset (and not PDB.TYPETMNT) to capture the DFHSM mounts, 2nd mounts and other mounts that do not go thru the IBM/STC exits; those events are depend on the subtype 8 SYSLOG records in PDB.TYPESYMT that ASUMTAPE combines with TYPETMNT and TYPE21 datasets to capture EVERY mount in PDB.ASUMTAPE.
JOB field in the subtype 8 record with ML-41 is in error as it contains the JCTJOBID value, rather than JOB name, which causes JESNR to be a missing value in PDB.TYPESYMT, which then causes ASUMTAPE to fail to match up the SYSLOG event data with the TYPETMNT and TYPE21 records. This revision to VMACTMNT captures the JOB name from the SYSLOG message text, rather than the JOB field, and the VGETJESN was relocated to use the correct JOB name to decode the JESNR from JCTJOBID. Not an error, but it was observed that the PROGRAM name in the TYPETMNT dataset is always blank; that field was only capturable when the (now archaic) cross-memory XMEM=YES option was used, prior to the exit-driven redesign. Since TYPETMNT has JOB READTIME and JESNR, the PROGRAM can be acquired from the PDB.STEPS dataset. Thanks to Scott Barry, SBBWorks, Inc, USA.
VMACPRPR of a text field, subsequently identified as the PRINTER Apr 11, 2008 between ACCOUNT and SHEETS. The change was made in April Jun 12, 2008 as Change 26.067, but never made it into CHANGES, and the change number was reused. Thanks to Carl Sablon, KBC Bankverzekerinngsholding, BELGIUM. Thanks to Siegfried Trantes, IDG, GERMANY.
VMAC120 Instead of properly using the triplet SM120SRN field to Jun 11, 2008 count the number of Server Region Sections, IBM chose to implement an aberrant design by instead creating 0-n new triplets (offset, length, count) in the record header! This "feature" caused MXG to only output the first data section in dataset TYP120SR. Circumvention code now uses SM120TRN-2 (number of triplets minus two) to loop across the Server Regions. This error was detected because the total number of allocation failures, SM120HIC, was much smaller than expected, and a detail trace identified that only one Server Region was being output. Thanks to Lisa Oulette, Wachovia Information Technology, USA.
EXNTBITS DDDDDD DATASET DESCRIPTION/OBJECT NAME EXNTPACE NTBITS BITSNET BITS NET UTILIZATION EXNTUSB NTPACE PACEPIPE PACER PIPE IMACNTSM NTUSB USB USB VMACNTSM -Jun 17, 2008: Variable PACEINST was misspelled VMXGINIT as PACEPIPE in the _BNTPACE macro definition, causing Jun 17, 2008 the PROC SORT of dataset PACEPIPE to fail. Jun 11, 2008 Thanks to Lisa E. Van Allen, Boeing, USA. Change 26.124 INPUT STATEMENT EXCEEDED for short (possibly defective) VMACITRF type '11'x ITRF record of only 176 bytes; current ITRF Jun 10, 2008 record should be 304 bytes long. The record contains only the Input Terminal and Date and Time and the 4-byte "UNIQUE" hex field; all other fields are nulls or blanks. The observation is still output in ITRFMSGO dataset, and short records can be identified/counted by the variables COT, LOQT, OQT (and others) having missing values. Thanks to Prashant Joshi, Perot Systems, USA.
VMACNTSM FRZRPLBY='FREE AND ZERO*PAGE LIST*BYTES' Jun 9, 2008 MODFPLBY='MODIFIED*PAGE LIST*BYTES' Jun 17, 2008 SBCACOBY='STANDBY*CACHE*CORE*BYTES' SBCANPBY='STANDBY*CACHE*NORMAL*PRIORITY*BYTES' SBCARSBY='STANDBY*CACHE*RESERVE*BYTES' -Support for new field added to NTSMF PROCESS object: WKSETPRV='WORKING*SET*PRIVATE' Thanks to Roger Zimmerman, Hewitt Associates, USA.
ASUMTAPE three comma delimiters. The SAS SCAN function treats all Jun 5, 2008 repeated delimiters as a single delimiter (why, no one at SAS can explain, but that 'feature' is documented!), so the use of TRANWRD(text,',,',', ,') ahead of the SCAN() was suggested, which worked fine with two delimiters. However, IEF234E messages with 'D 0F80,,,ZY11110,STEP099' (unexpected, a dismount with no volser nor PVT/PUB/STR on a 3590 device) were only expanded to 0F80, ,,ZY1110 so the subsequent SCANs returned wrong values in WORD2-5. Now, five TRANWRDs are executed to ensure the SCAN parse properly decodes the JOB and STEP. Thanks to Paul Naddeo, FISERV, USA. Thanks to David Bixler, FISERV, USA. Change 26.121 IBM/Candle/OMEGAMON Audit Records can be buried inside VMACOMAU CICS records; this change protects so only Audit records Jun 4, 2008 are processed by TYPEOMAU. Several variables that do not exist in the Audit records were removed. Thanks to Joseph J. Faska, Depository Trust, USA. Yüklə 28,67 Mb. Dostları ilə paylaş:
|