Resolution to my MCH3601 problem

[bvining@xxxxxxxxxxxx]

Up through V4R4 there was an appendix to the System API Reference titled
APIs by Release.  It marked every API that was changed by release as
well as what APIs were introduced in a given release.  This list was
removed in V4R5, and it appears from the various notes that no one
evidently even knew it was there (which is what had been suspected).

A goal for the future is to re-introduce this information via the
Information Center in a way that is much more obvious -- like, show me
the APIs that have changed in this release.

And yes, change flags (though no longer vertical lines in the margin)
continue to exist in the online API docs.  As for a summary booklet
of what might affect existing programs, the manual for that is the
Memo to Users.  The Memo to Users however does not point out changes
to APIs that can impact improperly coded programs (like inadvertently
retrieving 1000 bytes of data to a structure sized for 500).

Bruce

>
>Hmmm.. Don't those still exist?!
>
>At any rate, how would David have known to read the manual page for the
>API to see that it had changed?   Do you really read through the entire
>library of manuals with every new release and check the little bar at
>the lefthand side of the page to see whats new?!?!
>
>I agree with David.  A simple summary booklet with a "heads up" for things
>that have changed that might affect existing programs is a GREAT idea.
>
>>
>> I remember in the old days when we had manuals,  they had a vertical bar on
>> the page showing stuff that was new for this release.
>>
>


+---
| 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
+---