Re: Debugging a UDF on V6.1

Hi Walter,

One possibility is that the procedure in the service program is never getting called, which could happen because

a) the service program is not where it is expected to be on the CREATE FUNCTION statement

b) the parameters being passed to the UDF do not match what's expected. One of the more common problems is that a character string literal passed to a UDF is passed as a VARCHAR, but the procedure is expecting CHAR, i.e. a fixed-length field.

hth,

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx>

/
On 2/27/2014 10:46 AM, Walter Bellisio wrote:

I'm attempting to debug a User Defined Function that uses a service program to do the work on a V6.1 release. This is the iDate source downloaded from A. Campin, with the modules, service program and functions created properly. STRSRVJOB and STRDBG are done on one session, and a simple STRSQL with a select statement that uses the UDF is done on the other session that the STRSRVJOB points to. A break point was set on the first statement of every procedure in both modules and I can't get a module to stop at any of the break points. The RPGLE modules of the service program were also compiled with DBGVIEW(*ALL) and that did not work as well. Has anyone encountered a similar problem?

Walter

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com