RE: triggers & s36 update pgms

Jim,

Are you calling any API's or using data queues anywhere within the
application?  If so you may be corrupting memory due to invalid parameters
somewhere such as length of data parms.  These type of problems are
typically what causes this error when trying to access a file.  I have seen
several cases where code has 'worked' previously and then minor changes or a
different release will make the problem manifest itself.

Scott Mildenberger

> -----Original Message-----
> From: Jim Franz [mailto:franz400@triad.rr.com]
> Sent: Friday, May 11, 2001 4:22 AM
> To: MIDRANGE-L@midrange.com
> Subject: Re: triggers & s36 update pgms
> 
> 
> my files are actually native, and am gradually replacing s36
> pgms. Suspect I have a ptf prob. finally got a job log w/detl
>  40    05/11/01   08:32:47   QRNXIO         QSYS        *STMT 
>    QRNXIO
>    From module . . . . . . . . :   QRNXDBIO
>    From procedure  . . . . . . :   _QRNX_DB_SETLL
>    Statement . . . . . . . . . :   9
>    To module . . . . . . . . . :   QRNXDBIO
>    To procedure  . . . . . . . :   _QRNX_DB_SETLL
>    Statement . . . . . . . . . :   9
>    Message . . . . :   Tried to refer to all or part of an 
> object that no
>      exists.
>    Cause . . . . . :   The most common cause is that a stored 
> address to
>      object is no longer correct because that object was 
> deleted or part
>      object was deleted.
> 
> calling supportline next
> jim
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---