Prototypes for System APIs -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Prototypes for System APIs
From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
Date: Fri, 30 Nov 2018 17:16:39 -0500
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Anyone know what the IBM rules are for when a proto is supplied in QSYSINC ? Going through them a lot are supplied (such as QUSLRCD for example) but others such as QUSPTRUS are not there. I'm trying to come up with a way for clients to determine which ones they have and which they need to potentially create.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Prototypes for System APIs , Brian Parkins

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.