* copyright (C) 1984-2019 merrill consultants dallas texas usa
Yüklə 28,67 Mb.
|
| Workload Name that begins with 'PROD' as a pattern.
ASIWORKLOAD=TEST+++ selects only address spaces with a WLM Workload Name that begins with 'TEST' followed by 3 digits as a pattern. ASIWORKLOAD=? selects only address spaces with a blank WLM Workload Name as a pattern. ASIWORKLOAD=%* selects only address spaces with a non-blank WLM Workload Name as a pattern. -ASIRESGROUP= selects ASI entries by 8 character WLM Resource Group Name. Both ranges and patterns with wild card characters may be specified. Up to 32 ranges and 32 patterns are supported. The default is ASIRESGROUP=ALL. -Examples for ASIRESGROUP= ASIRG=CAP10:CAP20 selects all WLM Resource Groups GE 'CAP10' and LE 'CAP20' as a range. Note use of keyword alias ASIRG. ASIRESGROUP=CAP__ selects only address spaces with a WLM Resource Group Name that begins with 'CAP' followed by 2 alphabetic characters as a pattern. ASIRESGROUP=CAP%%% selects only address spaces with a WLM Resource Group Name that begins with 'CAP' followed by 3 characters as a pattern ASIRESGROUP=? selects only address spaces with a blank WLM Resource Group Name as a pattern. ASIRESGROUP=%* selects only address spaces with a non-blank WLM Resource Group Name as a pattern. -ASISRVCLASS= selects ASI entries by 8 character WLM Service Class Name. Both ranges and patterns with wild cards may be specified. Up to 64 ranges and 64 patterns are supported. The default is ASISRVCLASS=ALL. -Examples for ASISRVCLASS= ASISC=BATHIGH:BATLOW selects all WLM Service Classes GE 'BATHIGH' and LE 'BATLOW' as a range. Note the use of keyword alias ASISC. ASISRVCLASS=*HIGH selects only address spaces with a WLM Service Class Name that ends with 'HIGH' as a pattern. ASISRVCLASS=*+* selects only address spaces with a WLM Service Class Name that contain only one numeric character as a pattern. ASISRVCLASS=? selects only address spaces with a blank WLM Service Class Name as a pattern. ASISRVCLASS=%* selects only address spaces with a non-blank WLM Service Class Name as a pattern. -ASIRPTCLASS= selects ASI entries by 8 character WLM Report Class Name. Both ranges and patterns with wild cards may be specified. Up to 64 ranges and 64 patterns are supported. The default is ASIRPTCLASS=ALL. -Examples for ASIRPTCLASS= ASIRC=DB2:TSO selects all WLM Report Classes GE 'DB2' and LE 'TSO' as a range. Note the use of keyword alias ASIRC. ASIRPTCLASS=LOW.%%% selects only address spaces with a WLM Report Class Name that begins with with 'LOW', followed by a national character, and then followed by 3 more characters as a pattern. ASIRPTCLASS=MED++* selects only address spaces with a WLM Report Class Name that begins with 'MED', followed by 2 digits, and then possibly other characters as a pattern. ASIRPTCLASS=? selects only address spaces with a blank WLM Report Class Name as a pattern. ASIRPTCLASS=%* selects only address spaces with a non-blank WLM Report Class Name as a pattern. -ASIJOBCLASS= selects ASI entries by JES Job Class. Both ranges and patterns with wild cards may be specified. Up to 32 ranges and 32 patterns are supported. The default is ASIJOBCLASS=ALL. -Examples for ASIJOBCLASS= ASIJC=A:D selects only address spaces with a JES Job Class of A, B, C, or D as a range. Note use of the keyword alias ASIJC. ASIJOBCLASS=+ selects only address spaces with a numeric JES Job Class of 0-9 as a pattern. ASIJOBCLASS=? selects only address spaces with a blank JES Job Class as a pattern. ASIJOBCLASS=%* selects only address spaces with a non-blank JES Job Class as a pattern. -ASIJOBNAME= selects ASI entries by 8 character z/OS Job Name. Job Name characters are validated to those allowed by JCL syntax. Both ranges and patterns with wild cards may be specified. Up to 64 ranges and 64 patterns are supported. The default is ASIJOBNAME=ALL. -Examples for ASIJOBNAME= ASIJN=PROD1234:PROD5678 selects only address spaces with a z/OS Job Name GE 'PROD1234' and LE 'PROD5678' as a range. Note use of the keyword alias ASIJN. ASIJOBNAME=.* selects only address spaces with a Job Name that begins with a national character as a pattern. ASIJOBNAME=*++ selects only address spaces with a Job Name that ends with 2 numeric digits as a pattern. -ASIJESID= selects ASI entries by 8 character JES Job Identification. Both ranges and patterns with wild cards may be specified. Since a JES Id is one character followed by 7 digits or three characters followed by 5 digits not all pattern characters may be used with this keyword. For convenience any leading zeros in the numeric portion of the JES Id may be omitted and will be filled in automatically. Up to 64 ranges and 64 patterns are supported. The default is ASIJESID=ALL. -Examples for ASIJESID= ASIJID=J0000100:J0001123 selects all address spaces with batch JES Id numbers GE 100 and LE 1123 as a range. Note use of keyword alias ASIJID. ASIJID=J100:J1123 selects the same address spaces as above with the leading zeros omitted for coding convenience. ASIJESID=JOB12345:JOB32001 selects all address spaces with batch JES Id numbers GE 12345 and LE 32001 for installations with 5 digit JES Id numbers as a range. ASIJESID=J1* selects all batch address spaces with a JES ID that begins with '1' as a pattern. -ASIAND (default) indicates that selection results from two or more different ASI filter keywords are logically ANDed.
-ASIOR indicates that selection results from two or more different ASI filter keywords are logically ORed. -Examples of ASIAND/ASIOR: With ASIAND in effect ASISUBSYS=BATCH ASIJOBNAME=XYZ* selects ONLY batch jobs whose those job names begin with 'XYZ'. ASIAND (default) provides more restrictive ASI entry selection. With ASIOR in effect ASISUBSYS=BATCH ASIJOBNAME=XYZ* selects ALL batch jobs OR any job names beginning with 'XYZ' even if they ran under another subsystem. ASIOR provides less restrictive ASI entry selection. -Selection results from repeats of the SAME ASI filter keyword are always logically ORed. -New parameter SYSAND (default) indicates that selection results from the SYSPLEX= and SYSTEM= filter keywords for the Data Set Header (DSH) table when both are specified are logically ANDed. -New parameter SYSOR indicates that selection results from the SYSPLEX= and SYSTEM= filter keywords for the Data Set Header (DSH) table when both are specified are logically ORed. SYSOR must be coded when needed. -Examples of SYSAND/SYSOR: With SYSAND in effect SYSPLEX=PROD SYSTEM=SYSP selects ONLY RMF III data sets originating from the PROD sysplex AND the SYSP LPAR. SYSAND (default) provides more restrictive RMF III data set selection. With SYSOR in effect SYSPLEX=PROD SYSTEM=SYSP selects ALL RMF III data sets originating from the PROD sysplex OR any data sets for the SYSP LPAR even if SYSP is part of a different Sysplex. SYSOR provides less restrictive RMF III data set selection. -Selection results for multiple SYSPLEX= values are always logically ORed. -Selection results for multiple SYSTEM= values are always logically ORed. -The '_' pattern character now matches lower case in addition to upper case alphabetic characters in a source string.
-The '_' pattern character will now match an underscore in a source string. While this character is not technically alphabetic, the underscore is sometimes used in some WLM names for better legibility. -A new pattern character '?' will allow selection of completely blank source strings when used only by itself. When '?' is used with other characters in a pattern a single imbedded blank in a source string is matched. -Example of ? pattern character: ASIRPTCLASS=? selects all ASI entries that do not have a WLM Report Class assigned or that could not be found by ASMRMFV. That field in the ASI entry must be completely blank to select that entry. -A new pattern character '!' will match special characters in a source string. For this purpose special characters are those bytes in the EBCDIC code table that are NOT alphabetic (a-z, A-Z), numeric (0-9), national (@,#,$), or blank (X'40') and have been assigned to a character. -Example of ! pattern character: X'5C' is assigned the EBCDIC asterisk '*' and would match the ! pattern character. However, X'00' does not match this pattern character because no EBCDIC character is assigned to this byte. ASIJOBNAME=!MASTER! selects the *MASTER* address space. Coding ASIJOBNAME=*MASTER* in this case instead may produce different results because the '*' is a pattern character itself representing zero to many characters. So any job name with 'MASTER' imbedded would be selected. -Section 5 "Input Data Selection Parameters" is updated with discussion of all the new ASI selection keywords and aliases. -A new Section 25 "Ranges and Patterns" has been added to the documentation to explain use of these features in detail.
-A new Section 26 "Summary" is added to replace the old Section 25 and includes a summary of the new ASI keywords and all pattern characters. -New parameter SHOWALL (alias SA) indicates that the settings for all possible filter keywords that take range and/or pattern values are to be displayed in the ASMRMFV log in message RMFV006I even when no filters have actually been specified for a particular keyword. These display as keyword=ALL. -New parameter NOSHOWALL (alias NOSA) indicates that only filter keywords that have actual range and/or pattern values specified are to be displayed in the ASMRMFV log in message RMFV006I. This option helps reduce the size of the ASMRMFV log. NOSHOWALL is the default. -Section 6 "Report Control Parameters" is updated to add SHOWALL/NOSHOWALL parameters. -Several messages are slightly changed either to accommodate longer ASMRMFV keywords for the ASI filter selection or to display their settings.
VMXGRMFI kept. While the existing VMXGRMFI program provides many Jul 30, 2015 arguments (R70ID, R70MAX, R70SUM, etc) that can be used in your tailored %VMXGRMFI call, those arguments require you to list ALL of the variables to be kept. This change adds the ADD70ID=, ADD70MAX=, etc., arguments that only list the variables to be added. Thanks to Joachim Sarkoschitz, DATEV, GERMANY. Change 33.180 Support for MQ Version 8 subtype 215 record which creates VMAC115 DDDDDD DATASET DESCRIPTION VMXGINIT TY115X TY115215 TYPE 115 ST 215 BUFFER STATS Jul 30, 2015 -New variables QPSTFLAG0 and QPSTFLAG1 added to TY115215 and MQMBUFER datasets.
VMAC7072 MXG variable SMF70MTTT (misnamed, IBM field is SMF70MTIT) Jul 29, 2015 is now deaccumulated in PDB.TYPE70EN. Aug 4, 2015 -For SMT Mode, for complete detail per-engine data, use the PDB.TYPE70EN dataset instead of PDB.TYPE70. -This change also populated SMF70WTI/WTS/WTU in TYPE70PR with zeros or real values that were previously missing. -Aug 4. Corrected SORT error due to delete with TYPE7072. Change 33.178 Many of the ANAL* members in JCLPDB9 were old (some had JCLPDB9 not been touched in decades) or archaic and in some cases Jul 29, 2015 had been replaced by more robust and up to date members. These are ONLY included as examples; it is NOT likely that you would execute ALL of these example ANALxxxx reports in your production BUILDPDB. ANALCONT - replaced by VMXGPRAL ANALMPL - replaced by ANALINIT ANALTURN - replaced by ANALINIT ANALAVAL - removed since successful execution requires user tailoring ANALESV - obsolete GRAFWRKX - added GRAFCEC - added All report members now have comments describing them Commented ODS statement added to route output to PDF Change 33.177 -A new parameter PRINT was added. A value of ALL/DETAIL ANALRANK generates a report for each of the variable named in the ANALPROG VARS parameter, and a summary report with the rankings Jul 28, 2015 of ALL variables is produced. A value of DETAIL generates only the individual named variable report. A value of SUMMARY only generates the summary report. SUMMARY is assumed if PRINT is left blank. -A third example generates a report similar to ANALPROG.
IHDRBBMQ and associated macro variable &MACBBMH permits selection VMACBBMQ of data to be output after the BBMQ Header has been read. VMXGINIT
Jul 27, 2015 Change 33.174 The number of IFL processors in an LPAR was incorrectly VMXG70PR set to the number of IFLS on the CEC and IFL busy was Jul 21, 2015 also incorrect since it was based on the CEC not on the LPAR.
ASUM113 z13 SMF 113 records is not correct, but SM1132SP=5000 is VMAC113 the correct value, not 5. This impacted only EFFGHZ and Jul 22, 2015 LPARBUSY values. Thanks to David Cogar, Wells Fargo, USA. ====== Changes thru 33.172 were in MXG 33.07 dated Jul 22, 2015========= Change 33.172 -If you specified USERADDS=NOUSERID and IDs over 128 were ANALID found, an EOF test that built the macro variable that was Jul 22, 2015 used in UTILBLDP was never executed. -A superfluous RETURN; caused an error if you specified SMFAUDIT=NO.
VMAC120 potentially MANY of these log messages to be printed" Jul 20, 2015 ***SMF 120 SUBTYPE 9 UNEXPECTED MULTIPLE SEGMENT. _N_=2 SYSTEM=XX SMFTIME=19JUL2015:00:04:54.20 SM1209AK=1 Thanks to Jim Horne, Lowe's, USA.
VMACCTCP
Jul 16, 2015 Change 33.169 The z13 protection for zero divide for TLB1CYCL,PTEPCTMI, ASUM113 TLB1MSRT still used the zEC12 EXTND133+EXTND140 values Jul 16, 2015 but the z13 changed the divisor to EXTND129+EXTND134, which should have been also been used for the zero test. Luckily, the incorrect test was non-zero so the correct values were calculated. Thanks to David Cogar, Wells Fargo, USA.
VMAC30 enabled, or all _INST counters will be missing values. Jul 15, 2015 These two new variables are now created to identify why. SMF30_INSTCAPTDISRUPTION='NO*INSTRUCTION*COUNTERS' SMF30_INCOMPLETE_DATA='INSTRUCTION*COUNTERS*INCOMPLETE' From Bob Rodgers SHARE 2014 SYSPROG Goody Bag notes: - To get instruction counts in Counter Data Section, HIS must activate the CPU Measurement Facility to collect at least the basic counter set. - MODIFY HIS,BEGIN,CTRONLY,CTRSET=(B) is minimal - MODIFY HIS,BEGIN,CTRONLY,CTRSET=(B,E) is recommended - SMFPRMxx must contain the keyword SMF30COUNT Thanks to Alfred Holz, Express-Scripts, USA.
ANALDB2R only be defined if you are on SAS 9.4 or higher. A %LET Jul 13, 2015 was added to instantiate the variable to protect ancient versions. Change 33.166 Support for Correlog z/OS Agent SMF User record created EXTYCZA new dataset. IMACCZA dddddd dataset Description TYPECZA TYCZA TYPECZA Correlog z/OS AGENT TYPSCZA VMACCZA
VMXZGINIT Jul 29, 2015 Change 33.165 Subtype 24 XPTR records decoded VMACXPTR
Jul 9, 2015 Change 33.164 -If you specified READDB2 with IFCIDS=ALL and PDBOUT=WORK READDB2 some IFCIds (22 and 217) that create multiple datasets VMAC102 failed in their sort of those additional datasets looking Jul 8, 2015 for a PDB LIBNAME. In addition if you specifically requested (for example) IFCIDS=I22 it would fail looking for _C102I22 since the code to create that dataset is in _C102022. READDB2 now converts I22 to 22 U17 v17 T17 to 217.
-The _S102 "sort all 102s" macro now skips 202/225/230/239 and 369 because they are NOT 102s and instead are created in 100.2, 100.4, 100.3, 101.1, and 100.5 ID/Subtypes.
VMAC110 time of day, and PHSTARCN was input as a counter, but now UTILEXCL PHSTARTM is INPUT TODSTAMP8, formatted DATETIME21.2, and Jul 7, 2015 converted to local zone; PHSTARCN should never have been created so it no longer is. Thanks to David Shaw, M&T Bank, USA. Thanks to Doug Donoho, M&T Bank, USA.
VMXGINIT Macros %MXGLOGDO, %MXLOGPUT and MXLOGEND are defined in VMACSMF VMXGINIT. If an //MXGLOG DD or FILENAME MXGLOG is used, Jul 10, 2015 MXG will automatically enable and send MXG messages to Jul 12, 2015 the MXGLOG file on z/OS; on ASCII you send those messages Jul 14, 2015 to FILENAME MXGLOG 'c:\mxg\mxglog.txt'; but note that the Nov 23, 2015 file is written with MOD, so you may need to clear the file with DATA _NULL_; FILE MXGLOG; Status: These members' messages are updated: VMAC0 VMAC0203 VMAC10 VMAC113 VMAC115 VMAC116 VMAC120 VMAC21 VMAC22 VMAC23 VMAC26J2 VMAC30 VMAC42 VMAC6 VMAC6156 VMAC7 VMAC7072 VMAC71 VMAC73 VMAC74 VMAC75 VMAC76 VMAC77 VMAC78 VMAC89 VMAC8911 VMACDB2 VMACID VMACTMNT VMACSMF VMXG70PR These include all members in the default BUILDPDB. The last change-date wasn't updated in these members, as the changes did not impact the output datasets. The syntax of the messages written to MXG log will be MXGLOG::MXGtype.member.nnn where type is INFO, WARNING or ERROR, member is the member name that creates the message nnn is a sequence number in that member name. Thanks to MP Welch, Bank of America, USA. Change 33.161 Support for MOBILEWRK to read BMC's IMF/CIMSTRAN FA IMS MOBWRKI3 log records to create CIMSTRAN and use in MOBWRKI3, or MOBWRKI4 to use existing CIMSTRAN dataset(s) in MOBWRKI4. MOBILWRK Only comments updated in MOBILWRK. Jul 6, 2015 Thanks to Jan Tielemans, KBC, BELGIUM. Change 33.160 Reserved Change Number, now Unused. Change 33.159 Support for ANALID and VMXGSRCH to decompress DB2 or CICS ANALID records, on z/OS when EXITCICS/CICSIFUE exit is not used, DB2DECOM or on ASCII, where EXITCICS cannot be installed. MXGDECOM -For ANALID, the DB2 Product section, containing IFCID and SMFSRCH SUBTYPE and DB2 Version, is compressed, so those values UTILBLDP are missing. Optional new SMFDECOMP=DB2 argument invokes VMAC110 the MXG internal code to decompress 101 and 102 records VMACDB2 so those values can be reported. (Not needed for CICS as VMACSMF its version/subtype is the uncompressed area.) VMXGINIT -For SMFSRCH, compressed CICS 110 and DB2 101/102 records Jul 17, 2015 couldn't be searched. New SMFDECOMP=BOTH or DB2 or CICS argument will invoke the MXG decompression code so those records can be searched for the LOOKFOR text. -WARNING: The internal Code decompression requires A LOT more CPU time than the EXITCICS exit. A 5GB DB2 SMF file required 34 CPU minutes with the internal algorithm, but only 13.5 CPU minutes using EXITCICS. That is why YOU must choose to enable the SMFDECOMP decompression. -You can also force decompression of CICS and/or DB2 data when only the _SMF (decode SMF header macro) is used: %LET MXGDECOMP= BOTH or DB2 or CICS ; %INCLUDE SOURCLIB(VMACSMF); DATA; _SMF; The decompressed record will be in variable _INFILE_. -UTILBLDP is invoked by SMFSRCH to create all datasets in the selected SMF records; testing exposed an incorrectly built macro for type 102 when BUILDPDB=NO and the IFCID was only 2 characters long. -The decompression %MACROs MXGDECOM and DB2DECOM are now defined in those members and the redundant definitions in VMACSMF, VMAC110 and VMACDB2 are removed, since the AUTOCALL facility will resolve them when referenced. Change 33.158 Type 6 ESS zero length segment caused INPUT STATEMENT IMAC6ESS EXCEEDED STOPOVER error condition when the segment was Jul 3, 2015 the last ESS segment. GEPARMKY=0016x and 0027x have been observed with zero segment length, which would seem to be an IBM error (to be investigated with IBM Support) but protection is added to prevent the STOPOVER error. In testing this change with on-hand SMF 6 records from other users four new ESS segments are now decoded: ESSCKPTPAGE ESSOVERLAYB ESSOVERLAYF ESSDUPLEX Thanks to Andreas Menne, Finanz Informatik, GERMANY. Change 33.157 zVM XAM ERROR SYTCUP SEGMENT LENGTH occurs if the online VMACXAM engine count is changed, because XAM does NOT change the Jul 1, 2015 value in SYTNLPS, which always contains the number of INSTALLED engines (and the same is true of variable NCPUS from the SUBSUM segment). This change recalculates the number of engines into SYTNLPS based on SEGLEN, which XAM does update, and which is then used to input the actual online CP segments. Thanks to Patricia Hansen, ADP, USA. Thanks to Mike Chaves, ADP, USA. Change 33.156 Support for APAR OA44525, zHPF Extended Distance II. VMAC78 -New variables added to TYPE78CF dataset: VMAC79 R783CTMW='TRANSPORT*MODE*WRITE*COUNT' Jun 30, 2015 R783CTRD='1ST XFER*READY*DISABLED*WRITE COUNT' R783TMWM='XPORT*WRITE*COUNT*DCM CHANNELS' R783TRDM='1ST XFER*READ*DISABLED*DCM CHANNELS' -New variables added to TYPE79EF dataset: R79ECTRD='1ST XFER*READY*DISABLED*WRITE COUNT' R79ETMWM='XPORT*WRITE*COUNT*DCM CHANNELS' R79ETRDM='1ST XFER*READ*DISABLED*DCM CHANNELS' PCTPTHBY='PERCENT*CHPID PATH*BUSY'
VMAC74 that were incorrectly output in TYPE74MO dataset, which Yüklə 28,67 Mb. Dostları ilə paylaş:
|