AW: MSGSQL0601 on an SQL CLOSE statement

[Wiesmayr Rudolf <Rudolf.Wiesmayr@xxxxxxxxxxx>]

Hi David!

Just to be sure: You are current with PTFs, especially SF9910x?

40404040 i.e. Blanks looks like damaged variables, in this case
an internal pointer in the database routines' area.
Maybe it was your program. Watch out.

But sometimes its the database itself who gets crazy.
So try a search in the APAR database
http://as400service.rochester.ibm.com/as4sde/nas4apar.NSF/b6c9b771e38b5e
a2862564c00079d110?SearchView
using MSGMCH0601 AND your Q* routine name from the crash.

HTH,
Rudi

BTW: I have founded a new mailing list
     to discuss SAP R/3 on AS/400 topics.
     Contact me for further information.
-------------------------------------------------------------------
Dipl.-Ing. Rudolf Wiesmayr  /\ Tel:     +43 - 0732 / 7070 - 1720
SAP R/3 BASIS &             /\ mailto://Rudolf.Wiesmayr@mag.linz.at
AS/400 System Administrator /\ IBMMAIL: at3vs7vs@ibmmail.com
              List owner of /\ mailto://sap400@mag.linz.at
Magistrat Linz, ADV/SB      /\ Fax:     +43 - 0732 / 7070 - 1555
Gruberstrasse 40-42         /\
A-4041 Linz                 /\ http://www.linz.at
-------------------------------------------------------------------
A system admin's life is a sorry one.  The only advantage he has
over Emergency Room doctors is that malpractice suits are rare.
On the other hand, ER doctors never have to deal with patients
installing new versions of their own innards!

> -----Ursprüngliche Nachricht-----
> Von:  David Gibbs [SMTP:David.Gibbs@IL.US.MKS.com]
> Gesendet am:  Mittwoch, 17. Februar 1999 16:54
> An:   'Midrange Mailing List'
> Betreff:      MSGSQL0601 on an SQL CLOSE statement
> 
> Folks:
>  
> I've run into a stumper... has anyone run into a situation where you
> get
> a MCH0601 message when doing an SQL CLOSE statement in an SQL RPGLE
> program?
>  
> The actual text of the message is "Space offset X'40404040' is outside
> current limit for object SQLDA TEMP SPACE."
>  
> The only thing that *MIGHT* be strange is that there are two SQL FETCH
> statement just prior to the close... the first fetch gets a record,
> the
> 2nd fetch does not.  Also, the original program tried to do a "SELECT
> *"
> into a multi-occurrence data structure (I temporarily changed that so
> it
> fetches into a regular DS).
>  
> Any information would be appreciated.
>  
> david
>                                               
>  
> 
> --
> 
> David Gibbs
> Sr. Software Engineer
> Mortice Kern Systems US, Inc.
> 2500 S. Highland Ave., Suite 200
> Lombard, IL  60148
> 
> phone: (630) 495-2108 x5004
> http://www.mks.com
> mailto:dgibbs@mks.com
> 
> 
> Opinions expressed are strictly my own and do 
> not necessarily reflect those of my employer
> 
>  "I drank what???"
>   - Socrates
> 
> 
>  
> +---
> | 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
+---