COPYRIGHT (C) 1984-2021 MERRILL CONSULTANTS DALLAS TEXAS USA
MXG NEWSLETTER SIXTY-SIX
***********************NEWSLETTER SIXTY-SIX****************************
MXG NEWSLETTER NUMBER SIXTY-SIX - DATED AUG 17, 2015.
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,2015 MERRILL CONSULTANTS DALLAS TEXAS USA
I. The 2016 Annual Version MXG 33.33 was dated Jan 16, 2016.
The Current MXG Version MXG 34.01 is dated Feb 16, 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.
5. APAR OA49128 FIN (Fixed In Next z/OS) will correct the date value in
variable SMF92CTO in SMF 92 subtype 11; that same field is also used
in the IPCS OMVSDATA FILE report and both will show an incorrect
birthdate for FIFO files (possibly LE owned). Error is in z/OS 2.2.
4. Review of Arney Computer Systems Trap Diagnostic Facility, TDF.
Assembler language developers working with System z 64-bit
architecture soon discover that the traditional TSO TEST command is
inadequate for their needs. TSO Test only displays the last 32
bits of General Purpose Registers and has an antique command line
interface where prior displayed results soon roll off the screen.
Trap Diagnostic Facility (TDF) from Arney Computer Systems provides
a modern tool that leverages the power of the ISPF full screen
interface to make modern code debugging a productive and satisfying
experience.
All General Purposes Registers are shown on an ISPF panel without
having to request them. When in Instruction Step mode registers
are color coded so that changed registers are immediately apparent.
Prior storage displays are not lost and can be scrolled to review.
Breakpoints can be set to trip for a single occurrence or for every
occurrence.
Some of the tasks that can be accomplished using the User Interface
are:
- Define the programs to be debugged
- Display and alter storage, registers and PSW
- Interactively trace execution at the instruction level
- Set breakpoints and triggers to stop execution at desired points
- Review the output of previous commands in the response history
- Manage Session recording and replay
- Define and initiate non-interactive traces
TDF installs quickly using a simple TSO RECEIVE script to set up
the ISPF libraries and load library. Because TDF uses z
Architecture TRAP instructions an Authorized Program Facility (APF)
library is required for the load modules. TDF has a Started Task
for the Server task. A TSO Clist invokes the TDF ISPF interface
and then only a minor change to the JCL EXEC statement for the
program to be tested is needed.
This product is definitely worth evaluating for installations that
rely on development or enhancement of assembler programs for their
business needs.
Arney Computer Systems
info@arneycomputer.com
3. Pointing //LIBRARY to a PDS-E dataset instead of sequential caused:
ERROR: OPEN TYPE=J FAILED TO POSITION LIBRARY DATA SET
MXG.PROD.SOURCE.FORMATS TO VOLUME NUMBER 1.
2. TYPE70PR data can be wrong due to errors in IBM DIAG 204 instruction
that were fixed with "Driver 15 - MCL H49560.003 or Driver 12 -
MCL H09168.004." The defect caused segments for some LCPUADDR to NOT
be written, causing not only wrong engine counts, but the counts
were reversed in different system's TYPE70PR data. LPAR A reported
LPARs B and C had 1 and 2 CP engines, but LPAR B reported LPAR B and
C had 2 and 1 CP engines. Incorrect values were shown in RMF CPU
Partition Data Report.
1. The IEF032I Step Termination Message has many fields that are in the
SMF 30 records. I've typed the MXG Variable name in lower case:
IEF032I STEP/GO /STOP 2015050.0845
stepname endtime
CPU: 0 HR 12 MIN 04.94 SEC SRB: 0 HR 00 MIN 09.61 SEC
cputcbtm cpusrbtm
VIRT: 8580K SYS: 404K EXT: 5152K SYS: 11460K
usrszlow pvtszhi usrsizhi pvtszlow??
pvtszalow 10216K regreqst 8592K (IEFUSI caps at 8400+192K)
IV. DB2 Technical Notes.
1. Text
V. IMS Technical Notes.
1. IMS 13 APAR PI42904 now populates the IMS 56FA log record variable
TRANSACT with the value of the inputted CCTL/ODBA transaction ID or
Job ID, which was not populated when TLS was active.
VI. SAS Technical Notes.
2. Starting in SAS V9.2, the XPORT engine no longer supported the
TRANSCODE attribute, which protects character variables that
contain HEX values from being translated when moved between EBCDIC
and ASCII platforms (both ways). MXG assigns the TRANSCODE attribute
to all $HEX. formatted variables. The XPORT engine also does not
support long variable names nor long dataset names.
Using the XPORT engine with PROC COPY generated these error
messages executing under SAS 9.4:
NOTE: Copying PDB.TYPE70 to XPORT.TYPE70 (memtype=DATA).
WARNING: TRANSCODE suppression is not supported by the XPORT
engine. All the character variables will be added
without the transcode suppression to the dataset
ERROR: The variable name SMF70CPA_RATIO is illegal for the
version 6 file XPORT.TYPE70.DATA.
NOTE: Set the VALIDVARNAME=V6 option to enable automatic
truncation of long variable names.
ERROR: File XPORT.TYPE70.DATA has not been saved because copy
could not be completed.
You MUST use PROC CPORT/CIMPORT instead of the XPORT engine if the
MXG dataset has variables with the TRANSCODE=NOTRAN attribute, or
has variables with names greater than 8 characters, now common in
MXG datasets. All examples that referenced XPORT engine will be
replaced.
1. ASCII SAS does not accept slanted quotes, '60'x, instead expecting
the vertical quote, '27'x. However, when I emailed code with the
vertical quote, in an HTML-format email, the vertical quote was
changed to a slanted quote, and the program failed with:
DATA; X='A'; IF X=`A` THEN PUT ' MATCHED '; RUN;
-
390
76
ERROR 390-185: Expecting an relational or arithmetic operator.
And, in the actual log, on Windows, those slanted quotes were NOT
displayed by SAS 9.4 - they appeared to be vertical quotes in the
log window!
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.