RE: Pointer not set for location referenced.

Hey Eric,

I didn't read all responses to your inquiry so I'm not sure if you
resolved the issue yet. If you haven't, one thing you might want to
verify is the binding source associated with your service program. If
someone modified the binding source keeping the same signature but
changing the order of the exports and then didn't recompile every
program that uses that service program you'll get mch3601 errors. The
easiest way to verify this is to run debug over one of the programs
that's causing the issues. When it gets to the statement that uses one
of the service program procedures step into it and verify that the
correct procedure is being used. If it not you more than likely have an
issue with rearranged binding source. 

This is very common when you use TurnOver or some other type of change
management package. 



Thanks,
S. Ellsberry
(678) 893-6673
steve.ellsberry@xxxxxxxxxxxx
 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Eric Wolf
Sent: Tuesday, June 06, 2006 5:05 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Pointer not set for location referenced.

   To the list,
   I have looked through the archives but cannot seem to find an
explanation
   for what is occuring.  Here it is:
    
   My users are receiving this error MCH3601 Pointer not set for
location
   referenced on different programs during the day.  All the programs
are
   using modules of a service program to retrieve a single record from a
   file.  Each module is being passed the external datastructure of the
file
   to be retrieved and the datastructure is being cleared and the key
fields
   are being reset before each execution of the module.  They pretty
much all
   look something like this:
    
   /free
   ...
   clear carrier;
   carrier.id = ordcarrier;
   carrier = RtvCarrier (carrier);
   ...
   /end-free
   Every once-in-a-while, the error appears when attempting to execute
the
   RTVCARRIER statement. After receiving the error message, the users
sign
   off and back on again and all is fine.  None of the modules have
changed
   and new modules are added to the end of the SRVSRC BND
   member. The programs that are "calling" the modules are compiled with
the
   ACTGRP(*CALLER) 
    
   Any suggestions as to where to focus my attention would be greatly
   appreciated...
    
   TIA,
   Eric A. Wolf
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.