我的看剧历程 - 歌单 - 网易云音乐
我的看剧历程
我是从2011年夏天开始看日剧的，那时高考结束特别浮躁什么都做不下去，好友给我推荐了日剧，我竟然沉浸下来了爱上了日剧。四年多了，虽然看得不多，很多很好很经典的剧也没有补完，但一路下来也看了不少。...
我是从2011年夏天开始看日剧的，那时高考结束特别浮躁什么都做不下去，好友给我推荐了日剧，我竟然沉浸下来了爱上了日剧。四年多了，虽然看得不多，很多很好很经典的剧也没有补完，但一路下来也看了不少。初中看过两部花样男子，但真正的入坑剧却是野猪，彻底爱上则是从CB开始。前33首是陆续补起来的，后面的就是每季的追剧。说要做这个单很久了，终于动手做了，以后继续吧，记录我的看剧历程。
花样男子 1
花样男子 2
野猪大作战
Code Blue 1
Code Blue 2
血色星期一 1
血色星期一 2
柏原崇版恶作剧之吻
极道鲜师 1
极道鲜师 2
极道鲜师 3
花样少年少女
神探伽利略 1
正义的伙伴
14岁的妈妈
最后的朋友
深夜食堂 1
深夜食堂 2
深夜食堂 3
你教会我什么最重要
太阳再次升起
推理要在晚餐后
我不能恋爱的理由
幸运七人组
三花猫福尔摩斯的推理
东野圭吾推理系列
Sprout发芽
富贵男与贫穷女
Summer Rescue~天空的诊疗所~
东京机场管制保安部
Resident~实习医生五人组
最完美的离婚
最后的灰姑娘
飞翔情报室
神探伽利略2
潜入侦探蜥蜴
一吻定情~Love in TOKYO
救命病栋24小时5
SUMMER NUDE
海上诊疗所
安堂机器人
飞行员小姐
东京风潮~下町大家族物语
欢迎来到阴阳屋
S-最后的警官
失恋巧克力职人
我存在的时间
紧急审讯室
即使弱小也能获胜
路政英雄2014
金田一少年事件簿N
对不起青春
Dear sister
献给阿尔吉侬的花束
酒店礼宾员
表参道高中合唱部！
熟女正青春
朝5晚9：帅气和尚爱上我
掟上今日子的备忘录
无痛：诊断之眼
播放：10796次
网易云音乐多端下载
同步歌单，随时畅听320k好音乐
网易公司版权所有(C)杭州乐读科技有限公司运营：域名查询:cn域名删除时间
拟删除域名(网址)名单 -MXG CHANGES 10.10
COPYRIGHT (C)
MERRILL CONSULTANTS DALLAS TEXAS USA
MXG CHANGES 10.10
=========================member=CHANGE10================================
/* COPYRIGHT (C)
MERRILL CONSULTANTS DALLAS TEXAS USA */
This is the Production MXG Version 10.10, dated March 15, 1993.
Changes through:
Change 10.336 are
included in MXG
Version 10.10,
Mar 15, 1993
Change 10.323 were printed in Newsletter TWENTY-THREE, Mar 15, 1993
Change 10.304 are
included in MXG
PreRelease 10.6,
Feb 23, 1993
Change 10.265 are
included in MXG
PreRelease 10.5,
Jan 28, 1993
Change 10.251 are
included in MXG
PreRelease 10.4,
Change 10.241 are
included in MXG
PreRelease 10.3A, Dec 17, 1992
Change 10.235 are
included in MXG
PreRelease 10.3,
Dec 13, 1992
Change 10.208 are
included in MXG
PreRelease 10.2,
Oct 18, 1992
Change 10.199 were included in Early PreRelease 10.2,
Oct 12, 1992
Change 10.113 were included in MXG
PreRelease 10.1,
Jul 10, 1992
Change 10.104 were printed in Newsletter TWENTY-TWO,
Jul 10, 1992
Table of Contents:
MXG Software Status and Enhancements:
Incompatibilities, Installation, and Space Requirements.
Documentation of MXG Software.
MXG Technical Notes
- see NEWSLETTER TWENTY-THREE
MVS Technical Notes
- see NEWSLETTER TWENTY-THREE
VM Technical Notes
- see NEWSLETTER TWENTY-THREE
CICS Technical Notes
- see NEWSLETTER TWENTY-THREE
VIII. SAS Technical Notes
- see NEWSLETTER TWENTY-THREE
Change Log
MXG Software Status and Enhancements:
MXG 10.10 is the Production Version of MXG 10 (i.e., the version that
we "Produce" for all sites), dated March 15, 1993.
MXG 10.10 is a major revision, with many latent enhancements, and near
transparent installation.
Sites with normal MXG tailoring should need
less than 2 hours to unload, tailor, and submit the test jobstreams.
Make sure you read the COMPATIBILITY warning in Installation notes.
These enhancements are in MXG 10.10, but were not printed in the MXG
Technical Newsletter number TWENTY-THREE:
Note: There are 1965 members in MXG 10.10, not the 2000+ I thought
there would be.
MXG now creates 47,292 variables in 1195 data
sets with its 533,759 lines of source code.
Support for type 30 OpenEdition/MVS measurements
NETSPY Average Host Response calculation corrected
Major enhancements added in MXG 10.10, that were not in MXG 10.6:
Support for OpenEdition MVS, OMVS, RMF record enhancements.
Preliminary RS6000 AIX VMSTAT,IOSTAT,PS command processing
GMT offset, GMTOFFTM, available in MVS/ESA 4.3 RMF records.
DCOLLECT options SMSDATA creates nine new SMS construct datasets.
RMF reports can be produced from MXG TYPE70xx datasets.
Additional online MXG documentation members (ADOC and ACHAP).
Major enhancements added in MXG 10.6, that were not in MXG 10.5:
Support for Empact's Hipercache SMF record.
Support for IMF Release 2.8.
Support for Oracle 6.0.33.1.51.
Support for IBM 3495 Tape Library Dataserver's type 94 SMF record.
Support for (incompatible) Omegamon/CICS DATACOM SPE PTF QOC0109.
Support for STOPX37 Release 3.5.
Support for Empact's POOL-DASD user SMF record.
Support for Candle's IMS Transaction Reporting Facility, ITRF.
Support for Landmark for CICS's Release 9 and Release 1.0.
IBM-like RMF reports can be created with new ANALRMFR.
Additional HOGAN application fields added in CICSTRAN
HP's MPE data or HP/UX Unix data are both supported by TYPEHPCS
SLR-like IMS processing for sites with heavy fast-path in TYPESLRI
Additional CMF "type 240" subtypes supported in TYPECMF
Major enhancements added in MXG 10.5, that were not in MXG 10.4:
Support for MVS/ESA 4.3 and RMF 4.3.
Support for NPM Release 1.6.
Support for NETSPY Release 4.3 and LANSPY 1.1.
Support for IDMS Release 12 PM records confirmed.
Major enhancements added in MXG 10.4, that were not in MXG 10.3:
Support for ESCOM Multi-Image Facility (EMIF)
Support for VM/ESA 2.0
Validation of support for Velocity Software's XAMAP History files.
Major enhancements added in MXG 10.3, that were not in MXG 10.2:
Support for NPM 1.5.1 incompatible changes.
Correction of MXG-10.2-only error in ASUM70PR
Support for DFSORT Release 12 new fields.
Cleanup of all reported errors in prior prereleases.
Toleration support for VM/ESA 2.0 MONWRITE data.
Major enhancements added in MXG 10.2:
Powerful new "_L" and "_K" macro architecture allows full tailoring
of MXG datasets (variables kept/dropped, compression, blocksize,
the DDNAME to which the dataset is written, etc.).
Support for DB2 Trace IFCID 172/ 177 added, Audit/SQL reports fixed.
Support for FACOM AIM Version 12 type 116 SMF record changes.
Support for FACOM PDLF Type 127 for MSP/EX.
Support for HP Unix (HP/UX) PCS Performance Collection System data
Support for IBM TCP/IP Version 2 Release 2 SMF record.
Support for IBM TIRS type 96 SMF record coded.
Support for Network Alert APAR OY49717 in SMF Type 37.
Support for OMEGAMON II for VTAM V150 user SMF record coded.
Support for OPC changes.
Support for SAP Accounting data in CICS type 110 or journal file.
Support for SIMWARE SIM/XFER VTAM user SMF record.
Support for TMS Billing-by-dataset using enhanced DSNBRECD dataset.
Support for VSE DOS POWER Version 4.2
Support for Xerox Printer's SFS Status File System records.
Support for XCOM 6.2 Version 2.2.2G SMF record.
Alert that Legent's MIM can corrupt MXG Tape Mount counting.
"Appended" IMS L has now been tested with IMS 2.2.
Continued enhancement of ANALDB2R for DB2 reports.
Major enhancements added in MXG 10.1 but not listed in Newsletter 22:
OPC/A log processing major revision, additional datasets created.
Verstand's product, TTX, is now included in MXG Software.
Support for AS400 V2R1M0 added, and AS400 support was revised.
NPM 1.5.1 subtypes 144-150 (NPMEVX25 dataset) errors were corrected.
Sample IEFU83 exit to filter type 40 records for tape-only added.
Major enhancements added in MXG 10.1 that were listed in NL 22:
Required for CICS/ESA 3.3,
Required for VM/ESA 1.1.1,
Required for TYPEIMS major revision in IMS log processing.
Strongly recommended for DB2 sites, because it:
- has significant corrections in ANALDB2R reporting,
- has speeded up MXG DB2 processing and reduced WORK space needed,
- allows DB2ACCT direct to tape for sites with large DB2 activity,
- has new ASUMDB2A to summarize and reduce size of DB2ACCT.
- has MVS Account fields added to DB2ACCT (DB2 2.3).
Offers support for these new products or releases:
Support for AICorp's KBMS user SMF record.
Support for Amdahl's APAF replacement for MDFTRACK.
Support for Blue Line's Vital Signs for VTAM type 28.
Support for Fujitsu's FACOM MSP/EX (incompatible) SMF records.
Support for MVS/ESA 4.2 Dynamic I/O Reconfig in MXG Tape Monitor.
Support for NETSPY Release 4.2 added.
Support for NETSPY Token-Ring records added.
Support for ROSCOE Release 5.7 changes to SMF data.
Support for RSD's WSF/WSF2 Release 3.4.1.
Support for SPMS 1.2.13 incompatible changes.
Support for STOPX37 Release 3.4.
Support for Software Ag "Natural Process" SMF record.
Support for System Center's NETMASTER type 37 SMF records.
Support for The Network Director North Ridge Software
Support for UNIX iostat and vmstat commands from ULTRIX.
ASMVTOC avoids 213/314 abends reading VTOC of TPF or VM
LPAR CPU utilization reports added.
MINTIME=,MAXTIME= parameters added to VMXGSUM.
MVS/ESA 4.2.0 changed format of DEVNR/UNITADR in TYPE75.
MXG Tape Mount Monitor supports MVS/ESA dynamic reconfiguration.
New dataset TYPE40_D can be created for tape analysis
TAPEs allocated) added to PDB.STEPS/JOBS.
Trending with INTERVAL=MONTH members added.
Each of these enhancements are described in the Change Log, below.
The following table lists announced availability dates for the IBM
product, and the corresponding Version of MXG required to support
that IBM product.
Availability
MXG Version
Product Name
MVS/370, MVS/XA (all)
RMF 4.1.2 (for MVS/ESA 3.1.3)
(for MVS/ESA 4.1)
Oct 26, 1990.
MVS/ESA 4.1
Oct 26, 1990.
MVS/ESA 4.2
Mar 29, 1991.
RMF 4.2.1 (for MVS/ESA 4.2)
Mar 29, 1991.
MVS/ESA 4.2.2
RMF 4.2.2 (for MVS/ESA 4.2.2
MVS/ESA 4.3
RMF 4.3.0 (for MVS/ESA 4.3
CICS/ESA 3.1
CICS/ESA 3.2
Jun 28, 1991.
CICS/ESA 3.3
Mar 28, 1992.
Oct 28, 1991.
1.1.0 (370 Feature)
Oct 26, 1990.
1.1.0 (ESA Feature)
Mar 29, 1991.
Dec 27, 1991.
Dec 23, 1992.
Incompatibilities, Installation, and Space Requirements.
1. Incompatibilities in MXG 10.10 which will cause syntax errors:
If these members exist in your USERID.SOURCLIB, then you must
replace them, by re-tailoring your changes starting with the
new MXG 10.10 member:
IMACCICS IMACCIMS IMACCMF
IMACDCOL IMACIMS
IMACINTV IMACMONI IMACNSPY IMACOPC
IMACPDSM IMACROSC
IMAC30DD IMAC40DD IMAC434D
These members defined the DDNAME to which MXG sent certain
datasets (eg., MACRO _CICTRAN CICSTRAN % set the DDname for
DATA _CICTRAN.CICSTRAN).
The new "_L" architecture provides
the same function with different syntax (eg., now the macro
_LCICTRN defines both the DDNAME (LIBREF) and dataset name).
Change 10.175 provides specific details of what old-names have
to be changed to what new-names for these incompatibly changed
If you had tailored BUILDPDB/3 to create TYPETMNT (the MXG
Tape Mount Monitor records), you will need to remove your
tailoring in members EXPDBINC,EXPDBVAR,EXPDBCDE,EXPDBOUT.
In MXG 10.10 TYPETMNT is automatically created by BUILDPDB/3.
Sites migrating to MXG 10.10 from MXG 9.9 thru MXG 10.x should find
no other compatibility issues.
Sites migrating to 10.10 from an MXG version earlier than 9.9 must
read the compatibility section of the installation instructions in
MXG Newsletter TWENTY-ONE (also in member NEWSLTRS).
MXG 10.10 will still execute under SAS 5.18, but this is likely to
be the last version that will fully work under that archaic version
of SAS; MXG intends to begin to exploit Version 6 features in MXG
future versions, and we strongly recommend use of SAS 6.07 or later!
2. Installation and re-installation procedures are described in detail
in member INSTALL, but they are summarized here:
a. Install member MXGSAS as JCL Procedure MXGSAS in your PROCLIB.
b. Allocate a 70-cyl PDS: MXG.V1010.MXG.SOURCLIB, & use IEBUPDTE
to read the MXG tape to create the 1800+ member Source Library.
c. Allocate a 1-cyl PDS:
MXG.V1010.USERID.SOURCLIB for your site
"Installation Tailoring" Source Library.
Installation specific
tailoring (like telling MXG your shift hours, which performance
groups are TSO, CICS, etc.) is done by copying and modifying MXG
source members into V1010.USERID.SOURCLIB.
d. Allocate a 1-cyl SAS Data Library:
MXG.V1010.MXG.FORMATS and
execute SAS to create the library of Formats required by MXG.
Sample JCL for the above three steps is in member JCLINSTL.
e. If re-installing MXG, copy your existing USERID.SOURCLIB library
members into the MXG.V1010.USERID.SOURCLIB. Then examine the set
of IMACs that were changed incompatibly (see member CHANGES).
If any members in MXG.V1010.USERID.SOURCLIB are in that list,
you must reinstall your site's tailoring for that IMAC, starting
with the IMAC member from the MXG 10.10 Source Library.
e. If this is the initial install of MXG, tailor these members into
your MXG.V1010.USERID.SOURCLIB tailoring library:
IMACACCT (Account Length),
IMACSHFT (Shift Definitions),
IMACWORK (Performance Group to Workload mapping), and
IMACSPIN (for BUILDPDB).
Each IMAC member is self-documenting, and IMACAAAA is the index
of all of the IMACs.
You should at least scan IMACAAAA to see
the acronyms MXG uses for the many products MXG supports.
f. EDIT and submit member JCLTEST6 (JCLTEST if still on SAS 5.18)
to verify that your tailoring did not create any errors.
g. EDIT and submit JCLPDB to create a Daily PDB for testing.
use the TYPE.... members to process specific data sources, use
the ANAL.... members for report examples, the GRAF.... members
for SAS/GRAPH reports.
You have now installed MXG 10.10 in its own set of libraries. When
parallel testing is complete and are ready to implement MXG 10.10
in production, rename your three current MXG Production Libraries
(MXG.MXG.SOURCLIB, MXG.USERID.SOURCLIB, and MXG.MXG.FORMATS) to
(MXG.BACK.MXG.SOURCLIB, MXG.BACK.USERID.SOURCLIB, MXG.BACK.MXG....)
and rename the MXG.V1010.x.y libraries to their Production names!
Again, detailed installation instructions are in member INSTALL
Always read comments in the CHANGES member for compatibility issues, as
well as for any last minute changes.
Whenever you install changes or test a new version of MXG (or even your
own reports), be extra careful to look on the SAS log for any real error
conditions. Search for all occurrences of "ERROR:" and
"UNINITIALIZED" and "NOT CATLGD", as they may indicate a serious error.
A PROC PRINT and a PROC MEANS of each new MXG-built SAS dataset can help
you to understand their contents, and should be used to examine any
unusually large, negative, or suspicious values.
Print all variables in
the dataset, and read the variable's descriptions in its ADOC member.
Documentation of MXG Software.
Member CHANGES always contains the version number of MXG Software, and
it lists changes that were installed in that version.
Members named
Changenn are the CHANGES member from MXG Version "nn".
Each change in
MXG software is documented by a Change number and text.
The text of
each Change identifies the member(s) that were added or altered.
Documentation (especially for new product's support) is often
also found in comments at the beginning of those members listed in the
Change entry.
The CHANGE member is designed to be read online (with SPF
BROWSE); you can search for specific product name references (CICS,
MVS/ESA, etc.), or the MXG member name.
Member NEWSLTRS contains the text of all newsletters (up through the
newsletter that accompanied that MXG release). You can search NEWSLTRS
for product name or acronym to find the technical notes, APARs, etc.
from all MXG newsletters.
The Change Log pages of each Newsletter are
in member CHANGES or CHANGEnn and are not repeated in member NEWSLTRS.
Member DOCVER lists alphabetically ALL datasets and variables that can
be build by this MXG Software Version.
"Delta-documentation" between
MXG versions, which lists only those datasets and variables that were
Changed by version "nn" is found in DOCVERnn members for each version.
Chapter FORTY in the MXG Guide and MXG Supplement books are still the
primary documentation of MXG datasets and their variables (at least for
those data sources that existed in 1987!).
This should be the first
place you look for information about MXG variables and/or datasets.
As each section of chapter FORTY is rewritten, it becomes an ADOCxxxx
member of MXG.SOURCLIB, providing online documentation for product xxxx.
ADOCs contain alphabetic descriptions of datasets and variables, the
instructions on how to enable that product, bibliography to the vendor
documentation, sample PROC PRINT and PROC MEANS of real data, and the
MXG member names that you use to process that product, etc.
great? It will be when finished - this is work in progress!
Beginning with MXG 10.3, there has been an IMACxxxx member for every
product supported by MXG.
Once you know the xxxx suffix for a product,
you then know the names of all of the MXG members for that product:
IMACxxxx - Defines record IDs, and "_K,_L" macros for product xxxx.
ADOCxxxx - "Chapter FORTY" style dataset and variable documentation.
VMACxxxx - The "real" code member, often documentation in comments.
TYPExxxx - Standalone member to test or process product xxxx records.
ASUMxxxx - Summarization example (only for some products)
TRNDxxxx - Trending example (only for some products)
ANALxxxx - Reporting/analysis example (only for some products)
GRAFxxxx - SAS/GRAPH report example (only for some products)
EXyyyzzz - OUTPUT exit for each dataset.
There can be more than one
dataset per product.
The EX member name suffix yyyzzz is
the same as the suffix of "_L" and "_K" macros defined in
IMACxxxx for the product.
See further discussion under
"Using the MXG Exit Facilities".
Member IMACAAAA is an index of all IMACs, and is the best place to
begin to find what xxxx suffix Merrill chose for which product!
You can often find additional documentation by searching members
NEWSLTRS, CHANGES, and the CHANGEnn members for the xxxx suffix.
Finally, remember that MXG is source code, so you can often find your
answer by BROWSE/EDIT of the source member, especially the VMACs that
actually create the data set, or ANALs that analyze the MXG data sets.
In most cases, the MXG Variable name is the IBM or Vendor's field or
DSECT field name. In other cases, the DSECT field name is carried as a
comment beside in the MXG INPUT statement to map field name to MXG's
variable name.
MXG does expect that you will also have access to the
vendor's documentation of the data records you are processing.
The MXG Technical Newsletter is published aperiodically, one copy per
licensed site, and describes changes and enhancements to the software,
provides APARs and PTFs affecting MXG users, and provides tutorial
information of interest to MXG users.
Change 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 of the MXG SOURCLIB will always be more accurate than
the printed changes in a Newsletter, because the software is created
after the newsletter is sent to the printer!
Member CHANGES always identifies the actual version and release of
MXG Software that is contained in that library.
The actual code implementation of some changes in MXG SOURCLIB may be
different that described in the change text (which might have printed
only the critical part of the correction that can be made by paper).
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.
Alphabetic INDEX of significant changes in MXG 10.10 (since MXG 9.9):
Description
Powerful new "_L" and "_K" macros tailor MXG datasets
Support for MVS/ESA 4.3.
ADOCAAAA 10.332
Seventy-Three ADOCs documentation members now exist.
ANALDB2R 10.001
DB2 Report truncated character values.
ANALDB2R 10.034
SORTBY= operand parsed only the first SORT variable.
ANALDB2R 10.046
LIBRARY SMF IS NOT VALID message with PMSQL04 report.
ANALDB2R 10.047
DBID/OBID hex values printed instead of name.
ANALDB2R 10.055
Date/time selection in PMSACC01/02 produced no report
ANALDB2R 10.094
ANALDB2R Accounting report uses ASUMDB2A if exists.
ANALDB2R 10.135
DB2 Audit report may not be produced.
ANALDB2R 10.158
DB2 SQL Trace report FORMAT NOT FOUND error.
ANALDB2R 10.272
Buffer Pool statistics average values wrong.
ANALDSET 10.097
VSAM data sets may have wrong PROGRAM name.
ANALMONI 10.066
TMON/CICS sample report filled WORK file.
ANALRMFR 10.301
IBM-formatted RMF reports are now produced by MXG.
ANALRMFR 10.301
IBM's RMF reports produced from MXG datasets.
ASMIMSLG 10.084
Major revision in IMS log processing algorithms.
ASMIMSLG 10.142
Revision to "Appended" IMS log processing.
ASMIMSLG 10.191
"Appended" IMS process might miss RACF segment
ASMISMLG 10.146
New "Appended" IMS log processing works with IMS 2.2.
MXG Tape Mount Monitor supports Dynamic I/O Reconfig.
(MXG 10.1 only). ABEND S55F at startup.
MXG Tape Monitor sets TMNTRTRN=3 for MIM event.
ASMTMNTO 10.177
MXG Tape Mount Monitor for sites still on MVS/XA.
Avoid 213/314 abends reading VTOC of VM/TPF volumes
(MXG 10.1 only). Assembler error MSGAREA.
Use ASMVTOCO for ASMVTOC under MVS/ESA 3.1.3.
ASMVVDS fails with User 666 Abend.
ASUMDB2A 10.090
DB2 Account "transactions" summarized into ASUMDB2A.
ASUM70PR 10.131
PR/SM,MDF,MLPF summarization now supports 16 LPARs.
ASUM70PR 10.218
MXG 10.2 only, corrupted Effective/Management times.
ASUM70PR 10.284
Amdahl MDF LPARNUM=0 now supported, for 17 LPARs.
ASUM70PR 10.335
PCTOFHDW busy in this partition added to RMFINTRV.
BUILDPDB 10.117
BUILDPDB under SAS 6.07 needs changes.
BUILDPDB 10.129
Execution under CMS requires changes.
BUILDPDB 10.153
Step account variable SACCT1 now added to PDB.
BUILDPDB 10.190
JES APAR OY56235 filling SPIN library circumvention.
BUILDPDB 10.298
TOTLINES added to PDB.PRINT dataset.
SAS 6.07 under CMS has problems for MXG.
CONFIG07 10.109
Option S=72, s2=72 added to MXG Config members.
EXCICJRN 10.132
New exit for CICS journal data sent to SMF.
CPURCTTM PTF now exists, circumvention removed.
GRAFxxxx 10.227
SAS 6.07 replaced XSWISS font name with SWISS.
Not all DB2 graphs were produced.
GRAFLPAR 10.052
LPAR CPU utilization reports added.
GRAFTRND 10.049
Graphic trending reports were not always correct.
IMACACCT 10.119
Invalid type 30 subtype 1 SMF caused INPUT STATEMENT.
CORRNAME/CORRNUM set from QWHCATYP now.
Support for VSE DOS POWER Version 4.2 account records
IMACFACO 10.100
Fujitsu's FACOM MSP/EX SMF records now supported.
IMACFMTS 10.173
Member made archaic by SAS 6.07 FMTSEARCH option.
IMACICSA 10.164
Support for SAP Accounting data in CICS type 110.
IMACICUS 10.297
Optional HOGAN application variables in CICSTRAN.
New macro _DB2ACCT added. Compatibility exposure.
TAPEs allocated) added to PDB.STEPS/JOBS.
PDB.JOBS can have JELPSTM missing when it should not.
(MXG 10.1 only) JCLPDB6 fails, TYPETMNT not found.
JCLTEST6 10.030
INVALID DATA FOR SMFTIME, SAS zap MV313550 required.
MNTH.... 10.091
Trending with INTERVAL=MONTH members added.
MONTHBLD 10.206
All JCLPDB6 PDB & ASUM.... datasets are in MONTHBLD.
Example JCL Procedure MXGSAS now provided
TRACECLS= parameter does not select all IFCIDs.
RMFINTRV 10.299
Additional statistics added to RMFINTRV dataset.
TRNDDB2A 10.093
TRNDDB2A Account Trending uses ASUMDB2A if exists.
Verstand's TTX product is now included in MXG.
TYPEAICO 10.048
Support for AICorp's KBMS user SMF record.
TYPEAIM6 10.161
Support for FACOM's AIM Version 12 type 116 SMF.
TYPEAPAF 10.078
Support for Amdahl's APAF replacement for MDFTRACK.
TYPEAPAF 10.143
Variable Balance not kept in APAFDOMA
TYPEASTX 10.245
Support for Legent's ASTEX Trace Record
TYPECIMS 10.063
IMF flag variables wrong if multiple bits are on.
Boole's CMF variable R783PT in error.
Support for IMF Release 2.8.
TYPECTLD 10.327
CONTROL-D Release 2.0.0 is also supported.
TYPECTLD 10.327
CONTROL-D Release 2.0.0 is supported.
MVS Account fields added to DB2ACCT!
DB2ACCT fields ACCOUNTn were not input.
MVS Account fields now are actually input to DB2ACCT!
TYPEDCOL 10.071
INVALID VALUE FOR FUNCTION DATEJUL message.
TYPEDCOL 10.148
DCOLBKUP variables UBALLSP,UBUSESP,UBRECSP wrong.
TYPEDCOL 10.221
DCOLLECT variable UCTOTAL was incorrectly documented.
TYPEDCOL 10.307
DCOLLECT SMSDATA writes SMF constructs records.
TYPEFOCU 10.334
FOCUS record caused INPUT STATEMENT EXCEEDED error
NETVIEW FTP SMF record timestamps reversed.
TYPEF127 10.162
Support for FACOM PDLF Type 127 for MSP/EX Version.
TYPEHIPR 10.300
Support for Empact's HiperCache SMF records.
TYPEHPCS 10.178
Support for HP Unix (HP/UX) PCS Performance Data.
TYPEHPCS 10.294
HP's MPE operating system records now supported.
FSTTRKR/W large values are actually negative values.
TYPEIDMS 10.219
IDMS variable DBKDBKEY was incorrectly documented.
TYPEIDMS 10.265
Support for IDMS Release 12 PM records confirmed.
TYPEILKA 10.121
Invalid data because incorrect offset/documentation.
TYPEIMSA 10.142
STRTTIME/ENDTIME/INPQUETM/SERVICETM/RESPNSTM wrong.
TYPEIMSA 10.205
NMSGPROC value wrong. Must use ASMIMSLG for IMS log.
TYPEIMSA 10.288
Zero service time corrected.
TYPEITRF 10.273
Support for Candle's IMS Trans Report Facility,ITRF.
TYPEMON8 10.020
Landmark CICS "INVALID OFFSETS" message.
TYPEMON8 10.067
MONITASK variables STRTTIME/CREATIME now equal.
TYPEMON8 10.145
Landmark CICS variable TAMRCNT input incorrectly.
TYPEMON8 10.271
Support for Landmark's/CICS Release 9 and Release 1.
TYPEM204 10.120
MODEL204 variable M24IODEV input, EXM24ACT eliminated
TYPENATP 10.033
Support for Software Ag "Natural Process" SMF record.
TYPENETP 10.039
NETPACTM was total response, should be average.
Support for The Network Director North Ridge Software
TYPENSPY 10.015
Support for NETSPY Token-Ring records added.
TYPENSPY 10.057
Support for NETSPY Release 4.2 added.
TYPENSPY 10.144
NETSPY type 'N' records cause INPUT STATEMENT EXCEED.
TYPENSPY 10.262
Support for NETSPY Release 4.3 and LANSPY 1.1
TYPENSPY 10.326
NETSPY AHOSTRSP calculation corrected.
TYPEOMCI 10.182
Omegamon V550 ESRA (user) SMF "INPUT EXCEEDED".
TYPEOMVT 10.194
Support for OMEGAMON II for VTAM V150 user SMF.
Major revision for OPC/A log processing.
Support for Changes to OPC records.
RECFM= parameter removed so RECFM=U data can be read.
TYPEORAC 10.291
Support for Oracle 6.0.33.1.51.
TYPEPOOL 10.274
Support for Empact's POOL-DASD user SMF record.
TYPEQAPM 10.110
Support for AS400 V2R1M0 and restructured members.
TYPERMDS 10.102
RMDS messages INVALID DATA FOR RMDSMXVR eliminated.
TYPEROSC 10.022
Support for ROSCOE Release 5.7 changes to SMF data.
TYPEROSC 10.101
ROSCOE ADSFUN.. variables values corrected.
TYPEROSC 10.138
ROSCOE JCK and Documentview added to ROSCOVPE.
TYPERSxx 10.319
Support for RS6000 AIX VMSTAT,IOSTAT,PS commands.
Support for XEROX Printer's SFS Status File System.
Support for SIMWARE SIM/XFER VTAM user SMF record.
SIMWARE initial support revised.
TYPESLRI 10.290
SLR-like IMS log processing for Fast Path.
Header/Trailer messages on log were not always right.
TYPESPMS 10.011
SPMS R2.1.4 invalid record circumvented.
TYPESPMS 10.069
SPMS 1.2.13 inserted four byte field, causing errors
STC 4400 decode used wrong bits of STC07TYP.
STC4400 HSC SMF record for Release 1.2 incompatible.
STC 4400 Silo HSC variables formatted.
STC 4400 variables LSBECON1/2 incorrectly documented.
TYPESYNC 10.115
SYNCSORT variable COREREQ can be negative.
Support for IBM's TCP/IP Version 2 Release 2 SMF.
TYPETIRS 10.181
Support for IBM type 96 SMF record from TIRS.
TYPETMNT 10.200
Legent's MIM corrupts MXGTMNT Tape Mount count.
TYPETMS5 10.060
TMS inactive DSNBs now deleted, caused wrong VOLSER.
TYPETMS5 10.082
TMS.TMS had DSNB fields, TAPEFEET calculation changed
TYPETMS5 10.185
DSNBs could have been skipped.
TYPETMS5 10.196
TMS Billing-by-dataset enhanced in DSNBRECD dataset.
TYPETMS5 10.289
"Dead" tapes no longer create DSNBRECD observation.
TYPETMVS 10.058
TMON/MVS "INVALID DATA for WKLCPURF" message.
TPX variable TPXELAP has wrong value.
VMSQLxxx datasets enhanced for SQL/DS under VM.
TYPEVMXA 10.036
VM/ESA 1.1.1 additions now supported.
TYPEVMXA 10.071
VM/ESA VXSYTCUP dataset has only 49 observations.
TYPEVMXA 10.163
Candle's VCOLLECT 5.1.0 still writes invalid "VVBs".
TYPEVMXA 10.244
Support for VM/ESA Release 2.0.
Support for RSD's WSF/WSF2 Release 3.4.1.
WSF 3.3.6 caused error (no problem with 3.4.1).
Support for Velocity Software's XAMAP History files.
TYPEXCOM 10.165
Support for XCOM 6.2 Version 2.2.2G SMF record.
STOPX37 Release 3.4 is supported.
Support for Empact's STOPX37 Release 3.5.
DB2 SQLCODE can be negative, MXG read as positive.
DB2 Trace IFCID 172 and 177 now tested and supported.
DB2 optimizer's cost estimate was incorrect.
DB2 Trace statement Numbers now print as decimals.
DB2 T102S044 lock fields were incorrect.
Invalid type 110 subtype 2 could cause MXG to loop.
Omegamon error causes INVALID DATA FOR SMFPSRSN.
Type 110 STOPOVER due to bad record eliminated.
Support for CICS/ESA 3.3.0 monitor (CICSTRAN) data.
Support for CICS/ESA 3.3.0 statistics datasets.
Enhanced CICS error messages for EXCLUDE/INCLUDE.
OMEGAMON/CICS V550 DATACOM SPE is incompatible.
Fourth TCBs CPU time was not included in CICINTRV.
Spool off-load type 24 can cause STOPOVER abend.
Blue Line's Vital Signs for VTAM type 28 supported.
NPM 1.5.1 NPMEVX25 (subtypes 144-150) error fixed.
Line PCTBUSY in each direction measured separately.
(MXG 10.1 only). INVALID DATA FOR NPMPDUTH.
NPM variables LLBSSTIM/LLBSPTIM incorrect.
Support for NPM Release 1.6
Variables ACTDLYTM, RESDLYTM, DSPDLYTM created.
Some APPC variables in TYPE30 have wrong value.
Support for OpenEdition/MVS type 30 enhancements.
TYPE30OM 10.325
Type 30 support for OpenEdition/MVS
Error in processing SMF type 33 (APPC) records.
System Center's NETMASTER type 37 SMF record support.
Support for Type 37 Network Alert APAR OY49717.
INPUT STATEMENT EXCEEDED for subtype 5.
New dataset TYPE40_D can be created for tape analysis
DIV type 41 SMF record timestamps misdocumented.
Type 42 SMF record causes STOPOVER ABEND.
PSF type 6 record had FORM truncated.
Incompatible change to type 6 SMF record by PSF.
PRUWTR type 6 SMF record has incorrect READTIME.
VSAM Data and Index component names & SMS data added.
TCP/IP SMF record defaults to type 70!
Negative CPUACTTM/PCTCPUBY in TYPE70 with PR/SM/
Support for OpenEdition MVS, OMVS, RMF records.
TYPE70PR variable NRPRCS corrected.
PCTRDYWT variable now created.
GMT Offset, GMTOFFTM, available in MVS/ESA 4.3.
SWAP counts corrected.
ESCON converter flag variable ESCACVC not set.
MVS/ESA 4.2.2 EMIF Feature corrupts TYPE73 data set.
Only real channels create TYPE73 observations now.
MVS/ESA XCF Type 74 causes INPUT STATEMENT EXCEEDED.
MVS/ESA 4.2.0 changed format of DEVNR/UNITADR.
CMF Type 78 incorrect R783CPDN value causes 0 obs.
Type 79 subtype 1 corrections.
RMF 79 records appear to be un-deaccumulatable.
CA TOP SECRET caused INPUT STATEMENT EXCEEDED error.
RACF events consolidated in new TYPE80A dataset.
JES3 type 84 INPUT STATEMENT EXCEEDED error.
Support for IBM 3495 Tape Library Dataserver SMF.
HSM dates TTOCDLR and TTOCXPDT were wrong.
MINTIME=,MAXTIME= parameters added to VMXGSUM.
VMXGVTOC 10.018
CRITICAL ERROR IN VTOC if DSORG=PS-SUL data found.
VMXGVTOC 10.054
ISAM index space not recognized in VTOC.
VMXGVTOC 10.243
SAS 6.07 ZAP V6-SYS-FILE-4673 required.
VMXGVTOF 10.125
Variable DS4VTOCE input but not kept.
VMXGVTOF 10.171
VTOCs with freespace starting in track 1 missed it.
NOT SORTED when implementing MXG 9.9
TYPE70PR,DB2ACCT/STAT0/STAT1 added to weekly/monthly.
All JCLPDB6 PDB & ASUM.... datasets are in WEEKBLD.
BY list for WEEK.ASUM70PR wrong.
344 Compiler circumvention causes UNINITIALIZED msg.
Support for ULTRIX UNIX iostat and vmstat commands.
Inverse chronological list of all Changes:
NEXTCHANGE: Version 10
Change 10.336
The sample JCL Procedure MXGSAS is now provided in member
MXGSAS, and is now used in MXG JCL examples.
The PROC is
Mar 11, 1993
simply an extension to the SAS607 JCL Proc, with the MXG
data sets and options provided to minimize your JCL.
Using MXGSAS, it is no longer necessary to override the
BLKSIZE on the //WORK DD, because there is no BLKSIZE
specified on that DD in the PROC, which permits the MXG
CONFIG07 default of BLKSIZE(DASD)=HALF to control the
blocksize. (Previous JCL examples showed the override
because the SAS607 JCL Proc had hardcoded BLKSIZE).
symbolic parameters are provided in MXGSAS:
The highlevel qualifier of your MXG data sets,
defaults to MXGHLQ='MXG'
The highlevel qualifier of your SAS data sets,
defaults to SASHLQ='SAS.SAS607'.
Can be used to override, but the PROC itself
concatenates
&MXGHLQ..MXG.SOURCLIB(CONFIG07),
so there is no requirement to specify CONFIG=
Cylinders of work space. Default is (30,10)
Cylinders of sort work space in each of three
//SORTWKnn DDs.
Explicit DDs are included to
preven historically, SAS
and SORT packages have ABENDed when dynaloc was
used and there are multiple sorts of datasets of
different sizes (large, then small, then large
dataset sorting is common in BUILDPDB).
However, this is an example JCL PROC, and you are free to
modify it to meet your installation's JCL requirements.
Change 10.335
Program ASUM70PR enhanced to merge PR/SM data into the
RMFINTRV and added these three new variables:
Mar 11, 1993
PLATCPUS - Number of CPUs in the hardware platform
PLATBUSY - Total "platform" CPU busy of the PLATCPUS
PCTOFHDW - Percentage of platform busy in this MVS system
RMFINTRV describes each MVS system in a PR/SM partition,
while ASUM70PR describes the whole box.
The RMFINTRV
variable PCTCPUBY is the percentage of the interval during
which the NRCPUS in this MVS system were dispatched.
Assume a 100 second interval, and assume that you have a
with two partitions, a "test" partition as a
that can use three CPU engines, and a "prod"
partition as a
that can use all six engines, and
assume you have Capped the test partition at 33%.
utilization, then, PLATBUSY would be 100% (of PLATCPUS=6
engines), the test partition RMFINTRV PCTCPUBY would be
66% (of NRCPUS=3 engines) and the prod partition RMFINTRV
PCTCPUBY would be 66% (of NRCPUS=6 engines).
There were
600 seconds of total hardware platform CPU busy
(PLATCPUS=6)*(PLATBUSY=100%)*(DURATM=100) = 600, and
there would have been 200 seconds in test partition busy
(NRCPUS=3)*(PCTCPUBY=66%)*(DURATM=100) = 200, and there
would have been 400 seconds in prod partition busy
(NRCPUS=6)*(PCTCPUBY=66%)*(DURATM=100) = 400 seconds,
and PCTOFHDW can be calculated for the test partition:
PCTOFHDW = 100*(NRCPUS*PCTCPUBY)/(PLATCPUS*PLATBUSY);
= 100*(3*66)/(6*100) = 100*(1/3)= 33%
which shows that while PCTCPUBY=66% in RMFINTRV, in fact,
the test partition was using the full 33% of the hardware
platform that cappi arguably the test
partition is at 100% of the capacity you gave it!
Unfortunately, the Capping Target value is not stored in
the type 70 record, but PCTOFHDW may be a better measure
of processor utilization in a PR/SM environment with
shared processor engines.
Thanks to Gene Fernando, American Honda Motor Co, USA.
Change 10.334
FOCUS SMF record processing code caused INPUT STATEMENT
EXCEEDED RECORD length (because MXG did not protect for an
Mar 20, 1993
82-byte short record); the change was made in MXG 10.3,
but not entered in CHANGES, and thus I do not know to whom
to give thanks.
(If it's you, let me know!).
Change 10.333
DB2ACCT fields ACCOUNTn were not input. The test for the
existence of account fields (IF QWHSNSDA GE 6) should have
Mar 20, 1993
been GE 7, and needed to be relocated until after IMACDB2H
had been included (since that's where QWHSNSDA is input!).
Finally, the offsets for the QMDA triplet should have been
73, 77, and 79 instead of 75, 81, and 83!
Thanks to Linda Thomas, Alberta Government, CANADA.
Change 10.332
Many new ADOCs members were added to MXG 10.10. Some are
completed, but many are still work in progress, with new
text and discussion to be added.
Nevertheless, since all
of the "variable descriptions" have been reviewed, the
usefulness of the information justified baring my soul, as
there's clearly still a lot of writing to be done.
now have PROC PRINT and PROC MEANS examples, which I still
find to be the best tool in SAS to learn about new data.
I intend to concentrate more on writing now that 10.10 is
done and looks so robust.
Our next newsletter will keep
you informed of my progress toward the consolidation and
rewrite of both MXG books and all Newsletters, but I still
will provide all text in the MXG Source Library first, and
then will concern how much of it is put on paper!
Change 10.331
NETSPY Type "U" record sometimes produced negative value
for TRANSNO when LUFDRSEQ='.1......'B because I did not
verify that TRANSNO was non-zero before subtraction.
TRANSNO=TRANSNO-1 is executed only if both the bit is on
and TRANSNO GT 0.
Thanks to Jan-Ake Christoffersson, GotaData, SWEDEN.
Change 10.330
Variables UBRELBK and UMRELBK should have been spelled as
UBREBLK and UMREBLK, and now they are.
Change 10.329
MXG 10.10 has been tested under both SAS 6.07 & SAS 6.08,
and there are no external changes to your MXG jobs when
you migrate to SAS 6.08.
Member CONFIG07 works with 6.08.
However, there is a new CONFIG08 member in MXG 10.10, just
for consistency in naming conventions, and just in case it
turns out that it is needed when 6.08 becomes production.
Because SAS 6.08 is currently a Beta release, benchmarks
of MXG under SAS 6.08 will await the production 6.08.
Change 10.328
MXG 10.10 has been tested under SAS 5.18, but this is the
last MXG version that will completely support that archaic
Future MXG enhancements will now exploit new SAS
Version 6 features, which may cause incompatibility.
Change 10.327
CONTROL-D Release 2.0.0 is also supported by MXG as there
were no changes to their SMF record in that release.
Thanks to Brian Cobb, Credit General Industriel, FRANCE.
Change 10.326
NETSPY dataset NSPYLU average host response time AHOSTRSP
was slightly off if the number of transactions terminated
at the host (LUNRSPSS) was different than the number of
transactions input (TRANSNO), because MXG incorrectly used
TRANSNO now LUNRSPSS is used.
Thanks to Bob Hursch, Lockheed Information Technology, USA.
Change 10.325
Support for OpenEdition/MVS OMVS, section in type 30 adds
new dataset TYPE30OM, which will contain one observation
for each process segment in each type 30 record.
can be many process segments in a type 30 interval or step
termination record, and TYPE30OM will contain observations
from both step term and interval records.
In addition,
type 30 pseduo step termination records are created when
an OMVS address space is "dubbed", indicating a change of
in state of that address space.
The pseudo termination
record is identified by ABEND='OMVSEX' (because an OMVS
EX() was issued).
Each "dub" creates a separate type 30
step record, which are identified within each STEPNR by a
new sub-step number, SUBSTEP.
This support has only been
coded and syntax checked.
Change 10.324
Variable RMLFLAG2 was not kept in ASTEX dataset DMONVOL,
but now it is and it is formatted $HEX2.
Thanks to John Rosza, Depository Trust Company, USA.
====Changes thru 10.323 were printed in MXG Newsletter TWENTY-THREE====
Change 10.323
The PDB data sets listed in the Weekly and Monthly jobs
were no some were in the weekly but
not in the monthly, and TYPETMNT was copied twice in the
weekly and monthly examples.
Now, all data sets created
by the JCLPDB6 example will be copied to WEEK & MONTH.
Thanks to Barry Lampkin, Polaroid, USA.
Change 10.322
Significant progress has been made in MXG documentation,
as there are now many new ADOCxxxx members, but it's still
a long way from completion.
Most ADOCs now contain sample
PROC PRINTs and PROC MEANS, and variable definitions have
been revised, but some of the text has not been updated.
Change 10.321
This is the "all-your-data-sets-tracking-system" to keep
track of storage of all data sets, combining DCOLLECT data
(all of your online volumes as well as information on
HSM migrated datasets, HSM backups, DASD volume capacity,
HSM tape capacity, and VSAM clusters) with data from the
TMS (CA-1) product's TMC tape data set catalog.
described in member ADOCDSNS and in comments.
Thanks to Chuck Hopf, Primerica, USA.
Change 10.320
Support for OpenEdition MVS, OMVS, in RMF records. TYPE70
contains counts for OMVS address spaces (OMVS00-OMVS11 and
OMVSAVG,OMVSMAX,OMVSMIN).
TYPE71 contains six destination
counts for two new OMVS Swap Reasons, SWAPOI=OMVS Input
Wait, SWAPOO=OMVS Output Wait.
New TYPE74OM dataset from
Monitor III captures OMVS Kernel Activity: TOT/MIN/MAX for
System Calls, CPU time, Fork/Dub Fails because of either
max users, max processes, or max processes per user, count
of users, count of processes, and the defined maximum
number of users, processes, and processes per user.
Change 10.319
Very preliminary support for RS6000 AIX commands VMSTAT,
IOSTAT, and PS, with this user contribution. VMACRSCR
is the script used that adds the data/time that is not in
the command output!
Not all fields are decoded, variables
are not labeled, etc., but this is a start if you have the
need to look at AIX on your RS6000.
The next release will
enhance and document, probably rename datasets and members
and add support for the AIX accounting file as well.
Thanks to Rachel Quiroz Holt, Neiman Marcus, USA.
Thanks to Andy Rockwell, Neiman Marcus, USA.
Change 10.318
TYPE42VL variables SMF42DB1 & SMF42DB2 are now formatted
as $HEX2. so they legibly print their bit values.
Thanks to Stephen W. Sweely, NM, AUSTRALIA.
Change 10.317
The GMT Offset, GMTOFFTM, is now available in RMF records
under MVS/ESA 4.3, if Global Synchronization is enabled.
By comparing SYNCTIME with ENDTIME and using fuzzy logic,
MXG now creates the RETAINed variable GMTOFFTM from the
type 70 record, that may be useful in converting other SMF
records that contain GMT instead of local.
This work is
not complete, since it only protects records written after
the first type 70 is found in your SMF file.
I intend to
enhance the SPIN logic in BUILDPDB to keep the GMTOFFTM
from each SYSTEM to protect those early records!
Change 10.316
MXG formats contain the data value, a colon, and the data
description, but for some report users (notably auditors)
the data value and colon confused them.
This utility will
create an alternative format library for reports that has
removed the data value and colon.
You can then point the
//LIBRARY DD in your report programs to the alternative
format library, or use SAS's FMTSEARCH option in reports.
Thanks to Joseph J. Faska, Depository Trust, USA
Change 10.315
TCP/IP allows for two different SMF record IDs for TELNET
and FTP, but some sites assigned only one record ID. This
is now supported, as MXG reads inside the record to decide
which dataset is to be output.
See also Change 10.256.
Thanks to Kurt Karlsen, NIT.
Change 10.314
MXG 10.1+ only, for JES3 BUILDPD3, "WORK.TAPEMNTS.DATA"
error message results because the _VARTMNT and _CDETMNT
macro invocations were not in BUIL3606.
Now they are!
Thanks to Hanno Bresch, SAS Institute, GERMANY.
Change 10.313
Variable ZDATE was not in the KEEP= list for TYPETAO data
set, but it is now!
Thanks to Sharon O'Daniel, Blue Cross Blue Shield of Kentucky, USA.
Change 10.312
The paper "An RMF Bigots View of Measuring UNIX Systems,
or how i learned to type in lower case",
presented at
CMG and SHARE by Chuck Hopf, is now contained in ADOCHPCS.
Change 10.311
This is a preliminary change created for initial testing.
BUILDPDB was split into six members:
BUILD001 - Reads SMF and creates all WORK data sets,
CICSTRAN.CICSTRAN, DB2ACCT.DB2ACCT and the
PDB.DB2STATn data sets.
BUILD002 - SORT some WORK datasets into PDB library.
BUILD003 - SORT RMF datasets into PDB and then build
PDB.RMFINTRV dataset.
BUILD004 - Combine CICS Statistics datasets and create
four PDB.CICxxxRV datasets.
BUILD005 - (For JES2).
Sort TYPE30xx, TYPE6, TYPE26J2, interleave
with SPIN library, create PDB.JOBS,PDB.STEPS
PDB.JOBS, update SPIN library, copy SPIN
datasets into PDB (for backup), and create
PDB.SPUNJOBS.
BUILD006 - (For JES3).
Sort TYPE30xx, TYPE6, TYPE26J3, interleave
with SPIN library, create PDB.JOBS,PDB.STEPS
PDB.JOBS, update SPIN library, copy SPIN
datasets into PDB (for backup), and create
PDB.SPUNJOBS.
This may permit improved run time of the BUILDPDB process,
because once BUILD001 has run, the remaining four phases
may be executable in parallel.
However, there will be JCL
constraints, and SAS/SHARE may be required for concurrent
update from parallel steps,
and there may be additional
design changes before this becomes a recommended process.
Thanks to Dan Squillace, SAS Institute Cary, USA.
Change 10.310
For interval observations most MXG datasets have STARTIME
and DURATM variables for the interval start and duration,
but in some datasets STARTIME does not exist or it has a
different name, and similarly for DURATM.
It is now my
intention that STARTIME and DURATM variables will exist
consistently in all MXG interval data sets, by creating
them where necessary (and without changing existing names
of their counterparts, so your reports won't break).
members listed in this Change have all had either STARTIME
or DURATM or both added to their interval data sets,
except for TYPE39FF (NETMASTER), which does not contain
the DURATM and hence STARTIME cannot be determined.
me know if you find others that should be updated.
Thanks to Dan Squillace, SAS Institute Cary, USA.
Change 10.309
Very archaic EPILOG 451 code missed three undocumented
after BIODISP
PIB1. to correct the
Feb 28, 1993
BIO..... variables after BIODISP.
Thanks to Chris Spikings, Deutsche Bank AG, ENGLAND.
=Changes thru 10.304 were included in MXG PreRelease 10.6, Feb 23, 1993=
Change 10.308
OPC data apparently can be dumped in different formats.
If "OPC" starts in the 1st byte of the logical record, MXG
Feb 25, 1993
default is valid, but if "OPC" starts in the 4th byte of
the record, you must change to OFFSMF=-3 to OFFSMF=0 in
DATA;INFILE OPCLOG;INPUT;LIST;STOP: to
print the first record to find the location of "OPC".
Thanks to Fulvio Robbiani, Banca Commerciale Italiana, ITALY.
Change 10.307
MXG no longer sets ABEND=NOTP in PDB.JOBS & PDB.SPUNJOBS
because it was overlaying the ABEND value from the job
termination record.
This will help in counting job-level
events, but for analysis of CONDCODE within ABEND, you
Feb 24, 1993
must use the PDB.STEPS data (CONDCODE in PDB.JOBS is wrong
if a flushed step followed the abending step).
Thanks to Steve Talley, Department of the Army, USA.
Change 10.306
Type 0 SMF record processing now checks record length and
deletes invalid records, after putting a message on the
Feb 24, 1993
Occasionally, SMF records are created with the
record ID of 0, due to coding errors, but they looked like
IPL events.
If you detect bad records, and know what the
true ID is, you can convert the bad record ID in member
IMACFILE, using
IF ID=0 AND LENGTH GT 31 THEN ID=42;
if the bad record to be converted was actually a type 42.
Change 10.305
DCOLLECT has been enhanced in DFP 3.3 by APARS OY59795 &
OY60048 with nine new datasets describing SMS constructs
and control information.
Even more significant, DFSMS 1.1
adds long-needed VSAM statistics (including space used!).
Two existing datasets are enhanced with new variables:
DCOLCLUS (VSAM Data Set Information)
='BYTES OF*FREESPACE*IN DATA SET'
='CONTROL*AREA*SPLITS'
='CONTROL*INTERVAL*SPLITS'
='DELETED*RECORDS'
DCAHARBA='HIGH ALLOCATED*RELATIVE BYTE*ADDRESS'
Feb 24, 1993
DCAHURBA='HIGH USED*RELATIVE BYTE*ADDRESS'
='INSERTED*RECORDS'
='KEY*LENGTH*
='LOGICAL*RECORDS'
='RELATIVE*KEY*POSITION'
='RETRIEVED*RECORDS'
='UPDATED*RECORDS'
DCAVRRDS='VARIABLE LENGTH*REL RECORD*DATA SET?'
DCOLDSET (Active Data Set Information) new variables:
DCDALLFG='ALLOCATED*SPACE*RETURNED?'/
DCDNMBFG='UNUSABLESPACE*RETURNED?'
DCDPDSEX='POSIX*FILE SYSTEM*FILE'
DCDSECFG='SECONDARY*SPACE*RETURNED?'
DCDSTRP ='STRIPED*DATA*SET'
DCDUSEFG='USED*SPACE*RETURNED?'
Additionally, if the DCOLLECT option SMSDATA is specified,
these nine new MXG datasets will have observations that
describe your SMS environment:
- Aggregate Group Information
- Base Configuration Information
- Data Class Construct Information
- OAM Optical Drive Record Information
- OAM Optical Library Record Information
- Management Class Construct Information
- Storage Class Construct Information
- Storage Group Construct Information
- Storage Group Volume Information
These nine new MXG datasets have been syntax checked, but
no test data has yet with 277 new
variables, I'll be surprised if it's perfect!
Change 10.304
Unexpected non-packed decimal field caused IMS log reads
program to ABEND with 0C7. After the BZ READIN02 that is
Feb 23, 1993
after the label READINPQ, insert this instruction:
OI ARRVDATE+3,X'0F'
to ensure the field is in packed decimal format.
Thanks to Jeffrey S. Crum, Ashland Oil, USA.
Change 10.303
TYPE1415 variable DSORG can be "PS" when really is "PO"
and MEMBER can be blank because the IBM record is wrong.
Feb 23, 1993
If PDSs with member name specified are concatenated, the
first type 14 has DSORG='PO' and correct MEMBER name, but
the 2nd and subsequent type 14 records had DSORG="PS", and
MEMBER was blank.
The DSORG was wrong because both the
JFCBORG and DCBDSORG are '40'X (PS) in the concatenation
records, instead of '02'X (PO) as is in the first record.
MEMBER is blank because MXG INPUTed it only for DSORG=PO
(the location of MEMBER contains RELGDG if it is not a PDS
and is a GDG!).
Why are JFCBORG and DCBDSORG both "PS"
for a PDS?
Because when the member name exists in the
JCL, OPEN treats the data set as sequential, even though
the true DSORG (in the VTOC) is still "PO"!
will take some time to address this situation, MXG has
circumvented the problem (hopefully):
If MEMBER starts
with + or -, it must be a RELGDG and MEMBER is blanked.
Otherwise, if MEMBER is non-blank, it must be a PDS, and
so MEMBER is valid and DSORG if forced to "PO".
Thanks to Herbert G. Strozinsky, Burlington Northern Railroad, USA.
Change 10.302
OPC/A data records are created as RECFM=U but test data I
received had been copied to RECFM=VBS, misleading me to
Feb 23, 1993
assume that RECFM=VBS had to be specified in macro _SMFOPC
defined in VMACOPC. The RECFM=VBS parameter is now removed
from VMACOPC, so MXG will read either VBS or U data, using
the RECFM in the data set label.
Change 10.301
This new report macro replicates IBM's RMF reports from
MXG's TYPE70xx thru TYPE78xx datasets.
In addition to
Feb 22, 1993
producing reports, the source code can be read to find out
which MXG variables are used for RMF report values.
support includes all RMF reports except Channel and Trace,
(which will be added when there is a groundswell of user
requests, or when we feel like it, whichever comes first!)
The report syntax is self-defined in this member.
Change 10.300
Support for Empact's HiperCache product's SMF record adds
two new dataset:
HIPRSAM - Hipercache SAM data set activity
HIPRVSAM- Hipercache VSAM data set activity
thanks for this significant user contribution.
Feb 22, 1993
Thanks to David Childress, Lowe's Companies, Inc, USA.
Change 10.299
RMFINTRV enhancements have added SIO75CNT (Paging SSCHs),
SIO74TAP (SIOs to tape devices), and TSO2-TSO4 variables
Feb 22, 1993
SWAP,TRAN,RESP for 2nd thru 4th period TSO counts and
response time. In addition, these swap counts:
and page movement rates:
HIPMIGRS HIPREADS HIPWRITS PGMIEXAU PGMVTOEX PWSSMIIN
were added to RMFINTRV from the TYPE71 dataset.
Thanks to Tom Parker, Hogan Systems, USA.
Thanks to Chuck Hopf, Primerica, USA.
Change 10.298
PDB.PRINT dataset now contains new variable TOTLINES, the
sum of PRINTLNE, PUNCHCRD, EXTWTRLN, for sites that still
have impact printers.
Note that TOTLINES is the number of
Feb 22, 1993
print line images if JES2 or PSF prints line-mode data,
but if PSF prints PSF-mode data, it counts print records,
and a print record can be a single print line or it could
be a multi-page graph. Because of this, variable SHEETPRN
the actual number of sheets of paper printed, should be
used, with TOTLINES only used for impact printers under
See member ACHAP31 for discussion of print charging.
Change 10.297
Support for optional HOGAN application variables was
updated to add new variables FPSSCRN, TCTPLD, TCBFUNC,
PLDVERS, and correct variables FPSOPTN and FPSTYPCD, and
Feb 22, 1993
the new variables were added to CICSTRAN KEEP= list (but,
like all the optional variables in CICSTRAN, they will not
exist unless the optional code is enabled in IMACICUS).
Thanks to Tom Parker, Hogan Systems, USA.
Change 10.296
DB2 Reports. If PMIOS05=YES was requested with PDB=SMF,
and PDBOUT= was not specified, ERROR "LIBREF SMF IS NOT IN
Feb 21, 1993
A VALID FORMAT" resulted.
ANALDBTR should have replaced
the earlier "paring" macros, which were the source of the
real error. Replacing the "paring" with %ANALDBTR invoked
for those pairs eliminated the error.
Specifying PDBOUT=
circumvented the error.
The PMACC02=YES accounting detail
in the accounting detail report and the values reported as
averages in the Buffer Pool Summary were reported
incorrectly.
In addition, a 'Total Average' column was
added to be consistent with DB2PM.
Change 10.295
The variables created to identify why a plan had ended
were created but not kept because they were not in the
Feb 21, 1993
SUM= list.
Change 10.294
Support for HP's PCS data from HP/UX is extended to now
read MPE data (HP's older, proprietary operating system).
Some minor logic bugs were also corrected.
Macro HPCSDLM
was added to member IMACHPCS to identify the character(s)
that are to be used as field delimiters when the PCS data
was created, since the delimiter is a part of the data
Feb 21, 1993
collection command.
Member ADOCHPCS now contains the
specific SCOPE commands that was used to create the data
that MXG TYPEHPCS support expects.
In addition, that same
ADOCHPCS member contains Chuck Hopf's fine paper on UNIX
resource measurement, "An RMF Bigots View of Measuring
UNIX Systems, or how i learned to type in lower case".
Thanks to Doug McBride, Hewlett-Packard, USA.
for patience with the untutored in this particular world of DP, and
for the data and manuals that made this enhancement to MXG possible.
Change 10.293
Support for Boole & Babbage CMF User SMF record subtypes
expanded to support esse the complete
status for each subtype is listed in comments at the start
of member VMACCMF.
Most of this enhancement is based on
the sample SAS code distributed with CMF, so that names of
variables and datasets are the same, but their sample code
was architecturally revised and edited into the MXG style.
With this enhancement, these datasets are now created,
and all have been tested with real data records, too!
Description (Dataset Label)
CMF 00 DEV
CMF 00 DOM
CMF 00 IPS
CMF 00 OBJ
CMF 00 SRM
CMF 00 TCC
CMF 00 TPG
Feb 21, 1993
CMF 00 TRT
CPU QUEUE COUNTS
CPU AND CHANNEL SAMPLE DATA
ASM DATA (PAGE/SWAP DATASETS)
PAGING DATA (SRM SAMPING)
WORKLOAD DATA (DOMAIN SAMPLING)
DASD DEVICE DATA
TAPE DEVICE DATA
JES SPOOL ACTIVITY
JES CLASS ACTIVITY
I/O WORKLOAD TRACE
TSO COMMAND SUMMARY
TSO COMMAND DETAILS
TSO USER RESOURCES
CMF 23 PG0V
CMF 23 PRIOS
CACHE SAMPLING MODEL 3990-3
CACHE SAMPLING MODEL 3880
CACHE SAMPLING CSD
COMMON STORAGE COS
COMMON STORAGE CJS
COMMON STORAGE CDS
Change 10.292
Support for IMF Release 2.8 uncovered MXG corrections:
Dataset CIMSTRAN variable INPQUETM was wrong for fastpath,
Feb 20, 1993
and COREALOC is actually "Storage Available", so its label
was changed.
The IMF Release itself added these changes:
Dataset CIMSTRAN:
New variable UOWTIME is now created from existing
variable ALPCBTRN.
For DBCTL, ALPCBTRN is the IMS
Transaction's Unit of Recovery, the same as the CICS
Unit of Work ID, UOWID.
MXG converts the first six
bytes of ALPCBTRN into UOWTIME, the 6-byte part of
UOWID that is the constant token across all records for
the same transaction, and the token that is used to
match IMS events to their CICS and/or DB2 counterparts.
UOWTIME is always created, but is only valid when
ALPCBTRS contains a UOR.
The second field CICS/DB2
field used to match transaction, NETSNAME, the name of
the originating network on which UOWTIME was created,
is not yet in the IMF transaction record.
Variable FLGSPECL now contains Q for Quick Reschedule.
New variables TRNSKW and TRNSNKW count the SYNC buffer
flush writes (Key-Writes and NonKey-Writes).
New variable APPCIMS flags APPC/IMS transactions.
Dataset CIMSDBDS:
Two new counts:
DBTDDNNO='DDN*DBTNO'
DBTSECNO='SEC*DBTNO*(OVERFLOW)'
and seven new flag (status) variables:
DBTMSCNT='DBT CNTRS*OVERFLOWED?'
DBTOSSB ='OSAM*SB IN*EFFECT?'
DBTOVFLW='DBT*OVERFLOW*OCCURRED?'
DBTTYDDN='I AM A*DDNAME*DBT?'
DBTTYOTH='I AM A*CATCH-ALL*DBT?'
DBTTYSEC='I AM A*SECONDARY*DBT?'
DBTVSAM ='VSAM*ACCESS*METHOD?'
Fortunately for everyone, the new fields used existing
reserved fields, so the changes were compatible.
Change 10.291
Support for Oracle 6.0.33.1.51 added two READTIME and JOB
and ACCOUNTn fields, and two additional CPU time measures.
Feb 20, 1993
CPUCICTM is the CICS subtask CPU time (now added to CPUTM
as it was not previously captured).
CPUXMETM is the CPU
time spent in cross memory mode in the ORACLE address
space, but as this is already captured in CPUTCBTM or
CPUSRBTM, it is not added to CPUTM; CPUXMETM lets you see
how much of CPUTM was spent in the ORACLE ASID.
a new section for SQLNET data, but the contributor site
did not have documentation nor data for that option.
USER fi see comments in VMACORAC on
how to keep the USER field if it exists in your data.
Thanks to Martyn A. Jones, Data Sciences UK
Change 10.290
This significant user contribution matches SLR-IMS log
processing - it keeps only a subset of the statistics that
Feb 19, 1993
MXG's new ASMIMSLG produces and it uses the output of IBMs
DBFULTA0 as input for Fast Past processing, which greatly
reduced the elapsed processing time.
This contribution is
documented in the author's letter at the beginning of the
member, which is actually the JCL to build a PDS with the
several members of this IMS log processing alternative.
Thanks to George Denissof, Savings Bank Services Ltd, Espoo, FINLAND.
Change 10.289
To bill tape datasets using TMS dataset DSNBRECD is built
for the first dataset on the volume by OUTPUTing the info
from the volume record, but if the first dataset on the
Feb 19, 1993
volume was SCRatched or DELeted in the catalog, MXG still
output to DSNBRECD, causing a billing charge for a "dead"
Now, the observation is OUTPUT only if the dataset
is neither scratch nor deleted.
Thanks to Chuck Hopf, Primerica, USA.
Change 10.288
Service time could still be zero, because the reset logic
had not been moved into TYPEIMSA from TYPEIMS.
Feb 19, 1993
TYPEIMSA from STRTTIME=GUTIME; thru OUTQUETM=OGUTIME...
were deleted and replaced by TYPEIMS lines from
/* TEST FOR MISSING
thru RESPNSTM=ENDTIME-ARRVTIME;.
Thanks to Lonnie T. Rimmer, Philip Morris, USA.
Change 10.287
Format $MGAMDDT is no longer used (it was for an earlier
version of Amdahl's SPMS), and has been removed.
Feb 19, 1993
Thanks to Adrian Reynolds, SAS Institute, ENGLAND.
Change 10.286
MXG 10.5 only. Variable AVGMTPTM, the average mount time
per TAPEMNTS (new in ESA 4.3) was incorrect.
Feb 19, 1993
the duration when a mount was pending is added to TYPE74.
Change 10.285
Support for IBM 3495 Tape Library Dataserver Statistics
SMF type 94 record is added, providing hourly statistics
(min/max/avg counts/durations) of drives mounted, mount
requests pending, demounts, ejects, audit requests, and
the number of insert stores.
Feb 18, 1993
Change 10.284
Amdahl MDF creates TYPE70PR observations with LPARNUM=0,
while the first LPAR in IBM's PRSM or Hitachi MLPF is=1.
Feb 18, 1993
ASUM70PR will produce an error message "MORE THAN 16 LPAR"
when it encountered the unexpected LPARNUM=0.
summary member supports 17 LPARs, numbered 0 thru 16!
Thanks to Jeff McFadyen, Ministry of Correctional Services, CANADA.
Change 10.283
Some fields (notably R791TCPU) are accumulated in type 79
records created by RMF Monitor II.
However, it appears it
Feb 17, 1993
is not possible to deaccumulate the data.
Using the sort
BY SYSTEM R79SES R791ASID R791JBN STARTIME does
correctly sequence the TYPE791 dataset, but MVS/ESA 4.2.2
data contains adjacent intervals in which R791TCPU drops
rather than increases.
I assume these are either step
transitions or reuse of the same ASID by the same Job in
which the CPU clock is reset, but there is no indicator of
STEPNR or JESNR in the record by which the reset can be
recognized.
Furthermore, even when two intervals happen
to show an increase, it is possible that the CPU clock was
reset, but the CPU time in the second interval just
h in this case, if the values were
deaccumulated, the wrong CPU time would have been created.
In addition, the TYPE791 data contains accumulated counts
for page activity when the task is swapped in, but those
counts are zeros in the next record if the task is swapped
out, requiring additional investigations in the absence of
logic description from IBM as to when this occurs.
safe algorithm for deaccumulation is not possible until
IBM enhances the record and describes when fields are
zeroed and when they are not!
Thanks to Khalid Al-Harthi, Saudi Arabian Airlines, SAUDI ARABIA.
Change 10.282
This suite of RACF reports was made more user friendly by
removing references to &DAYNUM, and providing specific
Feb 17, 1993
example of how to set &START and &END in JCLRACFR.
occurrences of RACFTERM $6. were changed to $8. MXG Format
MG080TY was updated with new types.
PROC DATASETS were
added to delete unused work data sets, freeing DASD.
new members now exist:
JCLRACFR executes ANALRACF
programs, and JCLPRINT prints reports created by ANALRACF.
The internal members in ANALRACF that were altered are:
JCLRACFR JCLPRINT MXGDAY1
REPRACFB REPRACF2
REPRACF3 REPRACF4 WPDBRACF
While ANALRACF provides a lot of reports, the new TYPE80A
dataset may prove to be a better source of reporting. Much
of the logic in ANALRACF was required because MXG split
the type 80 record into multiple observations. The TYPE80A
member creates one observation per type 80 into several
datasets for improved access and reporting.
Try it first!
Thanks to George Waselus, State of Arizona, Department of Admin, USA.
Change 10.281
DB2 Trace IFCID 0044 Lock fields were input incorrectly.
Feb 17, 1993
Thanks to Jason Lau, AMP Society, AUSTRALIA.
Change 10.280
The 4th TCB (Secondary LU) CPU time was not summed into
CPUTCBTM in dataset CICDS, and thus it was also not in the
Feb 15, 1993
CICEODRV, CICINTRV, CICREQRV or CICUSSRV datasets.
Change 10.279
Believe it or not, there is still SMF data from VS1 being
created, and its type 5 record caused MXG to fail because
I assumed the MVS/370 service unit fields were present in
the record.
Now their input is conditional!
Thanks to Don Mosley, Farmland Industries, USA.
Change 10.278
OMEGAMON/CICS V550 PTF QOC0109-DATACOM SPE- adds 16 bytes
to their BSC segment in the type 110 record for both CICS
Version 2 and CICS/ESA.
This will corrupt the data in the
other OMEGAMON segments, as well as any user data segments
your installation might have added.
And, of course, there
is no way to detect whether or not you have installed this
PTF by examining the type 110 record!
As a result, you
will need to update member IMACPTF to enable _QOC0109 to
tell MXG when you have installed this OMEGAMON PTF.
9 of Newsletter TWENTY-TWO discussed how to enable the
MXG Support for OMEGAMON V550.)
Thanks to Carol Harper, EG&G Idaho, USA.
Change 10.277
DCOLLECT does not capture VSAM space used. IBM Appendix E
of the MVS/DFP Access Method Services For ICF documents
that DCDUSESP is not 'valid' for VSAM datasets.
ASMVVDS/TYPEVVDS processing, which reads the VVDSs, does
capture space allocate and space used.
However, under
user pressure, IBM has announced, in ETR Item E
that DFSMS Release 1.1 (March, 1993) will add a field to
the "A" record with space used value.
Note: Change 10.305 added the new fields to "A" record,
which is output to DCOLCLUS see ADOCDCOL.
Thanks to Frank Vessell, ITT Consumer Financial Corporation, USA.
Change 10.276
Support for STOPX37 Release 3.5 added a number of new
variables to the STOPX37 dataset.
This support has not
yet been tested with actual 3.4 data records.
Change 10.275
MXG 10.4-10.5. STOPOVER resulted because line 031500
should be SKIP=SKIP-8; instead of SKIP=LENCHDS-8;.
that line 030800 still must be SKIP=LENCHDS-8;).
Thanks to Jim Nissen, Principal Financial Group, USA.
Change 10.274
Support for Empact's POOL-DASD user SMF record, written
whenever POOL-DASD manages an allocation.
The text of the
WTO messages associated with the allocation override by
POOL-DASD describes what action was taken.
Change 10.273
Support for Candle's IMS Transaction Reporting Facility,
ITRF, is added.
MXG reads the output file created by the
ITRF Batch Summary program to create these MXG datasets:
- Message records
- Message Out records
- Database Records (DL1 and Fastpath)
- Summary Records (DL1 and Fastpath)
- Summary Records (DB2)
ITRF is a new part of Omegamon II for IMS.
Its online
component creates an IMS log record (default ID=160) that
captures response time, CPU time, virt