***********************NEWSLETTER SIXTY-FOUR***************************
MXG NEWSLETTER NUMBER SIXTY-FOUR - JUNE 16, 2014
Technical Newsletter for Users of MXG : Merrill's Expanded Guide to CPE
TABLE OF CONTENTS
I. MXG Software Version.
II. MXG Technical Notes
III. MVS, aka z/OS, Technical Notes
IV. DB2 Technical Notes.
V. IMS Technical Notes.
VI. SAS Technical Notes.
VI.A. WPS Technical Notes.
VII. CICS Technical Notes.
VIII. Windows NT Technical Notes.
IX. z/VM Technical Notes.
X. Email notes.
XI. Incompatibilities and Installation of MXG.
See member CHANGES and member INSTALL.
XII. Online Documentation of MXG Software.
See member DOCUMENT.
XIII. Changes Log
Alphabetical list of important changes
Highlights of Changes - See Member CHANGES.
COPYRIGHT (C) 1984,2014 MERRILL CONSULTANTS DALLAS TEXAS USA
I. The Current Version MXG 32.05 is dated Jun 16, 2014.
The 2014 Annual Version MXG 31.31 was dated Jan 20, 2014.
You can always use this form
http://www.mxg.com/Software_Download_Request
to request the ftp download instructions for the current version.
ALWAYS USE THE MOST CURRENT VERSION OF MXG.
See CHANGES member of MXG Source, or http://www.mxg.com/changes.
II. MXG Technical Notes
1. Using LABEL statement to change the order of variables in a dataset.
In general, MXG attempts to create datasets with the variables in
alphabetic order, to make it easier to find a variable in the output
of PROC PRINT/PROC MEANS, etc. But you might want a few "key" vars
to always be first, and you can do that with this syntax:
DATA NEW;
LABEL MYFIRST= MYSECOND= MYTHIRD= ;
SET OLD;
The NEW dataset will have the three MY variables first followed by
the other variables in alphabetic order, and ALL variables will have
their original label. In fact, you cannot use that LABEL statement
to change a label. SAS uses the LAST label statements' value for
the variable's label. Here, the inserted LABEL statement only sets
the order because it is the first reference to those variable names.
(So, you could tailor the last EXdddddd member and add your
replacement label there, it will be after all LABEL statements.)
III. MVS, a/k/a z/OS, Technical Notes.
4. ANALYSIS OF CICS, DB2, IMS, MQ, WAS AND TYPE 70 FOR MOBILE WORK =*/
THIS IS THE FIRST ITERATION OF MXG SUPPORT FOR MOBILE WORK.
This is MXG Technical Newsletter SIXTY-FOUR MVS Technical Note 4.:
Both this MOBILWRK text AND that Technical Note will be updated as
more is learned.
Please contact me direct at barry@mxg.com for your feedback.
a. The preliminary IBM documentation of their Mobile Workload Pricing
was dated May 4 and can be seen at this url:
USA:
http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/
rep_ca/3/897/ENUS214-223/index.html&lang=en&request_locale=en
EMEA:
http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/
rep_ca/0/877/ENUSZP14-0280/index.html&lang=en&request_locale=en
The full plan is not yet fully announced, but based on the preceding
document, and after conversations with the IBM Product Team, with
significant assistance from Al Sherkow, MXG provides these example
programs that will assist you in generating reports that you MAY be
able to use to track and identify and quantify your mobile work.
THIS IS NOT AN END-TO-END SOLUTION, AS YOU MUST FIRST PRESENT YOUR
PLANNED METHODOLOGY FOR MOBILE WORK IDENTIFICATION AS WELL AS THE CPU
METRICS TO BE USED, FOR IBM TO THEN EVALUATE AND (HOPEFULLY) ACCEPT.
Once approved, MOBWRKxx programs should then be able to provide those
approved data in the CSV file in the required format to send to IBM
each month for your discount. Both this text and these programs will
likely be revised, after feedback from early adopters and from IBM.
-Five products, CICS, DB2, IMS, MQ, and WAS at correct versions are
eligible.
-Your first task will be to determine how to identify mobile
transactions; section A below provides the list of variables that can
be used for each of those products.
-Then, you will execute the new MOBWRKnn programs to process your SMF
data or your existing "PDB's" to create the "MOBILEprod"
(MOBILECICS/MOBILEIMS/MOBILEDB2/MOBILEMQ/MOBILWAS) datasets with the
hourly GP CPU Time for each product and version.
-These MOBILEprod data are then read by the MOBWRK05 program (written
by Al Sherkow) that creates the hourly GP CPU time and maps the raw
versions to the product name. E.g. CICS 4.1 and 4.2 are a single
product, and CICS 5.1 and 5.2 are a single product for summarization.
-Finally, when IBM has made the formal announcement of their plans,
the MOBWRK06 program(also written by Al) will read the output of
these programs, to create the CSV file that you will upload monthly
to (hopefully) qualify for what could be a VERY significant discount.
I recommend you start by using the C.1 example, below, to read an SMF
file (a day, or a few hours) to test your mobile definition logic and
to ensure that all of the needed variables exist, and to then examine
your MOBILE datasets to see how much mobile work was reported.
Then, contact support@mxg.com to discuss how you will actually run
these programs (daily? monthly? read SMF? read existing PDBs? etc.)
since by that time, the alternative MOBWRKxx programs for those other
ways to create the monthly CSV file will exist.
I am VERY interested in the logic you choose to identify Mobile Work.
Please share, as I hope to enhance this documentation with examples
for others. I will not identify your company.
This document will be enhanced as more is announced and known, but
it presently contains these sections:
i. Identification of variables that can be used to identify
the mobile work transactions.
ii. Example MOBWRK00-MOBWRK06 processing times for eight hour's SMF
data from a VERY large site.
iii. Examples of MOBWRK00-MOBWRK06 executions to read SMF data with a
brief description of each of the current MOBWRK0n programs.
iv. Additional MOBWRKCn programs are created to replace MOBWRK02/03:
=======================================================================
i. Identification of variables
/* Mobile Workload Identification and CPU metrics */
1. You need to start by identifying which of the available variables
you will use, and the logic specific to your site, to identify your
mobile transactions. You would then update the MOBWRK01 program to
use those variables to define your mobile work and store the GP CPU
time into XXXXCPUMOB for the mobile transactions or into XXXCPUNOT
for the non-mobile transactions. This is the default example code
in MOBWRK01:
%LET MOBILECICS=%QUOTE(
IF TRANNAME=:'M' THEN CICSCPUMOB=CPUTM;
ELSE CICSCPUNOT=CPUTM;
);
%LET MOBILEDB2=%QUOTE(
IF QWHCAID=:'S03' THEN DB2CPUMOB=DB2TCBTM;
ELSE DB2CPUNOT=DB2TCBTM;
);
%LET MOBILEIMS=%QUOTE(
IF TRANSACT=:'M' THEN IMSCPUMOB=IMSCPUTM;
ELSE IMSCPUNOT=IMSCPUTM;
);
%LET MOBILEMQ =%QUOTE(
IF QWHCTRN=:'L' THEN MQCPUMOB=QMACCPUT;
ELSE MQCPUNOT=QMACCPUT;
);
%LET MOBILEWAS=%QUOTE(
IF SM1209CR=:'T1SR01SA' THEN WASCPUMOB=SM1209DH;
ELSE WASCPUNOT=SM1209DH;
);
RUN;
2. For each of the five eligible products, these are the possible
fields that can be used in MOBWRK01 to identify your mobile work,
and the fields that contain the GP CPU time and the product and
version and Hour.
CICS DESCRIPTIONS:
CICS Mobile Identification Variables:
APPLID VTAM APPLICATION NAME
TRANNAME TRANSACTION NAME
LUNAME LOGICAL UNIT NAME
NETSNAME ORIGINATING SYSTEM NET-NAME
OCLIPADR ORIGINATING CLIENT IP ADDRESS
OTRAN ORIGINATING TASK TRANSACTION NAME
PROGRAM PROGRAM NAME
RPTCLASS REPORTING CLASS NAME
SRVCLASS SERVICE CLASS NAME
CICS Summarization variables:
SMFPSRVR CICS/TS VERSION VALUE
66.0 - CICS/TS 4.1 - 5655-S97
67.0 - CICS TS 4.2 - 5655-S97
68.0 - CICS TS 5.1 - 5655-Y04
69.0 - CICS TS 5.2 - 5655-Y04
STARTIME DATE AND HOUR WHEN TRANSACTION STARTED
SYSTEM SMF SYSTEM ID
(SYSPLEX DOES NOT EXIST IN CICS SMF 110 RECORDS)
CICS CPU Metrics:
ORIGCPUTM CICS 110-1 ORIG CPUTM - see below
CPUCPONLY CICS 110-1 CPONLY CPU TIME - 5.1+ only
CICSCPUMOB CICS 110-1 MOBILE CPU TIME - Mobile Transactions
CICSCPUNOT CICS 110-1 NON-MOBILE CPU TIME - NonMobile Trans
CICSCPUTOT CICS 110-1 TOTAL CPU TIME - ALL Transactions
CICDSCPUTM CICS 110-2 INTERVAL DISPATCH (ALL TCBS) TIME
Description/derivation:
ORIGCPUTM = TASCPUTM + WMQASRTM + CPURLSTM (MXG NAMES)
USRCPUT + WMQASRTM + RLSCPUT (IBM NAMES)
CPUCPONLY = CPUTONTM (MXG NAME)
CPUTONCP (IBM NAME)
For CICS/TS 4.1 and 4.2, TASCPUTM/USRCPUT includes both GP CPU
time and any CPU Time on Specialty Engines (zIIP,zAAP), so the
ORIGCPUTM can be GREATER than the actual GP CPU time.
The CICDSCPUTM contains the interval GP CPU time, from 110-2
Dispatcher stats (summed for all TCBs), so it can be compared
with the ORIGCPUTM to estimate the portion that is GP-only
for these old versions.
For CICS/TS 5.1 and later, CPUCPONLY contains ONLY the GP
portion of TASCPUTM, so it is used in place of TASCPUTM in the
transaction metrics of Mobile/Non-Mobile/Total CPU time.
But for all versions, the CPU Time in the 110-1 transaction
records is only the CAPTURED CPU time. For every transaction,
there is a fixed CPU cost for the start and end of each
transaction that is NOT captured in the Transaction Record.
The uncaptured CICS time CAN be significant, especially when
there many "small" transactions, so the total CAPTURED CPU Time
for all transactions (CICSCPUTOT) should be compared with
CICDSCPUTM, and that fixed cost can be then estimated as
(CICDSCPUTM-CICSCPUTOT)/NRTRANS and potentially used to inflate
the Captured CPU times to the total CPU time.
NOTE: THIS TECHNICAL DISCUSSION/EXAMPLE OF CICS CAPTURED CPU
TIME MAY HAVE NO IMPACT ON THE METRIC THAT IBM CHOOSES.
FOR A LOT OF REASONS, THEY MIGHT WELL ONLY ACCEPT THE
RECORDED PRODUCT TRANSACTION TIME IN THE DETAIL DATA.
DB2 DESCRIPTIONS:
DB2 Mobile Identification Variables:
QWHSRELN DB2 VERSION RELEASE NUMBER
QWHSSSID DB2 SUBSYSTEM ID
QWHCPLAN DB2 PLAN NAME
QWHSLUNM LU NAME
QWHSNID NETWORK ID
JOB JOB NAME
QLACLOCN LOCATION NAME OF THE REMOTE DDF SITE
QMDAAUTH DB2 AUTHID
QWHCAID DB2
QWHCCN CONNECTION NAME
QWHCCV CORRELATION ID
QWHCEUID END USER'S USERID AT WORKSTATION
QWHCEUTX END USER'S TRANSACTION NAME
QWHCEUWN END USER'S WORKSTATION NAME
QWHCOPID ORIGINAL OPERATOR ID
QWHCATYP CONNECTING SYSTEM TYPE CODE
QWHSLOCN LOCAL LOCATION NAME
QWHSNID; NETWORK ID
DB2 Summarization variables:
QWHSRELN DB2 VERSION VALUE
9.1 5635-DB2
10.1 5605-DB2
11.1 ??
STARTIME DATE AND HOUR WHEN TRANSACTION ENDED - QWHSSTCK
SYSTEM SMF SYSTEM ID
(SYSPLEX DOES NOT EXIST IN DB2 SMF 101 RECORDS)
DB2 CPU METRIC:
DB2TCBTM SMF 101 Subtype
Description/derivation:
DB2TCBTM = (QWACEJST-QWACBJST) + QWACSPCP + QWACTRTE + QWACUCDP
IMS DESCRIPTIONS:
IMS Mobile Identification Variables:
IMSUSID USERID*IF*SPECIFIED
LTERM INPUT*LTERM*NAME
PROGRAM PROGRAM*NAME
PROGTYPE PROGRAM*TYPE
PSBNAME PSB*NAME
REGIONID JOB*NAME
STEPNAME STEP*NAME
TPCPGRPN GROUP*NAME*IF SPECIFIED
TPCPOSSN SUBSYS*NAME*OWNING*LOG RECORD*(CTL REG)
TPCPSIDD DESTINATION*SYSTEM ID
TPCPSIDS SOURCE*SYSTEM*ID
TPCPSSTY SUBSYSTEM*FUNCTION*TYPE
TPLUNAME LU NAME*OF MESSAGE*FROM APPC
TPNWID NETWORK*ID OF*MESSAGE*FROM APPC
TRANSACT TRANSACTION*CODE
IMS Summarization variables:
IMSVERSN IMS*VERSION
11.1 5635-A02
12.1 5635-A03
13.1 5635-A04
STRTTIME DATE AND HOUR WHEN TRANSACTION STARTED - STRTTIME
TPCPCPUI CPU*ID
IMS CPU METRIC:
IMSCPUTM IMSLOG*(MESSAGE)*CPU DURATION
WAS DESCRIPTIONS:
WAS Mobile Identification Variables:
SM1209BI NODE SHORT NAME
SM1209BJ CLUSTER SHORT NAME
SM1209BK SERVER SHORT NAME
SM1209BT JOB NAME FOR THE CONTROLLER
SM1209CR JOB NAME FOR THE DISPATCH SERVANT
SM1209CK TYPE OF REQUEST PROCESSED /
WAS Summarization variables:
SM1209BM WEBSPHERE VERSION NUMBER
8.1 5655-W65
STARTIME DATE AND HOUR WHEN TRANSACTION STARTED - SM1209CN
SYSTEM SMF SYSTEM ID
SM1209BS SYSPLEX
WAS CPU METRIC:
SM1209DH ENCLAVE CPU TIME REPORTED BY IWM4EDEL
MQ DESCRIPTIONS:
MQ Mobile Identification Variables:
MQMSSSID MQM SUBSYSTEM ID
QWHCAID AUTHORIZATION ID
QWHCNID NETWORK ID
QWHCCN CONNECTION NAME
QWHCTRN CICS TRANSACTION NAME
NETSNAME ORIGINATING SYSTEM NET-NAME
QWHSIDMQ MQ SUBSYSTEM NAME
MQ Summarization variables:
SM116REL MQ VERSION RELEASE NUMBER
710 - 5655-R36
STARTIME DATE AND HOUR WHEN TRANSACTION ENDED - SMFTIME
SYSTEM SMF SYSTEM ID
MQ CPU METRIC:
QMACCPUT CPU TIME USED
ii. Example processing time, 8 hour's SMF data from a large site:
Eight Hour's Input SMF File:
Size: 619 GigaBytes
SMF Records 255,361,968 Records
Elapsed Time: 536 Minutes
CPU Time: 2.96 Hours
MSU: 399 (SMF70CPA=37,309)
EIGHT Hour Output:
CICSTRAN 50,309,278 Transactions
DB2ACCT 111,796,879 Transactions
iii. Execution JCL examples:
1. Example JCL for z/OS for processing of SMF & IMSLOG data:
// EXEC MXGSAS
//CICSTRAN DD DSN=HLQ.OUTPUT.MOBILE.CICSTRAN.DATASET,DISP=NEW
//DB2ACCT DD DSN=HLQ.OUTPUT.MOBILE.DB2ACCT.DATASET,DISP=NEW
//IMSTRAN DD DSN=HLQ.OUTPUT.MOBILE.IMSTRAN.DATASET,DISP=NEW
//MQTRAN DD DSN=HLQ.OUTPUT.MOBILE.MQTRAN.DATASET,DISP=NEW
//WASTRAN DD DSN=HLQ.OUTPUT.MOBILE.WASTRAN.DATASET,DISP=NEW
//TYPE70 DD DSN=HLQ.OUTPUT.MOBILE.TYPE70.DATASET,DISP=NEW
//TYPE89 DD DSN=HLQ.OUTPUT.MOBILE.TYPE89.DATASET,DISP=NEW
//CICDS DD DSN=HLQ.OUTPUT.MOBILE.CICDS.DATASET,DISP=NEW
//DB2STATS DD DSN=HLQ.OUTPUT.MOBILE.DB2STATS.DATASET,DISP=NEW
//MOBILE DD DSN=HLQ.OUTPUT.MOBILE.PDB.DATASET,DISP=NEW
//SMF DD DSN=HLQ.YOUR.SMF.DATASET(S).DISP=SHR
//IMSLOG DD DSN=HLQ.YOUR.IMSLOG.IMS56FA.RECORDS,DISP=SHR
//SYSIN DD *
%INCLUDE SOURCLIB(MOBWRK01); /*DEFINE MOBILE WORK CRITERIA*/
%INCLUDE SOURCLIB(MOBWRK02); /*READ SMF & IMSLOG TO CREATE:
dddddd Default DATASET name Source
MOBCTR CICSTRAN.MOBILECICSTRAN SMF 110-1
MOBDTR DB2ACCT.MOBILEDB2ACCT SMF 101
MOBITR IMSTRAN.MOBILEIMSTRAN IMS 56FA
MOBMTR MQTRAN.MOBILEMQTRAN SMF 116
MOBWTR WASTRAN.MOBILEWASTRAN SMF 120
MOB7TR TYPE70.MOBILETYPE70 SMF 89
MOB8TR TYPE89.MOBILETYPE89 SMF 89
MOB9TR CICDS.MOBILECICDS SMF 110-2
MOB9TR DB2STATS.MOBILEDB2STATS SMF 100
%INCLUDE SOURCLIB(MOBWRK03); /*CREATE HOURLY DATA FOR AUDIT:
MOB7HR MOBILE.MOBILETYPE70HOUR
MOB8HR MOBILE.MOBILETYPE89HOUR
MOB9HR MOBILE.MOBILECICDSHOUR
MOB0HR MOBILE.MOBILEDB2STATSHOUR
MOBCHR MOBILE.MOBILECICSHOUR
MOBDHR MOBILE.MOBILEDB2HOUR
MOBIHR MOBILE.MOBILEIMSHOUR
MOBMHR MOBILE.MOBILEMQHOUR
MOBWHR MOBILE.MOBILEWASHOUR
CREATE IBM MOBILE WORK DATASETS:
dddddd dataset
MOBCIC MOBILE.MOBILECICS
MOBDB2 MOBILE.MOBILEDB2
MOBIMS MOBILE.MOBILEIMS
MOBMQ MOBILE.MOBILEMQ
MOBWAS MOBILE.MOBILEWAS
MOBHR MOBILE.MOBILEHOUR */
%INCLUDE SOURCLIB(MOBWRK04); /*PRINT REPORTS*/
%INCLUDE SOURCLIB(MOBWRK05); /*COMBINE PRODUCT/TYPE89*/
%INCLUDE SOURCLIB(MOBWRK06); /*CREATE CSV FILE */
RUN;
2. Example ASCII execution for full process
%INCLUDE SOURCLIB(MOBWRK00); /*DEFINE FILENAMES AND LIBNAMES*/
%INCLUDE SOURCLIB(MOBWRK01); /*DEFINE MOBILE WORK CRITERIA*/
%INCLUDE SOURCLIB(MOBWRK02); /*READ SMF AND IMSLOG TO CREATE*/
%INCLUDE SOURCLIB(MOBWRK03); /*CREATE MOBILE WORK DATASETS*/
%INCLUDE SOURCLIB(MOBWRK04); /*PRINT REPORTS*/
RUN;
3. Notes on execution.
-Even if you do not have all eligible products, use this example
so that, if you do add a new product, you will NOT have to change
you jobstream. For example, If you do not have IMS, then just use
//IMS LOG DD DUMMY for the input.
-Similarly, create all of the MOBILE.OUTPUT.product.DATASET "PDB's",
so they exist; if there are no input records for a product, then
it's "PDB" will have zero observations, taking no space, but that
will satisfy the rest of the code that expects them.
-Since these transaction datasets can be large, and are write once
read once, they are good candidates to be written to tape.
-The MOBWRK02 program that creates the MOBILEprodTRAN datasets KEEP
only the variables that are required, significantly reducing their
size. Nevertheless, sites with large counts of records can expect
large run times and large space allocations for the sorts needed to
create the output MOBILE.MOBILEXXXX datasets, although some further
tailoring options will be provided for further reductions.
iv. Additional MOBWRKCn programs are created to replace MOBWRK02/03:
For MXG sites that already create the CICSTRAN/DB2ACT/IMSTRAN etc
"PDB's", individual MOBWRKp3 programs, one for each product with
p=C/D/I/M/W, eliminate the need to read SMF data, and additionally
the MOBWRKC3/MOBWRKD3/MOBWRKI3/MOBWRKM3/MOBSRKW3 programs support
the concatenation of multiple days/weeks/ "PDB's", using the new
MXG-32.05-enhanced VMXGSUM with USEVGETDDS operand. Each of the
five product can be separately processed. For example, to read
four weekly CICSTRAN datasets you would use
// EXEC MXGSAS
//CICTRN1 DD DSN=YOUR.CICSTRAN(0),DISP=SHR
//CICTRN2 DD DSN=YOUR.CICSTRAN(-1),DISP=SHR
//CICTRN3 DD DSN=YOUR.CICSTRAN(-1),DISP=SHR
//CICTRN4 DD DSN=YOUR.CICSTRAN(-1),DISP=SHR
//CICDS1 DD DSN=YOUR.CICDS(0),DISP=SHR
//CICDS2 DD DSN=YOUR.CICDS(-1),DISP=SHR
//CICDS3 DD DSN=YOUR.CICDS(-1),DISP=SHR
//CICDS4 DD DSN=YOUR.CICDS(-1),DISP=SHR
//MOBILE DD DSN=YOUR.MOBILE.OUTPUT,DISP=OLD
//SYSIN DD *
%INCLUDE SOURCLIB(MOBWRK01); /* DEFINE MOBILE CRITERIA*/
%INCLUDE SOURCLIB(MOBWRKC3); /* READ EXISTING PRODUCT TRANS */
%INCLUDE SOURCLIB(MOBWRK04); /* PRINT REPORTS */
%INCLUDE SOURCLIB(MOBWRK05); /* COMBINE PRODUCT AND TYPE89 DATA*/
%INCLUDE SOURCLIB(MOBWRK06); /* CREATE CSV FILE */
3. APAR OA43983 - HIPER - ABEND0C4 IDA019R1+2AE8 on first VSAM CALL
after OPEN. This only occurs on z/OS 2.1.
2. Use of IBM File Manager can corrupt SMF files when copied. The File
Manager defaults to PAD=ON with x'00' as the default pad character,
causing all final '00'x bytes to be REMOVED from the output copy.
Changing to use PAD=OFF preserves the original SMF record.
1. Comparison of CPU times captured by RMF I, RMF III, and SMF.
This is NOT earthshattering; an MXG user asked who well the CPU
timings compared between RMF I, RMF III, and SMF 30 records,
and sent four hours data to analyze with MXG.
Initial summary:
- Four hours of data from five systems with z/OS 1.3 on a 2827-709,
2817-712 and 2817-720 from RMF I, RMF III, and SMF is compared.
This is not perfectly matched data: the site's RMF I data is written
at 15 minute intervals but with SYNC(59) instead of SYNC(0), while
the SMF 30s are written hourly and are NOT synchronized with SMF,
and RMF III writes every 30 seconds. z/OS 1.3
REPORT 1 - OVERALL COMPARISONS
- The "Hardware" records in REPORT 1 are close; the RMF III CPUG3
data recorded 909 seconds more Partition Dispatch Time (0.4%) than
did RMF I TYPE70 out of 203,223 seconds CPU time.
- The RMF III "Service Class" data in RCDG3 is slightly larger than
the RMF I type 72 subtype 3 records, recording 791 more (0.4%).
The RMF I/III average Capture Ratio for all systems is 89.5% of
the "hardware" CPU is recorded in Service Class in RMF I and III.
- The RMF III "Address Space" data in ASIG3 varies with 1503 more
total in RMF III than SMF Interval time, but it is inconsistent,
as three systems recorded more time in SMF than RMF III. But since
SMF was NOT synchronized, that these numbers are this close is good!
But, the SMF Capture Ratio is only 85% of the "hardware" CPU time.
Seconds of CPU time captured by RMF I, RMF III, and SMF.
SYS0 SYS1 SYS2 SYS3 SYS4 Total
"Hardware CPU Time":
Dataset Variable
a. RMF3 ZRBCPU CPUPHYSI 23214 55501 30298 29877 64321 203223
b. RMF1 TYPE70 CPUACTTM 23135 55009 30218 29883 64067 202314
c. RMF1 ASUM70LP LCPUPDTM 23135 55009 30218 29883 64067 202314
"Service Class CPU:"
Dataset Variable
d. RMF3 ZRBRCDS CPUTM 20655 51494 26443 26645 56688 182027
e. RMF1 RMFINTRV CPUTM 20568 51134 26393 26671 56467 181236
r RMF1 TYPE72GO CPUTM 20568 51134 26393 26671 56467 181235
"Address Space CPU:"
Dataset Variable
g. RMF3 ZRBASI ASICPUTA 19595 49032 25064 24713 54456 172863
h. SMF SMFINTRV CPUTM 19909 46615 26684 26380 51771 171360
These are the preceding CPU time metrics and their source:
RMF3 ZRBCPU - RMF III Record CPUG3.
RMF1 TYPE70 - RMF I Type 70 Subtype 1
RMF1 ASUM70LP - MXG Summary of TYPE70 PR/SM
RMF1 TYPE72GO - RMF I Type 72 Subtype 3 Service Class only
RMF1 RMFINTRV - MXG Summary of TYPE72GO
RMF3 ZRBRCDS - RMF III Record RCDG3.
RMF3 ZRBASI - RMF III Record ASIG3.
RMF1 SMFINTRV - SMF Type 30 Subtype 2/3
REPORT 2 - COMPARISON OF RMF I TYPE72-3 AND RMF III SERVICE CLASS
- This table compares the total CPU time and total ZIP time for each
Service Class. And here too, RMF III recorded 792 more seconds than
RMF I, although a few classes had more RMF I than RMF III, but these
data were not perfectly synchronized, so these again show goodness.
SRVCLASS RMF3CPUTM RMF72CPUTM DELTACPU RMF3ZIPTM RMF72ZIPTM
BATHI 7724.78 7787.33 -62.56 9.73 32.43
BATHOT 2347.31 2356.11 -8.80 4.26 5.84
BATLOW 33171.44 32792.04 379.40 2.95 137.36
BATMED 76069.23 75951.35 117.87 -54.48 274.11
BATMEDW 98.59 98.59 -0.00 . 0.00
DBHIGH 8029.33 7990.11 39.22 4946.80 5068.98
DBLOW 9454.16 9438.17 16.00 . 0.00
DDFADHOC 99.60 99.60 0.00 . 0.00
DDFCICS 1.84 1.84 -0.00 . 0.00
DDFPROD 839.37 837.34 2.04 909.92 1000.51
OMVS 62.09 46.04 16.05 11.00 12.34
ONLINHI 8804.13 8731.83 72.30 115.32 131.60
ONLINMED 8712.54 8662.36 50.18 54.85 79.23
ONLINTST 13.96 13.88 0.08 1.77 3.56
STCHI 3934.09 3903.70 30.39 207.75 250.54
STCLOW 3895.26 3868.81 26.44 0.07 0.72
STCMED 889.73 886.05 3.68 0.01 0.15
STCNDM 3565.27 3554.12 11.15 . 0.00
SYSOTHER 0.00 0.00 0.00 . 0.00
SYSSTC 6755.58 6717.66 37.92 1208.46 1293.00
SYSTEM 7178.80 7119.08 59.72 . 0.00
TSOPROD 330.44 328.99 1.45 . 0.00
TSOSPEC 50.44 50.44 0.00 . 0.00
========= ========== ====== ======== ==========
182027.98 181235.44 792.54 7418.41 8290.38
IV. DB2 Technical Notes.
1. Text
V. IMS Technical Notes.
1.
VI. SAS Technical Notes.
1. IEC988I jjj,sss,ddn(-#),dev,volser,hlq.CNTL DATASET NOT UNALLOCATED
DURING CLOSE RC 04
Beginning with z/OS 1.12, you might see this message
written to the JES SYSMSGS file referencing the CONFIG DD name at
your site.
This is an informational message and can be safely ignored.
See the IBM documentation for additional information about this
message.
In SAS 9.2 and later, the IEC988I message does not appear.
VI.A. WPS Technical Notes.
1. Text
VII. CICS Technical Notes.
1. Text
VIII. Windows NT Technical Notes.
1. Text
IX. z/VM Technical Notes.
1. Text
X. Email notes.
1. Text
XI. Incompatibilities and Installation of MXG vv.yy.
1. Incompatibilities introduced in MXG 32.05 (since MXG 31.31):
See CHANGES.
2. Installation and re-installation procedures are described in detail
in member INSTALL (separate sections for each platform, z/OS, WIN,
or *nix), with examples of common Errors/Warnings messages a new MXG
user might encounter, and in member JCLINSTT for SAS V9.2 or member
JCLINSTW for WPS. INSTALL also shows how to read SMF data on PCs/nix
using the FTP ACCESS METHOD.
XII. Online Documentation of MXG Software.
MXG Documentation is now described in member DOCUMENT.
XIIV. Changes Log
--------------------------Changes Log---------------------------------
You MUST read each Change description to determine if a Change will
impact your site. All changes have been made in this MXG Library.
Member CHANGES always identifies the actual version and release of
MXG Software that is contained in that library.
The CHANGES selection on our homepage at http://www.MXG.com
is always the most current information on MXG Software status,
and is frequently updated.
Important changes are also posted to the MXG-L ListServer, which is
also described by a selection on the homepage. Please subscribe.
The actual code implementation of some changes in MXG SOURCLIB may be
different than described in the change text (which might have printed
only the critical part of the correction that need be made by users).
Scan each source member named in any impacting change for any comments
at the beginning of the member for additional documentation, since the
documentation of new datasets, variables, validation status, and notes,
are often found in comments in the source members.
Alphabetical list of important changes after MXG VV.RR in MXG VV.RR+1:
Dataset/
Member Change Description
See Member CHANGES in your MXG Source Library for THIS MXG version, or
see Member CHANGESS in your MXG Source Library for all 8,935 changes
since 1984, and online at http://www.mxg.com/changes.