* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
|
MXG used MRHDRTOD=FLOOR(MRHRTOD); to truncate to whole seconds for the merge, as the value was always :00, but now, the start of the write of the USER records is often near the end of the 00: second (e.g. 0.999919 microsec) and the write extends into the :01 second, and sometime the ACT record is at :00 and INT is at :01, mismatched. Now, MRHDRTOD=FLOOR(MRHDRTOD)-MOD(FLOOR(MRHDRTOD),10); is used to force the minute intervals to always be :00 in the PDB.VXBYUSE MONWRITE dataset.
used to merge VXUSEACT and VXUSEINT datasets to create VXBYUSR previously happened to always be on the same second, so using MRHDRTOD=FLOOR(MRHDRTOD) to truncate that microsecond value to seconds, the merge matched observations correctly. However, the newer data shows that there can be a pair of records with the USEACT record at :00 seconds and the paired USEINT record at :01 seconds, causing that merge pair to create multiple observations. What has happened? The older data shows the start of the write of the USEACT/USEINT pairs began at 0.885 seconds after the pop and the write completed after writing all of them in 478 microsec, in that one second, but the newer data shows the write didn't start until 0.999 secs and the 406 microseconds write time ended in the next second causing ACT at :00 and INT at :01. Some of the new values don't even start write until the :01 second. Sept Data: 03:36:30.885294 Minute 36 Second 30 First USEACT 5 microsec 03:36:30.885299 Minute 36 Second 30 Paired USEINT 471 microseconds (write 78 pairs) 03:36:30.885770 Minute 36 Second 30 Last USEACT 2 microseconds 03:36:30.885772 Minute 36 Second 30 Paired USEINT ==> 78 pair written in 478 microseconds for Minute 36. But new data has pairs with different seconds values: Oct Data: 09:36:00.999919 Minute 36 Second 00 First USEACT 3 microseconds 09:36:00.999922 Minute 36 Second 00 Paired USEINT 76 microseconds (write 21 pairs) 09:36:00.999998 Minute 36 Second 00 First USEACT 2 microseconds 09:36:01.000000 Minute 36 Second 01 Paired USEINT 324 microseconds (write 65 pairs) 09:36:01.000324 Minute 36 Second 01 First USEACT 1 microseconds 09:36:01.000325 Minute 36 Second 01 Paired USEINT ==> 86 pair written in 406 microsec for minute 36. Thanks to Graham Harris, RBS, ENGLAND. ====== CHANGES THRU 36.197 ARE IN MXG 36.09 DATED Oct 18, 2018========== Change 36.197 Reserved Change Number. Change 36.196 Support for new z/OS 2.3 RMF III variables (COMPATIBLE) VMACRMFV added to ZRBASI/ZRBRCDD/ZRBRCDP/ZRBRCDS/ZRBRCDT/ZRBRCDX Oct 15, 2018 and ZRBSVPC. The new variables are listed in DOCVER36. -ZRBASI, existing variables now correctly populated: ZRBDCTIA/ZRBGMN/ZRBGMX/ZRBIDLE/ZRBWNM/ZRBGDE/ZRBDNM.
VMACXAM Serious Error messages and missing output data. Oct 15, 2018 Thanks to Patricia Hansen, ADP, USA. Change 36.194 Yet another invalid LENSR value TYPE42 Subtype 5 ABEND, VMAC42 value LENSR=376 added to Change 36.124. Oct 15, 2018
TYPETMS5 TAPEBYTC and to DSNBRECD as DSNBYTEC. Just like the Oct 11, 2018 TAPEBYTE and DSNBYTE variables (estimates based on BLKSIZE*BLKCNT) these are best guess estimates. Change 36.192 Support for IMS Version 15 (COMPATIBLE) dataset IMS56FA. VMACIMS New string TPCPTHRSESSN contains the pair of TPCPTHRS and Oct 11, 2018 TPCPESSN for up to six External Subsystems, TPCXLEN has the length of the TPCX, still 60 reserved bytes. Thanks to Robert Taylor, Wisconsin Dept of Administration, USA.
VMAC74 R748SCWT R748SNBW R748SNWO R748SNWS R748SNWT were INPUT Oct 11, 2018 and FORMATted and LENGTHed and LABELed incorrectly. Thanks to Steve Olenik, IBM, USA. Change 36.190 A reference line showing the memory allocated to each GRAFWRKX LPAR was added to the memory graph. The scale on the Y Oct 11, 2018 axis is 0 to the MAX memory for any LPAR in the data.
ANAL113 the engine type. Oct 9, 2018 Thanks to Jim Horne, Lowes, USA. Change 36.188 Support for new Bit 4 of SMF30_RAXFLAGS and creation of BUILD005 these new bit-level variables with explanation in label BUIL3005 SMF30_RAXFLAG0='RAX0*USERKEY*COMMON*AUDIT*ENABLED?' VMAC30 SMF30_RAXFLAG1='RAX1*USERKEY*COMON*AUDIT*USAGE?' Oct 16, 2018 SMF30_RAXFLAG2='RAX2*USERKEY*CADS*USAGE?' SMF30_RAXFLAG3='RAX3*USERKEY*CHANGE*KEY*USAGE?' SMF30_RAXFLAG4='RAX4*USERKEY*RUCSA*USAGE?' that are added to TYPE30_4/TYPE30_5/TYPE30_6/TYPE30_V and PDB.STEPS for BUILDPDB (JES2) and BUILDPD3 (JES3). (Variable RAXFLAGS was added in MXG 35.09.) Thanks to MP Welch, Bank of America, USA.
BLDSMPDB when it is necessary to respond to a message. PROCSRCE UTILCPLG
VMXGALOC Oct 5, 2018 Change 36.186 Labels for variables RECORDS, INSERTS, RETRVALS, UPDATES VMAC16 and DELETES are now consistent for these three records. VMAC64 VMACSYNC
Oct 4, 2018 Thanks to Warren Cravey, FMR, USA. Change 36.185 For want of an & PDB= was not honored but always looked GRAFCIMP for the data in PDB. Oct 4, 2018
VMAC84 triplets were misaligned and this was the first instance Oct 3, 2018 of that subtype to test. Oct 11, 2018 -Value of JMFINTRV is 60+ hours, JMFDELTA is 90 minutes, so the two percentage calculations use JMFDELTA. Thanks to Jim Horne, Lowes, USA. Thanks to Joe Faska, DTCC, USA.
VMACPOEX had zero length. Invalid record detected and printed on Oct 3, 2018 log and skipped, while vendor investigates. Oct 18, 2018 -Invalid new triplet record with no SECT segment deleted, Nov 20, 2018 and a record with truncated General Section is deleted. -The GMT offset depends on POEXENDT; if it's missign the offset can't be calculated. Pending a vendor correction, MXG Retains the GMTOFFEX and uses that value instead, which could cause missint values for STRT/ENDT. Nov 20: The Informatica fix number for this problem is PWX-7566 and it will be in code base PWX V10.2.0 Hotfix2 currenly scheduled for Q1 of 2019. Thanks to Scott Wiig, US Bank, USA. Thanks to Jan Tielemans, KBC, BELGIUM. Change 36.182 MXG 36.07-36.08. Possible syntax error in a SYSFUNC due MONTHBLD to Change 36.145, which changed a QCMPRES to a SYSFUNC MONTHBL3 (changed only to protect possible user typing errors) MONTHBL3 but should have used QSYSFUNC, because SYSFUNC saw the MONTHDSK commas as operands and failed. The member from 36.06 all MONTHASC the way to 32.05 can be used. Fortunately, MONTHBLD is PRODTEST normally tailored into the "USERID.SOURCLIB" so the ERROR PRODTESW only impacts new users of the MONTHPDB in 36.07-36.08. Oct 3, 2018 -Dec 31: MONTHBL3 was missing a semicolon, found in QA. Dec 31, 2018 Change 36.181 Support for zVPS USEDIAG segment adds variables DIAGNBR VMACXAM and DIAGVALUE to datasets XMUSVCPU and XAMUSR. Oct 2, 2018 Thanks to Patricia Hansen, ADP, USA. Change 36.180 -UTILBLDP with RMFINTRV=NO and BUILDPDB=YES did not create UTILBLDP PDB.TYPE70 nor the other PDB.TYPE7x datasets. The "NO" Oct 4, 2018 should have suppressed only the %INCLUDE of RMFINTRV in MACRO _INTRMF, but it also suppressed the seven _S7xxxxx data set sort macros. RMFINTRV=YES is automatic with BUILDPDB=YES, and now RMFINTRV=NO and BUILDPDB=YES will create the 70s but not create PDB.RMFINTRV. If you want to build PDB.RMFINTRV and the ASUM70PR datasets from only the 70 and 72 SMF records, see EXAMPLE 3A/3B in UTILBLDP. Thanks to Ralph Gifford, AIG, USA. Change 36.179 Support for USER CICS fields USER3/USER3 and ATOUSER. IMACAAAA
IMACICWZ IMACICXA
VMAC110 UTILEXCL
Sep 28, 2018 Thanks to Richard Baker, ATO, AUSTRALIA. Change 36.178 Target Resource Group dataset TYPE89R2 was incomplete and VMAC89 fields were misaligned. Sep 28, 2018 Thanks to Greg Goshia, Ohio Farmers Insurance, USA. Change 36.177 Reserved Change Number. Change 36.176 Extraneous % in UTILBLDP could cause 180 ERROR and ABEND. UTILBLDP Line 665 had a stray percent sign, MXG 36.08 only. Sep 20, 2018 The EXPDBOUT= argument exposes the error. Thanks to Tom MacCabe, Dominion Energy, USA Change 36.175 Support for SMF 30 User Key CSA Audit Enhancements adds VMAC30 new SMF30_RAXFLAGS to TYPE30_1, TYPE30_V, TYPE30_4 and Sep 28, 2018 the TYPE30_5 datasets. Change 35.212 (MXG 35.09+) Sep Feb 28, 2018 2017 made the code change but the change text was still Sep 20, 2018 a "Reserved Change" until Feb 28, 2018, but had the old 35.212 Change Number, so it was only in CHANGESS member. The IBM Record Change was made by APAR OA53355, but will only be needed thru z/OS 2.3, as User Key Common Storage usage support ends there. This is Health Check ZOSMIGV22R3_NEXT_VSM_USERKEYCOMM. These APARs required no additional code changes: OA53434 Corrects ASM DSECT Lengths, no MXG impact OA53289 Corrects value of SMF30HVR from zero to valid. OA45767 APAR that added the extra triplet caused OA53434 See Change 36.188 which added new bit-level variables.
VMACZCOS these variables, INCOMPATIBLY, due to a new field that Sep 21, 2018 was inserted prior to a triplet. Dataset ZCOS01: ZCOS01PC4HA='TOTAL*CATEGORYA*R4H OF LPARS' ZCOS01PC4HB='TOTAL*CATEGORYB*R4H OF LPARS' ZCOS01PC4HM='TOTAL*MOBILE*R4H OF LPARS' ZCOSDETO='SMF*INTERVAL*END*TIME' ZCOSDDTO='SMF*INTERVAL*DURATION' ZCOSDOTO='GMT*OFFSET' Dataset ZCOS02: ZCOSPR4HA='4H CATEGORYA MSU AVERAGE' ZCOSPR4HB='4H CATEGORYB MSU AVERAGE' ZCOSPR4HM='4H MOBILE MSU AVERAGE' ZCOSPS4H ='4H TOTAL MSU AVERAGE AT SMF IV TIME' ZCOSPS4HA='4H CATEGORYA MSU AVERAGE AT SMF IV TIME' ZCOSPS4HB='4H CATEGORYB MSU AVERAGE AT SMF IV TIME' ZCOSPS4HM='4H MOBILE MSU AVERAGE AT SMF IV TIME' ZCOSPSTIM='ZCOSPSTIM*DATETIME*STAMP' Dataset ZCOS04GP: ZCOSMOBT='MOBILE*TARGET*R/S/D' ZCOSCMPR='MANAGE*BILLING*CPM?' ZCOSCMPF='CMP*FLYING*MSU MGT?' Dataset ZCOS04CP: ZCOS04CTHR='CPC*CONTROL*THRESHOLD' Dataset ZCOS04LP: ZCOS04PDLV='MSU*DISTRIB*LEVEL*BOUNDARY'
EXCMFV02 MD73 utility creates these 28 new RTIN records, which EXCMFV09 create these 44 new datasets with CMRDETL information. EXCMFV0C
EXCMFV0D EXCMFV0F DDDDDD Dataset Description EXCMFV10 EXCMFV16 CMFV10 CMFV10 Address Space 10 ADRE EXCMFV17 CMFV16 CMFV16 Lock 16 LKRE EXCMFV18 CMFV17 CMFV17 VSAN RLS Activity 17 RLRE EXCMFV20 CMFV18 CMFV18 VSAM RLS LRU 18 RURE EXCMFV21 CMFV181 CMFV181 DEVICE 83 DLRE EXCMFV2E CMFV20 CMFV20 COUPLING FACILITY EXCMFV34 CMFV21 CMFV21 System Summary 21 SLRE EXCMFV46 CMFV2E CMFV2E Data Set 23 DSRE EXCMFV47 CMFV34 CMFV34 Unix Process 34 UPRE EXCMFV48 CMFV46 CMFV46 PROCESS EXCMFV49 CMFV47 CMFV47 WLM Extended Period 47 MXRE EXCMFV50 CMFV48 CMFV48 WLM Addr Space/Enclave 48 MTRE EXCMFV51 CMFV49 CMFV49 WLM Enclave Classify 49 MCRE EXCMFV52 CMFV50 CMFV50 XCF Path 50 XPRE EXCMFVES CMFV51 CMFV51 XCF System 51 XSRE EXCMFV54 CMFV52 CMFV52 XCF Source/Destination 52 XDRE EXCMFV70 CMFVES CMFVES ES CRITERIA 53 ---- EXCMFV71 CMFV54 CMFV54 WLM Server 54 MWRE EXCMFV72 CMFV70 CMFV70 System Summary 70 SBRE EXCMFV73 CMFV71 CMFV71 Device 71 DBRE EXCMFV74 CMFV72 CMFV72 Address Space 72 ABRE EXCMFV80 CMFV73 CMFV73 WLM 73 WBRE EXCMFV81 CMFV74 CMFV74 LPAR 74 LBRE EXCMFV82 CMFV80 CMFV80 ZFS Aggregate 80 ZSRE EXCMFVC0 CMFV81 CMFV81 ZFS Cache 81 ZCRE EXCMFVC1 CMFV82 CMFV82 PCIE Activity 82 PCRE EXCMFVC2 CMFVC0 CMFVC0 PROCESS C0 PRRE EXCMFVC4 CMFVC1 CMFVC1 THREAD C1 THRE EXCMFVCC CMFVC2 CMFVC2 MOUNTED FILE SYSTEM C2 FMRE EXCMFVCD CMFVC4 CMFVC4 SYSTEM PARAMETERS C4 PMRE EXCMFVCE CMFVCC CMFVCC PROCESS/TTY CC P1RE EXCMFVCF CMFVCD CMFVCD VSAM COMMON STORAGE CD P2RE EXCMFVD0 CMFVCE CMFVCE PROCESS/COMMAND CE P3RE EXCMFVD1 CMFVCF CMFVCF USS PROCESS CWD CF CFRE EXCMFVD2 CMFVD0 CMFVD0 MOUNTED FS/MOUNT POINT D0 F1RE EXCMFVD3 CMFVD1 CMFVD1 MOUNTED FS/MOUNT PARMS D1 F2RE EXCMFVD4 CMFVD2 CMFVD2 HFS GLOBAL D2 HGRE EXCMFVFD CMFVD3 CMFVD3 HFS FILESYSTEMS D3 HFRE EXCMFW18 CMFVD4 CMFVD4 HFS BUFFERS D4 HBRE IHDRCMFV CMFVFD CMFVFD SCM FD FDRE IMACCMFV CMFWC0 CMFVC0 PROCESS 18-1 DLRE VMACCMFV VMXGINIT -The three files contain these RTIN values: Oct 30, 2018 SHRT only contains 70x 71x 72x 73x 74x LONG only contains 0Cx 10x 18x 21x NORM contains all except 0Cx 10 11 12 13 14 15 and contains C0 C1 C2 C4 CC CD CE CF D0 D1 D2 D3 D4. -RTIN 18 appears both in LONG (1) and NORM (0), so the CMFV18 and CMFW18 DDDDDDs create CMFV18 and CMFV181. -These RTINs were supported, no longer documented: 25 26 27 28 29 33 41 42 43 45 53 96 97 -These RTINs are not yet supported, await DSECTs: 11 12 13 15 1E 2A 2B 2C 2D -Truncated RTIN '47'x with ENTL=1204 vs 1536 protected. Thanks to Michael Oujesky, DTCC, USA. Change 36.172 READDB2(IFCIDS=0-999) failed when it got past IFCID 367, READDB2 the current high IFCID. That syntax requires contiguous Sep 13, 2018 values, so if you specify a value GT 367 the upper limit is reset to 367 and a note is printed on the log. If you really want to create ALL of the IFCIDS use IFCIDS=ALL. Thanks to Scott Barry, SBBWorks Inc., USA. Change 36.171 Support for z/14 Clusters added to IBM Processor Topology ANAL9914 Report. Sep 13, 2018 Thanks to Raymond J. Smith, OPTUM, USA. ====== CHANGES THRU 36.170 ARE IN MXG 36.08 DATED SEP 10, 2018========== Change 36.170 For sites with 8-byte values for SMF70STN or SYSNAME or SAGANAL with 4-byte values that don't match SYSTEM, or MXGWARNs Sep 9, 2018 about TYPE70 or TYPE70PR data missing, you will need to Nov 11, 2018 use the output of this PROC FREQ report PROC FREQ DATA=PDB.TYPE70PR (WHERE=(SMF70STN=SYSNAME)); TABLES SYSNAME*SMF70STN/NOROW NOCOL NOCUM NOPCT; to update the new SELSTN macro variable to set the SYSTEM from the corresponding SMF70STN value: %LET SELSTN= %QUOTE(
IF STN(_I_) EQ 'DHECPROD' THEN STN(_I_)='DHEC'; ELSE IF STN(_I_) EQ 'DHECTEST' THEN STN(_I_)='DHCT'; ELSE IF STN(_I_) EQ 'PROD' THEN STN(_I_)='SYS1'; ELSE IF STN(_I_) EQ 'TEST' THEN STN(_I_)='SYST'; ELSE PUTLOG _N_= _I_= STN(_I_)= SYSTEM=; ); Thanks to Henry Jenkins, South Carolina State Government, USA. Change 36.169 Change 36.077 checked for the word BY in the first 2 VMXGSUM bytes of INCODE but there is no reason the BY would have Sep 8, 2018 to be in the first two bytes, so logic was revised to find any " BY " text in the INCODE. If the first text in the INCODE= was a %INCLUDE, it failed because the percent sign needed to be protected with %SUPERQ(). Change 36.168 Dataset BVIR20 variables MAX/AVE AHCT/BHCT were incorrect VMACBVIR as the +46 after DEVINTDL is their input location and Sep 8, 2018 removed. Thanks to Scott Barry, SBBWorks Inc., USA. Change 36.167 Support for BMC Energizer for IMS Connect which populates VMACCIMS TRNOTxxx variables in CIMSTRAN dataset, but TRNOTCON was Sep 7, 2018 not converted to local, and new CONNECT*SERVICE*DURATION in new CONNECTM variable. Thanks to Randy Hewitt, DXC, USA.
NO IMPACT TO PDB.TYPE70PR,ASUMCELP/ASUMCEC/ASUM70PR/ASUM70LP. Change 36.166 Dataset PDB.TYPE70 skips LCPUADDR/CPUID 64 and higher and VMAC7072 does NOT include any of those engine's CPU time, UP time, Sep 9, 2018 nor NRCPUS count, causing CPUACTTM for CPs to be less than the CPUTM in TYPE72GO Service Classes, which causes log messages NEGATIVE UNCAPTURED CPU TIME in RMFINTRV. -This error can occur with as few as 33 total engines; as in this case, with 13 CPs and 19 zIIPs, IBM skipped every other LCPUADDR so the last ZIP was '3F'x, and when a 14th CP was added, it became '40'X and exposed the MXG error. -ONLY PDB.TYPE70/PDB.RMFINTRV are impacted; PDB.TYPE70PR and PDB.ASUMCELP/ASUMCEC/ASUM70PR/ASUM70LP datasets that are created from TYPE70PR capture all engines' data. -This MXG error was introduced in 2013 in 31.04 support for 255 engines; previously separate variables for every engine, 0 thru 63 were created and kept; but new dataset TYPE70EN was created with all engines details so new vars were not needed to be kept, but they were still created for the summary into TYPE70, but the old logic to update the IFATYPE array still stopped at engine 63. You can use this program to read your PDB.TYPE70PR data to see if you are exposed, and the CPU TIME lost, if any:
SET PDB.TYPE70PR; IF LCPUPDTM GT 0 AND SMF70CIN IN ('CP' 'IIP'); KEEP SMF70CIN SYSTEM LCPUPDTM RANGE; IF LCPUADDR LT 64 THEN RANGE='INCLUDED-LT 64 '; IF LCPUADDR GE 64 THEN RANGE='NOT INCLUDED-GT 64'; PROC FREQ; TABLES SMF70CIN*RANGE*SYSTEM/NOCOL NOCUM NOROW; WEIGHT LCPUPDTM; TITLE LOST/INCLUDED PDB.TYPE70 CPU TIMES HIGH LCPUADDR; to see how much CPU was included or lost in PDB.TYPE70. -Normally, CPs LCPUADDR start at zero, followed by zips, so the impact is more likely for zip metrics, but when CPs are added dynamically, they get the next LCPUADDR. Only PDB.TYPE70 and PDB.RMFINTRV datasets are impacted. and only resources summed from individual engines; the 4HR Average MSU SMF70LAC and similar "interval variables" are not impacted by this error. Neither the PDB.TYPE70PR nor the four ASUM70PR datasets PDB.ASUMCELP,ASUMCEC,ASUM70PR,ASUM70LP are impacted. Thanks to Jim Horne, Lowes, USA.
ANAL89 into MSU values, with several reports. Sep 10, 2018 Thanks to Edward Cornish, Verisk, USA. Change 36.164 Variable SMF82KVL is added to TYPE8207 with number of VMAC82 nibbles in SMF82KV field. ICN 1652. Aug 30, 2018
VMACIMS have an ARRVTIME so their INPQUETM can't be known, but Sep 7, 2018 MXG incorrectly calculated wrong values. Now INPQUETM is missing when ARRVTIME is unknown. Change 36.162 Variable SYSTEM does not exist in IMS Log Records but MXG IHDRIMS can set it from SYSPARM() on the // EXEC JCL statement, VMACIMS but that applies to the entire IMS log that was read. VMXGINIT Now, to process multiple IMS system's logs in one job, Aug 28, 2018 JFCB=IMSJFCB is added so the DSNAME in the first 44 bytes can be used in tailoring member IHDRIMS or instream use %LET MACIMSH= in your SYSIN to set the variable SYSTEM. For example, if the second node in your DSNAME is SYSTEM, %LET MACIMSH= %QUOTE( SYSTEM=SCAN(IMSJFCB,2,'.'); ); will populate variable SYSTEM with that value. -Variable PROGTYPE='C' is now set for PROGTYHX='10'X. Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY. Change 36.161 If OUT70GL=WORK.xxxxxxxx, ASUM70PR program failed with VMXG70PR DATASET PDB.ASUM70GL NOT FOUND because the _LSU70GL Aug 28, 2018 token instead of macro variable &OUT70GL was used. Thanks to Jutta Gleixner-Schmid, Allianz, GERMANY. Change 36.160 MXG 36.07 only. Debugging PUTLOG statements that filled VMACCIMS the log were disabled. Aug 27, 2018 Thanks to Andreas Menne, Finanz Informatik, GERMANY. Change 36.159 DB2STAT2 field QDBPFRAM, Frame Size, in SMF is $EBCDIC2 VMACDB2 with text values of 4K, 1M, 2G, but MXG input QDBPFRAM Aug 27, 2018 as PIB2 numeric causing wrong values (62151 for 2G). New QDBPFRAMCH character variable has the 4K/1M/2G text, and QDBPFRAM remains numeric now with the correct bytes (for calculations), printing 4K, 1024K, 2048M with the MGBYTES format. Thanks to Lori A. Masulis, FMR, USA Change 36.158 Support for APARs OA55574/OA55609/OA55610 adds new VMACDCOL variables in dataset TYPEDSET: Aug 25, 2018 DCDCMPTV='COMPRESSION*TYPE*VALID'? DCDCTYPE='COMPRESSION*TYPE' although MXG variable DCDCMTYP already contains the compression type, decoded from DCDEXFLG. ICN 1650. Change 36.157 -Variable FCVSWTTM in CICSTRAN was incorrect, containing VMAC110 the same value in FCXCWTTM. Aug 26, 2018 -Variable SMFPSSPN, the Specific APPLID is now kept in the CICSTRAN dataset. Thanks to Giuseppe Giacomodonato, EPVTECH, ITALY.
VMXGODSO their programming, ODS is evolving so quickly and there VMXGODSC are so many permutations and combinations that they are TECHNOTE no longer a practical answer for most applications. Aug 23, 2018 Some MXG GRAFxxxx and ANAL members have ODS parameters, but you may find it preferable to wrap many reports in a single ODS package. For example, to run GRAFWRKX+GRAFCEC and send the results to a single ODS PDF file, use: ODS LISTING CLOSE; /* always needed on zOS */ OPTIONS ORIENTATION=LANDSCAPE; ODS GRAPHICS/ WIDTH=10IN HEIGHT=7.5IN; ODS PDF FILE='D:/MYPDF.PDF' STYLE=MXGSTYLE1; %GRAFWRKX; %GRAFCEC; RUN; ODS PDF CLOSE; RUN; -MXGSTYLE1 was used here because the default style used by ODS results in bars of solid colors so close together it can be difficult to tell one bit of the bar from another. MXGSYLE1 uses brighter colors and patterns to make it simpler to tell who is on first. MXGSTYLE1 is created and stored in the FORMATS library by the FORMATS member. STYLE is just one of many ODS options you may wish to use which is what makes VMXGODSO/VMXGODSC obsolete. -Pasted directly from the SAS site to create CSV file: ods html close; options obs=15; Yüklə 28,67 Mb. Dostları ilə paylaş:
|