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

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

Am 02.02.2026 um 17:16 schrieb Justin Taylor <jtaylor.0ab@xxxxxxxxx>:

The intention is to perform a query with diff WHERE clauses. The
varchar(10) is order# while varchar(20) is serial#. Personally, I'd have
just gone with diff procedures, but the original author went OVERLOAD.

Thanks

On Mon, Feb 2, 2026 at 9:03 AM Daniel Gross <daniel@xxxxxxxx> wrote:

Well - that might help now, but it might also cause problems in the future
when compiling programs, that depend on the first (old) prototype.

With CONST one can code procedure(variable:...) or procedure('HELLO':...)
- without CONST you can't supply the parameter as a literal.

So - what is the intention of having two procedures where one parameter is
VARCHAR(20) or VARCHAR(10)? As you had CONST, it wasn't a
"return-parameter".

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.