× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yes, there are all sorts of objects created in QTEMP that you can't see
but CLRLIB doesn't delete them!

> -----Original Message-----
> From: Leland, David [SMTP:dleland@Harter.com]
> Sent: Tuesday, June 08, 1999 8:21 AM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: QTEMP
> 
> No, I don't think it's that.  It's happening on programs which don't
> create or use objects in QTEMP or QRPLOBJ and we aren't recompiling
> the
> programs which would place them in QRPLOBJ.  This has been going on
> for
> a while and I keep hoping with each new release of the operating
> system
> that the problem will be taken care of.  It's so sporadic that it's
> hard
> to document and report to IBM.
> 
> For some reason, I remember someone saying something about the fact
> that
> IBM keeps some objects in QTEMP but they're hidden.  Anyone know if
> this
> is true?
> 
> Dave
> 
> > ----------
> > From:       Stone, Brad V (TC)[SMTP:bvstone@taylorcorp.com]
> > Reply To:   MIDRANGE-L@midrange.com
> > Sent:       Monday, June 07, 1999 3:21 PM
> > To:         'MIDRANGE-L@midrange.com'
> > Subject:    RE: QTEMP
> > 
> > These are most likley objects that have been replaced.  IBM stores
> > them in
> > QRPLOBJ library.  If you replace an object that a job still has in
> > memory
> > and the job tries to call it again, you'll get the error you
> describe.
> > 
> > Bradley V. Stone
> > Taylor Corporation - OASIS Programmer/Analyst       
> > bvstone@taylorcorp.com
> > 
> > 
> > > -----Original Message-----
> > > From:     Leland, David [SMTP:dleland@Harter.com]
> > > Sent:     Monday, June 07, 1999 2:16 PM
> > > To:       'MIDRANGE-L@midrange.com'
> > > Subject:  QTEMP
> > > 
> > > From time to time we continue to receive a rather odd error
> message
> > on a
> > > few programs.  They are all ILE RPG program and the similarity
> > between
> > > all these programs is that they return to the caller with LR off.
> > The
> > > error messages we receive are:
> > > MCH3402 - Tried to refer to all or part of an object that no
> longer
> > > exists.
> > > and this is followed by:
> > > RNX9998 - Internal failure in compiler or subroutine.
> > > 
> > > 
> > > I'm wondering if IBM stores objects in the QTEMP library that are
> > > hidden, and if clearing QTEMP could cause the problem above.  The
> > > programs do not create or access any objects in QTEMP themselves.
> > > Pressing F9 on MCH3402 shows the following:
> > > 
> > > Message ID . . . . . . :   MCH3402       Severity . . . . . . . :
> > 40
> > > 
> > > Date sent  . . . . . . :   06/07/99      Time sent  . . . . . . :
> > > 13:31:09
> > > Message type . . . . . :   Escape
> > > 
> > > CCSID  . . . . . . . . :   65535
> > > 
> > >  
> > > 
> > > From program . . . . . . . . . :   QRNXIO
> > > 
> > >   From library . . . . . . . . :     QSYS
> > > 
> > >   From module  . . . . . . . . :     QRNXDBIO
> > > 
> > >   From procedure . . . . . . . :     _QRNX_DB_CHAIN
> > > 
> > >   From statement . . . . . . . :     6
> > > 
> > >  
> > > 
> > > To program . . . . . . . . . . :   QRNXIO
> > > 
> > >   To library . . . . . . . . . :     QSYS
> > > 
> > >   To module  . . . . . . . . . :     QRNXDBIO
> > > 
> > >   To procedure . . . . . . . . :     _QRNX_DB_CHAIN
> > > 
> > >   To statement . . . . . . . . :     6
> > > 
> > > 
> > > Any ideas?
> > > 
> > > Thanks,
> > > Dave
> > > p.s. We are very current on our CUM tapes and I'm installing the
> > latest
> > > Database CUM PTF tape this weekend.
> > > +---
> > > | 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
> > > +---
> > +---
> > | 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
> > +---
> > 
> +---
> | 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
> +---
+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.