T.L. Ashford is “The Labeling Answer”® for the System i. Ashford's Barcode400 has been the dependable choice for the industry since 1983. With Barcode400's newly enhanced Graphic Designer no “green screen” interaction is needed for label design. New features include: AFP/HP-compatible printing, easy-to-use graphics import tool, test print to desktop printer, simple font download tool, updated drivers and format listing reports. Even compliance labeling is made easy with design templates. Call 800-541-4893 to order a FREE DEMO CD or visit us at T.L. Ashford & Associates. Read More >>
Another year and another set of RPG enhancements. As always, the reactions range from "I'm not sure how that applies to me" to "This is downright intriguing."
As my teammate Jon Paris mentioned a couple of weeks ago, the IBM documentation we have seen to date seems to be placing a strange emphasis on which enhancements are most pertinent. But in fairness to IBM (now there is a novel thought), I think most of the documentation simply follows the order of RPG specifications. In this article, I will attempt to guide you through the enhancements in the order I think is most pertinent. Feel free to disagree.
The API Corner: Understanding API Data Types In a previous column, we discussed the basics of the API error code structure. In today's column, we'll talk about the basic API data types found in callable APIs and exit points.
By Bruce Vining
System APIs use a language-neutral convention when defining the type and size of data that is to be used as a parameter or a subfield of a data structure. A typical API parameter list would be the Retrieve Member Description QUSRMBRD API shown below and documented here.