Re: stored procedure error - sql0443n - sqlstate=38501

[rob@xxxxxxxxx]

CHGJOB of that job to increase logging levels do anything?
STRSRVJOB, TRCJOB, help find the missing service program?
However, it sounds like you should have enough data that IBM should now be 
able to figure it out.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Steve Richter <stephenrichter@xxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/08/2005 12:42 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: stored procedure error - sql0443n - sqlstate=38501






the problem turns out to be a "service program not found" error.  This
is the db2 udb trace ( on the pc side ) that showed the error:

db2trc  fmt  -c  <dump file>  trace.com 

I still dont know how to get the as400 to show me any error
information. The stored procedures are executed in a job named
QRWTSRVR in QSYSWRK. But the IBM code that runs in those jobs must
remove the messages from the joblog because I can find no indication
in the joblog of those jobs  that an error has occured.

-Steve

On Apr 8, 2005 12:56 PM, Dan Kimmel <dkimmel@xxxxxxxxxxx> wrote:
> Lie. Tell DB2 it is RPG. It shouldn't matter to DB2 whether the external
> program is written in RPG or RPGLE. In either case it does a system call
> to the program and parameters are passed through a system call in the 
same
> manner whether it is RPG or RPGLE.
> 
> I haven't tested this. Just a theory.
> 
> Dan
> 
> 
> Steve Richter <stephenrichter@xxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 04/08/2005 10:41 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> 
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
> 
> Subject
> Re: stored procedure error - sql0443n - sqlstate=38501
> 
> On Apr 8, 2005 10:51 AM, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
> > Question:  Is the CREATE PROCEDURE what is failing from your PC 
program?
> 
> no.  I can create and drop the procedure.  what fails is the execute.
> It only fails when LANGUAGE is RPGLE.  LANGUAGE RPG or CL works.  ( I
> suspect DB2 UDB does not support RPGLE )
>  cmd.CommandType = CommandType.Text;
>  cmd.CommandText = "CREATE PROCEDURE FAXMAIL.TEST35B (" +
>                       "IN VLU1 CHAR(1) ) " +
>                        "LANGUAGE RPGLE " +
>                        "DETERMINISTIC " +
>                        "NO SQL " +
>                        "SPECIFIC TEST35B " +
>                        "PARAMETER STYLE GENERAL " +
>                        "EXTERNAL NAME 'FAXMAIL/TEST35B'";
>   cmd.ExecuteNonQuery();
>    Trace.Write("AutoCoder", "Stored procedure created");
> 
> > If so, have you tried putting the entire CREATE PROCEDURE in a source
> > member and using RUNSQLSTM on it and see what happens?  Because 
writing
> a
> > PC program to do this (which should be a one shot deal) seems like a 
lot
> > of extra work.
> 
> I am an asp.net programmer now! :)  It is a good idea but it is better
> for me to address the problem on the asp.net side of things.
> 
> I do have an IBM DB2 support call open, so I will see what they say.
> 
> Here is how to run and format the db2 trace:
> 1 - db2trc on -l 128M
> 2 - recreate the error
> 3 - db2trc dump <file_name.dmp>
> 4 - db2trc off
> 5 - db2trc fmt <file_name.dmp> <file_name.fmt>
> 6 -     db2trc flw <file_name.dmp> <file_name.flw>
> 
> -Steve
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.