Periodically, our one 3rd party application results in a MCH3601 Pointer not set for location referenced. A pointer was used, either directly or as a basing                       
                                       pointer, that has not been set to an address. 
What could be the cause of the MCH3601?
What can be captured to resolve the issue?  
MCH3601    Escape                  40   03/16/14  08:36:45.622618  APIPROC      ICGTWYP1OC  *STMT    APIPROC     ICGTWYP1OC  *STMT
                                     From user . . . . . . . . . :   WSCUSER                                                      
                                     From module . . . . . . . . :   APIPROC2                                                     
                                     From procedure  . . . . . . :   DoProcess                                                    
                                     Statement . . . . . . . . . :   59                                                           
                                     To module . . . . . . . . . :   APIPROC2                                                     
                                     To procedure  . . . . . . . :   DoProcess                                                    
                                     Statement . . . . . . . . . :   59                                                           
                                     Message . . . . :   Pointer not set for location referenced.                                 
                                     Cause . . . . . :   A pointer was used, either directly or as a basing                       
                                       pointer, that has not been set to an address.                                              
CEE9901    Escape                  30   03/16/14  08:36:45.623605  QLEAWI       QSYS        *STMT    APISTART    ICGTWYP1O   00BD 
                                     From user . . . . . . . . . :   WSCUSER                                                      
                                     From module . . . . . . . . :   QLEDEH                                                       
                                     From procedure  . . . . . . :   Q LE leDefaultEh                                             
		     	Statement . . . . . . . . . :   204                                             
 Message . . . . :   Application error.  MCH3601 unmonitored by APIPROC at       
   statement 0000000059, instruction X'0000'.                                    
 Cause . . . . . :   The application ended abnormally because an exception       
   occurred and was not handled.  The name of the program to which the           
   unhandled exception is sent is APIPROC APIPROC2 DoProcess. The program was    
   stopped at the high-level language statement number(s) 0000000059 at the      
   time the message was sent.  If more than one statement number is shown, the   
   program is an optimized ILE program.  Optimization does not allow a single    
   statement number to be determined.  If *N is shown as a value, it means the   
   real value was not available. Recovery  . . . :   See the low level messages  
   previously listed to locate the cause of the exception.  Correct any errors,  
   and then try the request again.                                               
Thank You
_____
Paul Steinmetz 
IBM i Systems Administrator 
Pencor Services, Inc. 
462 Delaware Ave 
Palmerton Pa 18071 
610-826-9117 work 
610-826-9188 fax 
610-349-0913 cell 
610-377-6012 home 
psteinmetz@xxxxxxxxxx 
http://www.pencor.com/
As an Amazon Associate we earn from qualifying purchases.