• Subject: RE: LSTFFD utility from Midrange computing
  • From: "Stone, Brad V (TC OASIS)" <bvstone@xxxxxxxxxxxxxx>
  • Date: Mon, 12 Jul 1999 13:04:57 -0500

Well, after further looking, the source from MC was old and I had hardcoded
the size of the data instead of using the parameter passed back in the
EntrySize parameter.  This has been fixed in the meantime and I will be
posting the newer version on my AS/400 shareware site.

The reason I thought IBM did something is because they DID change an API
from V4R2 to V4R3 for another one of my tools (SCNMSGF).  Half of the data
was pushed over one byte.  This could not be fixed without having two
version of the software.

Bradley V. Stone
BVS/Tools
http://www.bvstools.com




> -----Original Message-----
> From: Dennis Lovelady [mailto:dennis@lovelady.com]
> Sent: Monday, July 12, 1999 12:29 PM
> To: MIDRANGE-L@midrange.com
> Subject: Re: LSTFFD utility from Midrange computing
> 
> 
> Hi, Bradley:
> 
> I think IBM's getting a bum rap on this one.
> 
> From: Stone, Brad V (TC OASIS) <bvstone@taylorcorp.com>
> Sent: July 8, 1999 3:47 PM
> 
> 
> > They did, but in this case they added a few new fields to 
> the end of a
> > format, and changed the size of one field from 10 to 30.
> <snip>
> > CALL      'QUSRTVUS'
> > PARM                    SpaceName
> > PARM                    SpaceStart
> > PARM                    DataSize
> > PARM                    List
> 
> Ummm... if this is the failing line, then I don't understand 
> your point.
> This has been the structure of the parameters for QUSRTVUS 
> ever since it
> was introduced, at V2R3.
> 
> What field was the field length increased on?  And in what API?
> 
> > They say they will be backward compatible (I should try the 
> V4R4 version
> on
> > V4R3 to see), but forward?  Dunno.  If you use the /COPY members for
> APIs in
> > QSYSINC, you still have to recompile and possibly change a 
> few things to
> get
> > it to work.  If they change an API, chances are you will 
> have to update
> the
> > application.
> 
> Actually, they don't make mention of backward compatibility 
> w.r.t. APIs.
> They have this to say regarding FORWARD compatibility, though:
> > 1.1.1 Compatibility with Future Releases
> > In future releases, IBM intends that one of the following 
> will be true:
> >
> >  If additional input or output parameters are provided for 
> any of the
> > APIs, the new parameters will be placed after the current parameters
> > and will be optional parameters. The existing APIs will continue to
> > work without any changes.
> 
> 
> 
> +---
> | 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 thread ...


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

This mailing list archive is Copyright 1997-2019 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].