COPYRIGHT (C) 1984-2018 MERRILL CONSULTANTS DALLAS TEXAS USA

MXG NEWSLETTER SIXTY-THREE

***********************NEWSLETTER SIXTY-THREE***************************
                                                                        
                                                                        
                                                                        
          MXG NEWSLETTER NUMBER SIXTY-THREE  Feb 26, 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.02 is dated Feb 26, 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.   
                                                                        
    See CHANGES member of MXG Source, or http://www.mxg.com/changes.    
                                                                        
II.  MXG Technical Notes                                                
                                                                        
 1. FORMAT NOT FOUND errors usually occur when the LIBREF/DD LIBRARY    
    (the MXG.FORMATS catalog) was not updated (with FORMATS step in the 
    JCLINSTL), or if the REGION= virtual memory size is insufficient.   
    An additional source was found when ISPF 3.3 was used to copy a fine
    FORMAT library on LPAR into an existing dataset that had LRECL=4096.
    Rebuilding the dataset letting SAS set the DCB attributes eliminated
    these errors.                                                       
                                                                        
III. MVS, a/k/a z/OS, Technical Notes.                                  
                                                                        
 5. APAR OA41968                                                        
    "High Paging with Large Frames NOT being broken down to 4K frames", 
    introduces the new parmlib value of INCLUDE1MAFC of the existing    
    IEASYSxx LFAREA parmlib parameter to Specify that the 1 MB pages are
    to be included in the available frame count (RCEAFC):  APAR text:   
      By installing this PTF and specifying this new parameter value,   
      system behavior will change in the following manner:              
      - RSM will perform less paging when there is an abundance of      
        available fixed 1M pages in the system.                         
      - RSM is more likely to break up fixed 1M pages to satisfy 4K page
        demand.  Although RSM attempts to coalesce broken up fixed 1M   
        pages when there is fixed 1M page demand, there is no guarantee 
        that coalescing will be successful, especially if one of the 4K 
        frames making up the fixed 1M page is fixed long term.          
    APAR OA42066 is also required for this enhancement/fix.             
                                                                        
 4. APAR PI07971 for IBM/Sterling Connect-Direct 5.1 revises their zIIP 
    engine use for handling compressed data to first check a threshold  
    value before invoking zIIP processors and SRB mode.  This will      
    reduce the overhead that resulted when small record sizes were being
    compressed.                                                         
                                                                        
 3. JES2 APAR OA41698 revises sending of ENF 58 and 70 (Notifications of
    a job end event), previously sent to all members of the SYSPLEX but 
    with this APAR, send only to the members of this JESPLEX.  The ENF  
    processing on non-JESPLEX members was observed to consume/waste CPU 
    time on those systems.  Option ENFSCOPE=SYSPLEX/JESPLEX enables.    
                                                                        
 2. APAR PI07940 reports SMF ID=119 Subtype=70 variables FSDRIP FSDLIP  
    FSDRPort FSDLPort FSDConnID can be incorrect in the Rename and      
    Delete command's records, where they should not be populated as     
    there is no data connection, but the values from a prior connection 
    were being incorrectly output.  Now they are zero in those records. 
                                                                        
 1. SMF 30 DD segments can be not-written with EMPTYEXCPSEC or S99DASUP.
     See Newsletter FIFTY-FOUR, MVS Technical Note 1. "APAR OA29582" for
     the original discussion of EMPTYEXCPSEC option.                    
                                                                        
    -APAR OA29582 added the EMPTYEXCPSEC(SUPPRESS) option in z/OS 1.10. 
     That option applies to ALL address spaces and their type 30 records
     will have EMPTY DD segments NOT-WRITTEN.  Variable SMF30DAS is the 
     count of DD segments that were suppressed by this option.          
                                                                        
    -APAR PM17542 for DB2 V10 exploits new z/OS 1.12 S99DASUP option,   
     which completely removes ALL of the DD segments from the SMF 30    
     records for that DB2 subsystem.  Use of S99DASUP is enabled in     
     DB2 with the SYSTEM MEMDSENQMGMT(ENABLE)                           
       but DB2 still decides whether to use S99DASUP or not.            
     SMF30DAS does NOT contain any counts of these non-written DDs.     
       (MEMDSENQMGT also enables DB2 management of Dataset Enqueues     
        in memory, a second performance improvement in that APAR.)      
                                                                        
     I found this post from Steven B Jones, IBM BCP Development in reply
     to a question about the independence of the two options:           
                                                                        
      "MEMDSENQMGMT and S99DASUP are independent, as you say.  S99DASUP 
       allows an authorized caller to suppress some of the accounting   
       overhead associated with Allocation.  It is intended for use with
       VSAM data sets, since VSAM records more information in its SMF   
       records than Allocation and SMF, which makes the overhead of us  
       maintaining the information pointless.                           
                                                                        
       MEMDSENQMGMT is associated with another feature in Allocation    
       processing.  The ALLOCxx parmlib member contains MEMDSENQMGMT    
       keyword to allow an installation the ability to disable the      
       feature, in case of odd interactions with ancient programs.  Once
       enabled, though, a program must use the IEFDDSRV MODIFY FEATURE  
       service to enable the feature for job step/ address space.       
                                                                        
       Two levels of enablement may seem excessive, but with Allocation,
       we're learning that we can never know what programs have done to 
       and with our data areas and allowing a programmer to choose to   
       enable a feature may have effects that the installation needs to 
       control.                                                         
                                                                        
IV.   DB2 Technical Notes.                                              
                                                                        
 1. Text                                                                
                                                                        
                                                                        
V.   IMS Technical Notes.                                               
                                                                        
 1. APAR PI05160 for IMS Connect Extensions V2 provides new function to 
    offload some CEX Event Recording processing to zIIP engines via a   
    start=up option for CEX.                                            
                                                                        
VI.  SAS Technical Notes.                                               
                                                                        
 3.  This note discusses a way to define %MACRO arguments that can be   
     changed in in nested macros.  It has not been implemented in MXG.  
     If %MACRO B defines a macro parameter ECHO, and %MACRO B is called 
     by %MACRO A, %A may or may not be able to change ECHO.             
                                                                        
     -If the %MACRO B (ECHO=NO); statement itself is used to set the    
      default value for parameter ECHO, then ECHO can not be changed    
      when %B is invoked by %A.  The default value defined in the %MACRO
      statement in %B will be used.                                     
                                                                        
      But, if that default NO value is instead conditionally set with a 
      %LET ECHO=NO; statement when there was no argument passed, then   
      that default value can be changed in the calling macro.           
      These are the two %macro defines:                                 
                                                                        
          %MACRO A (L=,M=,N=);                                          
           %B(BARGUMENT=&ANYPARM);                                      
          %MEND;                                                        
                                                                        
          %MACRO B (BARGUMENT=,ECHO=);                                  
           %IF %LENGTH(&ECHO) EQ 0 %THEN %LET ECHO=NO;                  
           %PUT FROM INSIDE B ECHO=&ECHO;                               
          %MEND;                                                        
                                                                        
      By inserting &ANYPARM at the last argument in %B invoke, ANY      
      parameter defined in %B can be set, and NONE of B's parameters    
      have to be defined in %A.                                         
                                                                        
      This syntax would change to ECHO=YES and invoke %A:               
                                                                        
          %LET ANYPARM=,ECHO=YES;                                       
          %A;                                                           
                                                                        
      HOWEVER: if the invocation statement in %MACRO A already specifies
      that argument, this technique will fail; SAS won't tolerate two   
      two instances of ECHO= in the call.                               
                                                                        
                                                                        
 2.  SAS Note 51008 reports using SAS ODS Graphics on z/OS with Java    
     versions:                                                          
        -Java 1.6.0.1 SR6                                               
        -Java 1.6.0.0 SR14                                              
        -Java 1.7.0.0 SR5                                               
     caused these errors when MXG invoked ODS:                          
       ERROR: The Java proxy could not create a new classloader.        
       ERROR: The Java proxy failed to update a classloader.            
       ERROR: Unable to attach current thread.                          
     That SAS note provides a  -jreoptions=  statement to add to your   
     HLQ.CONFIG(SITE) file to circumvent the error, documented in the   
     note for SAS 9.3, but the errors also occurred with SAS 9.4.       
                                                                        
                                                                        
 1. SAS Note 45793 for z/OS 1.13 reports an 0C4 ABEND can occur when    
    concatenated files are read but a file in the concatenation doesn't 
    exist.  IBM APAR OA37610 will correct the 0C4 ABEND so that you get 
    a SAS ERROR message rather than the ABEND.                          
                                                                        
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 31.09 (since MXG 30.30):        
    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.