Resolution to my MCH3601 problem

Folks:

Just an update ... I've solved my MCH3601 problem!

The issue was: in OS400 release V4R5 & below, the QBNLPGMI API was returning
entries of only 508 bytes long.  This is what my program expected.

In V5R1, however, the API is returning entries that are 3995 bytes long.  I
took it on faith that the entry size in the user space header was correct
and used that value to tell the QUSRTVUS api how much data I wanted put into
my data structure (which was only 508 bytes long).  Obviously, when I got
3995 bytes back, it over-wrote working storage and screwed things up that
happened to be situated after my data structure.

I've adjusted my API calls to only ask for the number of bytes in my data
structure (508) and everything is happiness again.

Of course, that begs the question, why is the API all of a sudden returning
entries of 3995 bytes long?  Is this a V5R1 change?  Where is it documented?

The data returned by the API appears to be blank after the initial 508
bytes.

Thanks to all those who gave advice.

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

Need a laugh: http://www.userfriendly.org/static
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---