RE: QTEMP (and QRPLOBJ)

Simon:

Thanks for the info.  I went through all my VLOG's for the last couple
weeks and didn't find anything relating to this problem.  And you're
right about the 2nd level text not providing any further help.  The next
time it happens I will report it to IBM and see if we can't get it
resolved.

Thanks again for your advice.

Dave

> ----------
> From:         Simon Coulter[SMTP:shc@flybynight.com.au]
> Reply To:     MIDRANGE-L@midrange.com
> Sent:         Wednesday, June 09, 1999 5:05 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: QTEMP (and QRPLOBJ)
> 
> 
> Hello Brad,
> 
> I doubt very much that is the problem.  This message usually results
> from the following 
> situations:
> 
>       Job gets resolved pointer to object
>       Object is destroyed
>       Job uses resolved pointer to access object
> or
>       Job gets resolved pointer to object
>       Job uses resolved pointer to set pointer to associated space
>       Object is destroyed
>       Job uses associated space pointer
> 
> This used to be a common situation before QRPLOBJ.  When a program was
> compiled you used to 
> have to delete or move the existing program.  Deleting it while it was
> in use would result in 
> this message (or a similar one).  Moving it was fine.  
> 
> The whole point of QRPLOBJ and the REPLACE(*YES) parameter is to avoid
> this situation.  The 
> compiler moves the existing program to QRPLOBJ and replaces it with
> the new version.  Any job 
> using the old version continues to do so until the program is CALLed
> again (provided it has 
> been deactivated).  That is because the job has a resolved pointer to
> the program and moving 
> an object doesn't change its virtual address -- doesn't move it
> physically either, just 
> reassigns its context.
> 
> Clearing a library is supposed to only destroy external objects.
> 
> This problem is happening in the ILE runtime support for the CHAIN
> operation and as I have 
> previously stated here MCH messages in IBM code generally indicate an
> APARable situation.  
> Some object the CHAIN expects has been destroyed.  Possibly due to LR
> being off.
> 
> MCH messages are notorious for their brevity so I doubt the
> second-level text names the 
> missing object but there should be a VLOG entry for the error that IBM
> can use to further 
> investigate.
> 
> Regards,
> Simon Coulter.
> 
> «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
> «» FlyByNight Software         AS/400 Technical Specialists       «»
> «» Eclipse the competition - run your business on an IBM AS/400.  «»
> «»                                                                «»
> «» Phone: +61 3 9419 0175      Mobile: +61 0411 091 400           «»
> «» Fax:   +61 3 9419 0175      mailto: shc@flybynight.com.au      «»
> «»                                                                «»
> «» Windoze should not be open at Warp speed.                      «»
> «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
> //--- forwarded letter
> -------------------------------------------------------
> > X-Mailer: Internet Mail Service (5.5.2448.0)
> > Date: Mon, 07 Jun 99 15:21:50 -0500
> > From: "Stone, Brad V (TC)" <bvstone@taylorcorp.com>
> > To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
> > Reply-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
>  
> 
> +---
> | 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
+---