***********************NEWSLETTER SIXTY-SEVEN***************************
MXG NEWSLETTER NUMBER SIXTY-SEVEN OCT 7, 2016.
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,2016 MERRILL CONSULTANTS DALLAS TEXAS USA
I. The 2016 Annual Version MXG 33.33 was dated Jan 18, 2016.
Current Version MXG 34.07 is dated Oct 7, 2016.
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. Text:
III. MVS, a/k/a z/OS, Technical Notes.
6. APAR OA50393 corrects RMF Type 78 data that can have incorrect
CHIPDs in the Channel Path detail when CHPIDs are taken offline.
5. APAR OA50395 corrects the value in SMF 70 MXG variable SMF70MTTT the
SMT Mode Multithreading Idle Time, which was previously accumulated
but now contains the correct interval value. Note that the correct
variable name SHOULD have been SMF70MTIT, and that name is in the
label for SMF70MTTT.
4. z/OS 2.2 APAR PI69487 corrects the excessive response time for TSO
reported in RMF TYPE72GO elapsed time because each SDSF session's
elapsed time was included in the elapsed time of completed TSO
transactions.
3. RMF Type 74 subtypes went from 1-6,8 to only 1, 5, 8, when RMF III
Monitor was not started on that system.
2. Increased CPU Time in JES2 address space (two to three times) when
migrating from z/OS 2.1 to z/OS 2.2 was eliminated by APAR OA50777,
a two part fix that also requires RSM APAR OA50806.
1. New JES JOB Correlator field, SMF30COR and SMF26JCR are each 64-byte
tokens that are unique for each job, and currently contain printable
text J0029999 SYSPLEXA CF41F7ED .......: (JCTJOBID, SYSPLEX, token)
in the first 32 bytes, and blanks in the last 32 bytes (which can be
populated with local information).
The fields are populated for Jobs and TSO sessions and full function
STCs, but all OMVS type 30 records type 30s for these JOB/STCs that
start prior to JES startup finish, known as "Early Address Spaces"
or "Early ASIDs", will all contain hex zeros in all 64 bytes.
APPC ASCH AUTAM92A AUTAM92B AUTO92S BLSJPRMI CAS9 CSAA HSAPIPLC
HZR IFGEDI INIT JES2 LLA MIA MIMASC MIMEDI RESOLVER RRS SOFTAUDT
TFS TSS VLF ALLOCAS CAMASTER CONSOLE EYUX420 GRS IEFSCHEAS
JES2AUX PCAUTH RACFDS RASP SMSPDSE SMSPDSE TRACE
It's VERY unclear of the use since the total length of 64 bytes is
more than double the 24 bytes need for READTIME JOB JESNR which
have always uniquely identified all records from a job, and those
fields are in many more SMF records than just the 26 and 32.
IV. DB2 Technical Notes.
1. Text
V. IMS Technical Notes.
1. Text
VI. SAS Technical Notes.
1. SAS 9.4 datasets can NOT be read with SAS 9.2 or earlier SAS if the
9.4 default option EXTENDOBSCOUNTER=YES (alias EOC=YES) was used.
This INCOMPATIBILITY is documented in SAS Note 49496, with message:
ERROR: FILE xxx not compatible with this SAS version.
on the log, BUT THE RETURN CODE IS ZERO.
The SAS Note 49496 lists these possible circumventions
Reading (a 9.4 dataset created with EOC=YES default) with SAS 9.2
or earlier:
-In order to read this data set with SAS 9.2 or earlier, you must
do one of the following (both also require 9.3 or 9.4):
-Using SAS 9.3, do one of the following:
-Re-create the data set with the data set option EOC=NO, as shown
on the Full Code tab above.
-Create a transport file using PROC CPORT and then, in SAS 9.2,
use PROC CIMPORT to read it.
-Using SAS 9.4, do one of the following:
-Re-create the data set with the SAS system option
EXTENDOBSCOUNTER=NO or its alias EOC=NO.
-Create a transport file using PROC CPORT and then, in SAS 9.2,
use PROC CIMPORT to read it.
Creating a 2,500,000,000 observation data with EOC=NO resulted with
these observed impacts:
-SAS log creating the dataset has WORK.DATA1 HAS . OBSERVATIONS.
-PROC CONTENTS shows OBSERVATIONS . on the top line; details are
PAGES=107,332, MAX OBS Per Page=20963, 1st Page obs=20625
which produces count of 107331*20963+20625=2,250,000,373.
-PROC MEANS shows 2,500,000,000 observations
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 33.11 (since MXG 32.32):
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.