***********************NEWSLETTER SIXTY-EIGHT***************************
          MXG NEWSLETTER NUMBER SIXTY-EIGHT JANUARY 3, 2017.            
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.                       
I.  The 2017 Annual Version MXG 34.34 was dated Jan 3, 2017.            
    You can always use this form                                                           
    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    
II.  MXG Technical Notes                                                
 1. Text:                                                               
III. MVS, a/k/a z/OS, Technical Notes.                                  
 3. APAR OA51823 corrects z/OS 2.2 SMF Record Corruption when using     
    Logger, but ONLY if your  SMF MAXBUFSIZE is less than 64K. Single   
    bytes in various SMF records (14, 61, 80) were wrong with one bit   
    changed in the created output SMF dumped file.                      
 2. APAR OA50703 for z/OS 2.2 with GDGe (GDGs Extended) with performance
    impact on Catalog Search is still open as of Dec 21, 2016.          
 1. APAR OA51325 reports SMF 15 UCB fields (DEVCLASS, DEVTYPE plus) are 
    invalid after APAR OA49909 was installed. APAR is open 10/25/2016.  
IV.   DB2 Technical Notes.                                              
 1. Text                                                                
V.   IMS Technical Notes.                                               
 1. Text                                                                
VI.  SAS Technical Notes.                                               
 1. SAS 9.3 and earlier can loop after termination, when ALL of the     
    following conditions exist, SAS NOTE 46767::                        
    - A file was allocated externally to SAS, in a JCL DD statement.    
    - A FILENAME statement in the SAS program used the same DD name     
      that was defined externally                                       
    - The same files in the same order were in both the FILENAME and    
      the external JCL statements, with at least one additional file    
      in the FILENAME statement at the beginning of the concatenation.  
    - The SAS system option SASAUTOS is being set and makes reference   
      to the FILENAME/DD Statement.                                     
    - SAS macro autocall services were used subsequently to setting     
      the SAS system SASAUTOS.                                          
    When you terminate SAS during resource cleanup, SAS loops while     
    trying to clear the SASAUTOS DD name.  The SASLOG displays SAS      
    termination messages, and all output is complete, but the job is    
    still consuming CPU time.  If all of the above conditions are true, 
    except that the data set names are different or the order is        
    different,  then instead of the loop during termination, you        
    get the following error in your SAS log:                            
       ERROR: Logical name MYAUTOS assigned but not in current scope.   
       ERROR: Error in the FILENAME statement.                          
    The only exposure in MXG is if you use // EXEC SAS,CONFIG=CONFIMXG  
    AND you have added a //SOURCLIB DD in your JCL.  It's that added    
    DD statement that creates the exposure for the problem.  Remove it. 
    None of the example MXGSASxx JCL Procedures are exposed.            
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 34.07 (since MXG 33.33):        
    See CHANGES.                                                        
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            
 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:  
  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