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

No, no it can't ... not really.

Assuming the procedure's been out there for a while with CONST, removing it
will break existing callers. Unless you recompile everything using it.
And even there you could end up with a failed compile.

Charles


On Mon, Feb 2, 2026 at 9:51 AM Justin Taylor <jtaylor.0ab@xxxxxxxxx> wrote:

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 <daniel@xxxxxxxx> 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: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.