RE: Resolution to my MCH3601 problem

There have been changes to API's for v5r1.  As to where they are documented?
Good Luck.  It's scattered throughout the manuals.

The example I 'found' was the length of the trigger buffer increased, to a
length longer than the dtaq entry length my trigger programs wrote them to
which caused some truncation (fortunately in the middle of a packed numeric
field so I got a DDE in one case).  After some lengthy 'discussions' with
IBM their developers informed me that I should have retrieved the length of
the dtaq entry with the api and compared it to the buffer length and when it
became necessary automatically deleted the current data queue and created a
new one with a large enough entry size.  A reasonable fix I suppose,
although I would have checked all that about 50 million times for the one
change at v5r1.  Then I could check it who knows how many times till they
decide to change it again in the future sometime.  Of course, they sell
hardware don't they?

A cogent list of gotcha's would be nice, but by the time I got them to admit
it had changed the memo to users was already printed in 55 languages or
something.  Best I could get was a mention in an apar to the memo to users.

Upgraders:  Read the memo to users and any associated information very
carefully and critically!  And hope you won't be the one to find the next
gotcha.

Tom Westdorp
AS/400 Senior Programmer/Analyst 
IBM Certified Specialist - RPG IV Programmer
IBM Certified Specialist - RPG IV Developer 
Certified Master RPG IV Programmer 
Voice:  (702) 221-6859
Fax:    (702) 221-6881
tom.westdorp@stationcasinos.com <mailto:tom.westdorp@stationcasinos.com>  

==> The trouble with hitting the jackpot on a slot machine is that it takes
so long to put the money back.

 

-----Original Message-----
From: David Gibbs [mailto:dgibbs@mks.com]
Sent: Wednesday, May 30, 2001 12:12 PM
To: 'RPG400 Mailing List'
Subject: 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
+---
+---
| 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
+---