×
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.
SQL0204 for UDF, common problems:
1> DSPSRVPGM to get the real full name; i.e. case sensitive
2> Invoking with mismatch type, length, etc. [esp. for
CHAR(length); use VARCHAR to enable specifying a literal with less than
/length/ characters]
3> The SQL PATH is not established to match assumptions\expectations
The given exhibits #2 [the literal 'test' is VARCHAR(4) according to
SQL], and very possibly #1 [procedure name may be:
IMPORT_SUBSTRINGMERGE]. When the statement is run with NAMING(*SYS),
the default path is [¿or includes?] *LIBL.
The UDF can be found in *LIBL from the path, but the UDF that is
resolved [via /function resolution/ via QSYS2.SYSROUTINE] can not have
its *SRVPGM dynamically located; the specific program must be bound in
the UDF.
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
