Re: OVERLOAD matching: varchar(10) & varchar(20)

The OVERLOAD points to diff procedures, and those procedures have the query
details.  OVERLOAD IMO obfuscates the functionality, which I don't like.
But it can work.



On Mon, Feb 2, 2026 at 10:40 AM Daniel Gross <[email protected]> wrote:

> Oh - and you are trying to detect the field/column for the WHERE clause
> out of the length of the parameter field?
>
> Not a good idea IMHO.
>
> Make it 2 parameters with OPTION(*NOPASS:*OMIT). If the user wants the
> original procedure with SERIAL#
>
>    procedure(serial_field);
>
> If the ORDER# is wanted:
>
>    procedure(*omit:orderno_field);
>
> And the user can even supply both fields if needed).
>
> This way you can detect it via %PASSED(...) and there are no ambiguities.
>
> HTH
> Daniel
>
>
>
-- 
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: [email protected]
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact [email protected] for any subscription related questions.