Re: Replacing *entry plist -- 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: Re: Replacing *entry plist
From: Scott Klement <klemscot@xxxxxxxxxxxx>
Date: Tue, 25 Mar 2003 12:22:10 -0600 (CST)
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>,<mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

It's illegal to code 2 PI's without putting P-specs in between.

*RNF3768 The procedure interface has already been defined for this
procedure.

It makes absolutely no sense to have two PI's, unless they're in separate
subprocedures...

On Tue, 25 Mar 2003, mlazarus@xxxxxxxx wrote:
>
>  Whoops, of course you're right.  I confused it w/ the PR.  But my question
> still stands - what if two PI's are coded?
>

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

DUMP Program on Error?? , Michael Naughton

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.