* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
SMF19SUT Number of additional free tracks SMF19SNC Number of complete cylinders in largest free extent
SMF19SNT Number of additional free tracks in largest free extent SMF19SNE Number of free extents The following five new counters apply only to the track-managed space on the volume. For volumes with no cylinder-managed space (SMF19CYM is off) these counters are the same as the previous five counters for the whole volume.
SMF19BUC Number of free complete cylinders SMF19BUT Number of additional free tracks SMF19BNC Number of complete cylinders in largest free extent
SMF19BNT Number of additional free tracks in largest free extent SMF19BNE Number of free extents The following new fields provide volume size information SMF19TRK Total number of tracks on the volume SMF19TRM Total number of tracks in track-managed space when SMF19CYM = '1' to the value of SMF19TRK otherwise. When SMF19CYM ='1' this value is also the address where cylinder-managed space begins.
JCLIMSL6 in a single job with JCLIMSL6 or using TYPEIMS7, because Mar 11, 2009 the IMS version is not provided in the log records. You must EDIT the MACRO _IMSVERS nn % to tell MXG what IMS version's records are to be read. The original way was to define _IMSVERS in your IMACKEEP member, but if you have two different versions, you needed to create two special tailoring PDS libraries, each with only the that IMACKEEP member, and then override the //SOURCLIB DD to place this tailoring library ahead of the "USERID" and "MXG" source libraries; do-able, but messy at the least. To eliminate all that stuff, the JCLIMSL6 example now has added, in //SYSIN stream for the TESTIMSB/TESTIMSA: %LET MACKEEP= MACRO _IMSVER 10.0 % ; which overrides the IMSVER definition in either your IMACKEEP member or in your IMACIMSA, so that you do NOT have to EDIT either of those members into your USERID to define the IMS Version.
that read the native IMS log records, TYPEIMSx. It does not apply to these vendor products that create their own IMS data which contain the IMS version number and which can be concatenated or have multiple versions input in one job: TYPECIMS/TYPESVIE/TYPEITRF/TYPETIMS. Thanks to Herbert Sweeney, Verizon, USA.
VMAC110 fields in CICSTRAN were INSERTed rather than APPENDed to Nov 20, 2008 the SMF 110 Subtype 1 records: Dec 17, 2008 BFDGSTCT='EXEC*CICS*BIF*DIGEST*COMMANDS' Jan 12, 2009 BFTOTCT ='EXEC*CICS*BIF DEEDIT*BIF DIGEST*COMMANDS' Mar 10, 2009 ECEFOPCT='EVENT*FILTER*OPERATIONS' EXCICECC ECEVNTCT='EVENTS*CAPTURED' EXCICPGD ECSIGECT='SIGNAL*EVENTS*CAPTURED' EXCICEPG EICTOTCT='EXEC*CICS*REQUESTS' EXCICECG MAXTTDCN='MAXTTDLY*WAIT FOR*T8 TCB*COUNT' EXCICECR MAXTTDTM='MAXTTDLY*WAIT FOR*T8 TCB*DURATION' VMXGINIT MLXSSCCN='XML*SYSTEM*SERVICES*CPU*DISPATCHES' UTILEXCL MLXSSCTM='XML*SYSTEM*SERVICES*CPU*DURATION' IMACCICS MLXSSTDL='TOTAL*DOCUMENT*LENGTH' Mar 14, 2009 T8CPUTCN='T8CPUT*JVM*MULTITHREADED*COUNT' T8CPUTTM='T8CPUT*JVM*MULTITHREAD*DURATION' TIASKTCT='EXEC*CICS*ASKTIME*COMMANDS' TITOTCT ='EXEC*CICS*ASK/CONVERT/FORMAT*TIME*CMDS' WBATMSNM='ATOMSERVICE*RES DEF*NAME*USED' WBPIPLNM='PIPELINE*RES DEF*NAME*USED' WBPROGNM='PROGRAM NAME*FROM URIMAP*RES DEF' WBSVCENM='WEBSERVICE*RES DEF*NAME*USED' WBURIMNM='URIMAP*RES DEF*NAME*MAPPED' WBSVOPNM='WEBSERVICE*OPERATION*NAME' MLXMLTCT='EXEC*CICS*TRANSFORM*REQUESTS' WSACBLCT='WSACONTEXT*BUILD*REQUESTS' WSACGTCT='WSACONTEXT*GET*REQUESTS' WSAEPCCT='WESAEPR*CREATE*REQUESTS' WSATOTCT='TOTAL*WS-ADDRESSING*REQUESTS' WBSFCRCT='SOAPFAULT*CREATE*REQUESTS' WBSFTOCT='TOTAL*SOAPFAULT*REQUESTS' WBISSFCT='INVOKE*XXXSERVICE*SOAP*FAULTS' WBSREQBL='SOAP*REQUEST*BODY*LENGTH' WBSRSPBL='SOAP*RESPONSE*BODY*LENGTH' JVMTHDTM='JVMSERVER*THREAD*WAIT*DURATION' JVMTHDCN='JVMSERVER*THREAD*WAIT*COUNT' WMQASRTM='WEBSPHERE*MQ*API*CPU SRB*DURATION' WMQASRCN='WEBSPHERE*MQ*API*CPU SRB*COUNT' -Three new TCBs are added to the CICDS Dispatch Statistics and CICINTRV datasets, T8, EP, and TP, but only T8CPUT is contained in the CICSTRAN data at present. And the TCB Numbers have changed, as shown in this table, but since the TCB 2-character name is used to identify the TCB, this (fortunately) caused no incompatibility in CICDS: See Change 27.200 for updated table. -New Pool added to STID=60, CICDSPOO for MAXTHRDS TCBs. -CICS Statistics STID=11, dataset CICXMR has new variables XMRCHGAG XMRCHGDT XMRCHGUS XMRGRFRM XMRINSAG XMRINSDT XMRINSUS -CICS Statistics STID=12, dataset CICXMC has new variables XMCCHAGT XMCCHGTM XMCCHUSR XMCDEFSR XMCINAGT XMCINSTM XMCINUSR
-CICS Statistics STID=21, dataset CICVT, has new variables A03LUHWM A03LUNUM A03PSEC A03PSIC A03PSNC A03PSOC A03PSUC A03PSTYP A03PSDIN -CICS Statistics STID=42, dataset CICTQR new variables TQRCHGDT TQRGRFRM TQRCHGAG TQRCHGUS TQRINSAG TQRINSDT TQRINSUS
-CICS Statistics STID=52, dataset CICCONSR new variables A14CHGDT A14GRFRM A14CHGAG A14CHGUS A14INSAG A14INSDT A14INSUS -CICS Statistics STID=67, dataset CICFCR new variables A17CHGAG A17CHGDT A17CHGUS A17GRFRM A17INSAG A17INSDT A17INSUS
-CICS Statistics STID=74, dataset CICIMQ new variables CMQBUFMH CMQCB CMQCHGAG CMQCHGDT CMQCHGUS CMQCRTMH CMQCRTNE CMQCTL CMQDLTMH CMQDLTMP CMQGRFRM CMQINQMP CMQINSAG CMQINSDT CMQINSUS CMQMHBUF CMQRESYN CMQSETMP CMQSTAT CMQSUB CMQSUBRQ -CICS Statistics STID=102, dataset CICDB2RE new variables D2RCHGAG D2RCHGDT D2RCHGUS D2RGRFRM D2RINSAG D2RINSDT D2RINSUS
-CICS Statistics STID=104, dataset CICWBR new variables WBRCHGAG WBRCHGDT WBRCHGUS WBRGRFRM WBRINSAG WBRINSDT WBRINSUS WBRNAME WBRUSAGE -CICS Statistics STID=105, dataset CICPIR new variables PIRCHGAG PIRCHGDT PIRCHGUS PIRGRFRM PIRINSAG PIRINSDT PIRINSUS
-CICS Statistics STID=106, dataset CICPIW new variables PIWCHGAG PIWCHGDT PIWCHGUS PIWGRFRM PIWINSAG PIWINSDT PIWINSUS -CICS Statistics STID=108, dataset CICTCPIP new variables SORCHGAG SORCHGDT SORCHGUS SORGRFRM SORHOST SORINSAG SORINSDT SORINSUS SORIPADR SORIPFAM SORMXDAT SORTRNID SORURM -CICS Statistics STID=109, dataset CICISR new variables ISRCHGAG ISRCHGDT ISRCHGUS ISRFSICQ ISRFSICR ISRFSICS ISRGRFRM ISRINSAG ISRINSDT ISRINSUS ISRIPADR ISRIPFAM ISRLAUTH ISRRMTST ISRTRBYR ISRTRBYS ISRTRREQ -CICS Statistics STID=111, dataset CICTCPIP new variables IIRCHGAG IIRCHGDT IIRCHGUS IIRGRFRM IIRINSAG IIRINSDT IIRINSUS
-CICS Statistics STID=112, dataset CICDHD new variables DHDCHGAG DHDCHGDT DHDCHGUS DHDGRFRM DHDINSAG DHDINSDT DHDINSUS -CICS Statistics STID=114, dataset CICTCPEJ new variables EJRASSRT EJRCHGAG EJRCHGDT EJRCHGUS EJRGRFRM EJRINSAG EJRINSDT EJRINSUS EJRIPADR EJRIPFAM -New CICS stats STID=120, new dataset CICPGD='PROGRAM DEF (RESOURCE) ID' new variables: PGDAPI PGDCHGAG PGDCHGDT PGDCHGUS PGDCONCU PGDDATLO PGDDYNAM PGDEXECK PGDEXEKY PGDGRFRM PGDINSAG PGDINSDT PGDINSUS PGDJVM PGDJVMPR PGDLANG PGDLANGD PGDPGMTY PGDREMOT PGDRMTPG PGDRMTSY PGDRMTTR PGDRUNEN -New CICS stats STID=140, new dataset CICECG='EVENTBINDINGS (GLOBAL) ID' new variables: ECGFLTOP ECGCAPTU ECGDISAB -New CICS stats STID=142, new dataset CICEPG='EVENTPROCESS (GLOBAL) ID' new variables: EPGCUEVQ EPGCUTRQ EPGDSPAT EPGDSPCU EPGDSPPK EPGEVTCU EPGEVTTR EPGEVTTS EPGEVTWM EPGNOREV EPGPKEVQ EPGPKTRQ EPGPRIEV EPGPUTEV EPGSYNEV EPGTRDEV EPGTRNEV -New STIDs 141 and 143 are structurally supported, but only the _CICCMN variables are output, awaiting test data records to validate. STID DATASET DESCRIPTION 141 CICECR EVENTBINDINGS (RESOURCE) ID 143 CICECC CAPTURESPEC RESOURCE ID -See Change 27.200: MXG 27.08 now supports STID 141,143. -CICS/TS 4.1 is still a BETA release, so IBM may choose to add, or remove, any of these fields in their GA release. -See Change 27.200 for Support for CICS/TS 4.1.0 GA. -Old notes "ADDED IN CICS 4.1.0" were not CICS/TS 4.1, but are now "ADDED IN CICS/ESA 4.1.0", from 1994!
ANAL119 from IBM type 119 records (MXG Member TYPE119) for the May 7, 2009 analysis of FTP and Telnet usage, very similar to the ANALTCP reports from SMF 118 records (which was also contributed by Steve, by Change 18.091 in April, 2000! Excellent comments in the ANAL119 member document these sample reports, but don't contact Steve for help; any problems should be directed to support@mxg.com. Thanks to Steve Clark, DHL, USA. Thanks to R. Wells, American General Finance, USA. Change 27.030 -Only the last MDISK segment in XAMDEV records was output EXXAMDEM in the XAMDEV dataset, but there can be many MDISKs, so IMACXAM the new XAMDMINI dataset is created, outputting all MDISK VMACXAM segments, containing these MDISK-specific variables: VMXGINIT DNMDISKS MDSKADDR MDSKDIST MDSKECYL MDSKOWNR MDSKSAMP Mar 6, 2009 MDSKSCYL MDSKWRIT MDSKZERO UDSKDIST UDSKSAMP UDSKUSER Mar 17, 2009 UDSKZERO USSKWRIT and ALL those variables were removed from XAMDEV dataset. -The IODCAD logic had a typo, testing for 3390 instead of for 3990, so the 3990 variables in XAMDEV dataset were always missing values. -These MTRPAG variables were kept in XAMSYS but not in the dataset XAMDEV: PGS1 PGS2 PGS3 CALCYLPA CALCYLSP CALCYLPR CALEXTPG CALEXTPS CALEXTPP Thanks to Douglas C. Walter, Citigroup, USA. Change 27.029 Support for BMC's Ultra Op Product's User SMF record EXULOPIN creates new dataset ULTRAOP. FORMATS IMACULOP
TYPEULOP TYPSULOP
VMACULOP VMXGINIT
Mar 4, 2009 Thanks to Tony Curry, BMC, USA. Change 27.028 -Support for NMON Nigel's Monitor for AIX/Linux under zVM, EXNMONPO record type 'VM' adds 37 new variables to the NMONINTV IHDRNMON Interval dataset. The descriptor record for 'VM' is not IMACNMON consistent; sometimes its second word is the expected VMACNMON Tnnnn snapshot value, sometimes that value is missing. VMXGINIT DIRTY='NR*DIRTY' Mar 13, 2009 WRITEBACK='NR*WRITEBACK' UNSTABLE='NR*UNSTABLE' PAGETABLEPAGES='NR*PAGE*TABLE*PAGES' MAPPED='NR*MAPPED' SLAB='NR*SLAB' PGPGIN='PGPGIN' PSPGOUT='PGPGOUT' PSWPIN='PSWPIN' PSWPOUT='PSWPOUT' PGFREE='PGFREE' PGACTIVATE='PGACTIVATE' PGDEACTIVATE='PGDEACTIVATE' PGFAULT='PGFAULT' PGMAJFAULT='PJMAJFAULT' PGINODESTEAL='PGINODESTEAL' SLABSCANNED='SLABS*SCANNED' KSWAPDSTEAL='KSWAPD*STEAL' KSWAPINODESTEAL='KSWAPD*INODESTEAL' PAGEOUTRUN='PAGEOUTRUN' ALLOCSTALL='ALLOCSTALL' PGROTATED='PGROTATED' PGALLOCHIGH='PGALLOC*HIGH' PGALLOCNORM='PGALLOC*NORMAL' PGALOCDMA='PGALLOC*DMA' PGREFILLHIGH='PGSTEAL*HIGH' PGREFILLNORM='PGSTEAL*NORMAL' PGREFILLDMA='PGREFILL*DMA' PGSTEALHIGH='PGSTEAL*HIGH' PGSTEALNORM='PGSTEAL*NORMAL' PGSTEALDMA='PGSTEAL*DMA' PGSCANKSWAPDHIGH='PGSCAN*KSWAPD*HIGH' PGSCANKSWAPDNORM='PGSCAN*KSWAPD*NORMAL' PGSCANKSWPADDMA='PGSCAN*KSWAPD*DMA' PGSCANDIRECTHIGH='PGSCAN*DIRECT*HIGH' PGSCANDIRECTNORM='PGSCAN*DIRECT*NORMAL' PGSCANDIRECTDMA='PGSCAN*DIRECT*DMA' -Support for record type 'POOLS' creates new NMONPOOL dataset with these variables: ENTITLED='ENTITLED' ENTITLED_POOL_CAPACITY='ENTITLED*POOL*CAPACITY' MAX_POOL_CAPACITY='MAX*POOL*CAPACITY' POOL_BUSY_TIME='POOL*BUSY*TIME' POOL_ID='POOL*ID' POOL_MAX_TIME='POOL*MAX*TIME' SHCPUS_IN_SYS='SHCPUS*IN*SYS' SHCPU_BUSY_TIME='SHCPU*BUSY*TIME' SHCPU_TOT_TIME='SHCPU*TOT*TIME' -New IHDRNMON "NMON infile" exit is taken after RECTYPE has been INPUT so that unwanted record types can be deleted prior to processing. But use carefully; if you delete the wrong records, you could end up with nothing output to the NMON datasets. And the &IHDRNMOH macro variable is also defined so the exit can be defined in your //SYSIN with %LET IHDRNMOH= %quote ( your code ) ; -Erratic JFSFILE records with 38 instead of 36 fields have been observed, but that is a problem with NMON, not MXG. Thanks to Long Nguyen, DHS, USA. Thanks to Marvin Einarson, DHS, USA. Thanks to Steven Olmstead, Northwestern Mutual, USA.
VMAC42 milliseconds, but MAXRSPTM incorrectly had TIME12.2. Now Mar 2, 2009 all have 6.3 format and milliseconds in their label. Thanks to Karl Lasecki, Chemical Abstracts Service, USA. Change 27.026 Variable SMF88LTD='TIMESTAMP WHEN*SMF INTERVAL*EXPIRED' VMAC88 was usually wrong, as the GMT Offset was repetitively Mar 2, 2009 applied. Also, the GMT offset was never applied if the GMT Offset was positive. Change 27.025 Support for z/OS 1.11. EXTY8224 -TYPE 0. New variable: EXTY8225 CVTTZ ='CVTTZ*TIME DIFFERENCE*LOCAL*TO GMT' EXTY8226 -TYPE1415. NO NEW DATA, but lots of text inserts about IMAC82 assembling the IFGSMF14 Macro with DSECT=YES, which is VMAC0 why it is flagged in the SMF Manual as changed. VMAC82 -TYPE30. NO NEW DATA, only one line of text updated. VMXGINIT -TYPE82. New subtypes 24, 25, and 26. May 2, 2009 -TYPE92. Subtype 15 now documented, but MXG supported was added in Change 26.277 for APAR OA24208. -TYPE1415 New variables DCBEEX31 XTIOTYES created from SMF14FLGS. Change 27.024 If only PMACC04 was requested, a NOT SORTED ERROR for the ANALDB2R DB2SUMRY dataset occurred. Some additional corrections to Feb 28, 2009 PMACC01/PMACC02 (short reports had LOCK suspends reported under the PREFETCH column, and WRITE IMMEDIATES under the LOCKS column, and time formats match DB2PM (TIME12.6). Thanks to Paul Volpi, UHC, USA. Change 27.023 Variables S17FBKNM S17FEXNM and S17FMFNM are now KEPT in VMAC117 dataset S117NODE so that it can be combined with S117FLOW Feb 27, 2009 dataset so the Execution Group and Flowname to which the Node belongs can be known. Those variables are also added to the _B117NOD and _B117FLO By List macros. Thanks to Trevor Holland, ANZ, AUSTRALIA Change 27.022 NDM Record 'IK' is now supported, output in NDMDT dataset VMACNDM not because I have a DSECT for that NDM subtype, but Feb 26, 2009 because it appears to have the same structure. Thanks to Herbert Sweeney, Verizon, USA. Change 27.021 QPACxxxx flag variables set from QPACFLGS were not reset, VMACDB2 so if there was more than one NRQPAC segment in a record, Feb 25, 2009 the values could have been wrong. These eight variables QPACDBRM QPACPACK QPACCLS8 QPACCRNT QPACINSP QPACCLS7 QPACPAC could have been carried forward. Thanks to Giuseppe Giacomodonato, E.P.V. Technologies, ITALY. Change 27.020 WEEK70PR failed with VARIABLE INTERVAL NOT FOUND because WEEK70PR - that variable has not existed in ASUM70PR in years, and Feb 25, 2009 - WEEK70PR was way out of date, only supporting 16 LPARs. This change recreates the old INTERVAL (interval count) and was enhanced to support all 60 possible LPARS. Thanks to Atle Mjelde, Ergo Group, NORWAY. Change 27.019 CICS User fields USECOPID/USECUSER/USECBRAN/APPCEMP1 IMACAAAA are supported in listed new IMACICxx CICS exit members. IMACICUA IMACICUA - USECOPID IMACICUB IMACICUB - USECUSER IMACICUC IMACICUC - USECBRAN IMACICUD IMACICUD - APPCEMP1 UTILEXCL VMAC110
Feb 24, 2009 Change 27.018 DB2 V9 variables added by IBM or overlooked now input. VMACDB2 New variables in DB2STAT0/DB2STATS from QWSD segment: Feb 23, 2009 QWSDARTH='ROLLUPS*DUE TO*ROLLUP*THRESH*EXCEEDED' QWSDARSG='ROLLUPS*DUE TO*STORAGE*THRESH*EXCEEDED' QWSDARST='ROLLUPS*DUE TO*STALENESS*THRESH*EXCEDED' QWSDCDTB='NOT ROLLUP*DUE TO*KEY FIELDS*NULL' New variable in DB2STAT0/DB2STATS from QVLS segment: QVLSL254='CONTENTIONS*LATCH CLASS*254' New variables in DB2STAT0/DB2STATS from QVAS segment: QVASCBOS='SUCCEED*SYSEVENT*BOOSTS*THREAD-WAIT' QVASCBOF='FAILED*SYSEVENT*BOOSTS*THREAD-WAIT' QVASMBOS='SUCCEED*SYSEVENT*BOOSTS*THREAD-STORE' QVASMBOF='FAILED*SYSEVENT*BOOSTS*THREAD-STORE' New variables in DB2STAT0/DB2STATS from QSST segment: QSSTGETS='QSST_SGETM*STACK*REQUEST*GETMAINS' QSSTGETR='QSST_SGETR*GET*REQUESTS' QSSTGETE='QSST_SGETEXT*STACK*EXTENSIONS' QSSTFRES='QSST_SFREEM*SEGMENT*FREEMAIN*REQUESTS' QSSTFRER='QSST_SFREER*REQUESTS*TO FREE A*SEGMENT' New variables in DB2STAT0/DB2STATS from QWOS segment: QWOSLUIC='UNREFERNCED*INVERVAL*COUNT' QWOSFLG ='STATUS*FLAG FOR*RMF-API (S)' QWOSRCDE='RETURN*CODE FROM*RMF-API (S)' QWOSRSNC='REASON*CODE FROM*RMF-API (S)' NOTE: DB2 Parameter ZOSMETRICS=YES must be specified to populate these variables. APAR PK62116 applies. With the default NO value, fields contain 'FFFFFFFF'x. New variables in DB2STAT1/DB2STATS from QXST segment: QXCRESEQ QXALTSEQ QXDROSEQ QXPRRESI QXALTVW QXALTCTX QXALTJR QXCRCTX QXCRROL QXDRPCTX QXDRPROL QXMERGE QXRNIX QXSTXMLV QXTRTBL These variables were not INPUT in the DB2STAT1 record, but were deaccumulated; all were labeled and did not raise an uninit warning because they were INPUT in the DB2ACCT record. New variables in DB2ACCT from QXST segment: QXALTCTX QXALTJR QXCRCTX QXCRROL QXDRPCTX QXDRPROL QXMERGE QXRNIX QXSTXMLV QXTRTBL These variables were INPUT but not kept. Variable QBSTLPL in DB2ACCT was not input because its conditional INPUT should have been at 276 vice 280. Thanks to Steve Wood, DST Systems, USA. Thanks to Terry L. Berman, DST Systems, USA.
EXTY80TK their segment-specific variables TOKHOME/TOKPROG to value IMAC80A 'NOHOME' or 'NOPROGRAM', and logic was added to print VMAC80A the first ten instances of undecoded TOKDANAM values with VMXGINIT ***MXGNEWDATA: messages and a hex dump on the SAS log. Feb 20, 2009 -NOTHREADMAX and NOSHMMEMAX non-tokens create new variable Mar 13, 2009 TOKNOTHR and TOKNOSHM with those text values, and real token LDAPHOST decodes and populates new var TOKLDHST. -However, it was discovered that there can be multiple instances of the (301) segment, with different TOKSUBSY values, so these "TOKDANAM-specific" variables TOKASIZM TOKDCE TOKGID TOKHOME TOKLDAP TOKLDHST TOKNOSHM TOKNOTHR TOKPROG TOKUID cannot be kept in the TYPE80nn event datasets, since only the last value would be output. Instead, new TYPE80TK dataset is now created, with both the TOKDANAM-specific variables, and TOKSUBSY, TOKDANAM, TOKCHARV and TOKNUMRV replications to give you easier reporting choices. Thanks to Bill Arrowsmith, EuroClear, BELGIUM. Thanks to Maurice Peek, EuroClear, BELGIUM. Change 27.016 -SMF 42 Subtype 25 (Rename Member), NEWMEMNM/OLDMEMNM were VMAC42 misaligned, because SMF42PF1 plus 3 reserved bytes only Feb 20, 2009 exist in the subtype 24 record. -The three member name fields NEWMEMNM/OLDMEMNM/AORMEMNM in subtypes 24 and 25 are theoretically variable length fields, so they were INPUT x $VARYING8. SMF42PML/QOL, but those lengths are always 8 bytes, so now $EBCDIC8. is used, which also makes them correct under ASCII SAS. -The subtype 25 record has a minor error: SMF42NT/NRTRIPLT the number of triplets, is 3, but 4 triplets are present. The fourth points to ICHRUTKN, so MXG tests the offsets rather than trusting the NRTRIPLT. Thanks to David Kaplan, DTCC, USA.
UDB2GTF -The SORT FIELDS= statement in UDB2GTF must be changed to VMACSMF only sort on the first field; without this change, there Feb 20, 2009 was no error, but the output records were incorrect. -The _GTFDB2 macro now sets ID=101 if IFCID=239 is found. -The massive number of DEBUG statements are no longer printed on the log, unless you choose to enable debugging in the UDB2GTF program. Thanks to Tony Curry, BMC, USA. Thanks to Steve Wood, DST Systems, Inc, USA. Change 27.014 -SAS option TRANSCODE=NO is now set for all $HEX variables DOC so they are NOT translated from EBCDIC to ASCII or vice FORMATS versa. Normally when a SAS dataset is moved between UTILCVRT different platforms (XPORT,CIMPORT,etc.), all character UTILXRF1 variables are translated, but this is most unwelcome for VMXGINIT MXG variables that contain $HEX values (CPUTYPE changed VMXGSUM from '2086'x to '8786'x). The TRANSCODE attribute is set Mar 8, 2009 in SAS V9 with syntax "ATTRIB var1 var2 TRANSCODE=NO;" May 4, 2009 but since it does not exist under SAS V8, and there still are MXG sites limping along on archaic SAS V8, two new GLOBALed macro variables, &MXGNOTRA and &MXGNOTRB, are defined in VMXGINIT by this macro logic: %IF &SASVER GE 9 %THEN %DO; %LET MXGNOTRA= ATTRIB ; %LET MXGNOTRB= TRANSCODE=NO; %END;
%ELSE %DO; %LET MXGNOTRA= * ; %LET MXGNOTRB= ; %END;
and then this statement was added in each of the 300+ members that create $HEX variables &MXGNOTRA var1 var2 var3 &MXGNOTRB ; so the TRANSCODE=NO attribute will be set under SAS V9, but under SAS V8, that statement becomes only a comment. -In addition to variables formatted with the $HEX format, there are character variables that contain hex values but they are formatted with MXG-created $MGxxxxx formats. The FORMATS member was read to select those format names, and lookup format $MGNOTRA was created to validate that these "$MG-HEX" variables also have the TRANSCODE=NO specified. New QA tests read FORMATS to discover any new "$MG-HEX" formats, and update the $MXNOTRA table when new formats are found (if I forget when creating a new one!). -In March, 2009, SAS V9 did not pass the ATTRIB TRANSCODE into a dataset created by a SAS VIEW, but in May, 2009, Yüklə 28,67 Mb. Dostları ilə paylaş:
|