Re: Need assistance with External SQL Proc

is there a joblog in the job which calls the procedure? SQL fails
silently, so it can be hard to see where an error has occurred.

Can you call the SQL prosecute from an SQL command line like STRSQL? you
should see a message saying the result set returned data.

I would add some code to the procedure that writes messages to a message
log file. That way you can start to pin down where the procedure is
working and where it fails.

create table qgpl/runlog (
message char(256) not null default ' ',
logDateTime timestamp not null default current timestamp )

insert into qgpl/runlog ( message )
values('received from dtaq ' || char(dqrcdln) || ' ' || LEFT(DQDATA,
INT(DQRCDLN)) ) ;

you can also call QCMDEXC in the SQL procedure and run the DSPJOBLOG
command:

call qcmdexc('dspjoblog output(*print) ', 27) ;

sometimes to track down the actual job in which the procedure is running I
will have the procedure send a message to the QSYSOPR message queue:
call qcmdexc('sndmsg msg(hello) tousr(*sysopr) ', 34) ;

-Steve