Re: stored procedure error - sql0443n - sqlstate=38501 -- MIDRANGE-L

On Apr 8, 2005 10:06 AM, Colin Williams <colin.williams@xxxxxxxxxxxx> wrote:
> The message description for that is "Trigger program or external routine
> detected an error".
> 
> Sounds like your calling the program correctly, but the RPG program is
> falling over

I checked for joblogs, looking for errors and could not find any.  I
dont know which job on the 400 runs the stored procedure.   Is there a
trace I can run?

I dont think the as400 program is failing.  I changed the code to just
do a return and I gave public authority to the program and the
library.

-Steve


> 
> cheers
> Colin.W
> 
> http://as400blog.blogspot.com
> 
> 
> -----Original Message-----
> From: Steve Richter [mailto:stephenrichter@xxxxxxxxx]
> Sent: 08 April 2005 14:52
> To: Midrange Systems Technical Discussion
> Subject: Re: stored procedure error - sql0443n - sqlstate=38501
> 
> On Apr 8, 2005 9:44 AM, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
> > Have you tried testing the stored procedure from iSeries Navigator?
> 
> how do I do that?  The reason I went the DB2 Enterprise Server route is
> because I dont have client access V5R3 ( I have v5r1 ).  V5R1 does not have
> the DB2Connection classes for .NET.
> 
> -Steve
> 
> > 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 08:35 AM
> > Please respond to
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> >
> > To
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc
> >
> > Subject
> > stored procedure error - sql0443n - sqlstate=38501
> >
> >
> > I am getting an error, sql0443n, sqlstate=38501 when I execute a
> > stored procedure from db2 udb that is calling an rpgle program. The
> > code is on an
> >
> > asp.net <http://asp.net> web page and uses the DB2Connect and
> > DB2Command classes to connect to the sql database of the as400.
> >
> > Here is the asp.net <http://asp.net> code that creates and then
> > executes the stored procedure:
> > ( note how clean asp.net <http://asp.net> code can be! )
> > cmd = new DB2Command();
> > cmd.Connection = conn;
> > 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!");
> >
> > stored procedure is executed:
> > string vlu1 = "a";
> > cmd = new DB2Command();
> > cmd.Connection = conn;
> > cmd.CommandType = CommandType.StoredProcedure ; cmd.CommandText =
> > "FAXMAIL.TEST35B"; cmd.Parameters.Add(new DB2Parameter("VLU1", vlu1
> > )); cmd.ExecuteNonQuery();
> > Trace.Write("AutoCoder", "Stored procedure executed!");
> > What is odd is this code works when the language of the stored procedure
> > is
> > RPG or CL. It only fails when it is RPGLE. I suspect that the DB2 UDB
> > install I am using on the Windows PC does not support RPGLE, only RPG and
> > CL. ( when I spoke to an AS400 tech last week he said the "N" at the end
> > of
> > the error code means the error is on the PC side )
> > There is a DB2 trace that can be run on the PC:
> > db2trc on -f trace.dmp
> > <reproduce the problem-try to connect from ASP .NET>
> > db2trc off
> > But the output is in a seemingly secret IBM binary code, so I cant open
> > the
> > file in a text editor.
> > Any thoughts on this error?
> > Is there a trace I can run on the as400 that shows if my stored procedure
> >
> > is actually running on the as400?
> > thanks,
> > -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.
> 
> This e-mail has been sent by a company of Bertram Group Ltd, whose registered 
> office is 1 Broadland Business Park, Norwich, NR7 0WF.
> This message, and any attachments, are intended solely for the addressee and 
> may contain privileged or confidential information.  If you are not the 
> intended recipient, any disclosure, copying, distribution or any action taken 
> or omitted to be taken in reliance on it, is prohibited and may be unlawful.  
> If you believe that you have received this email in error, please contact the 
> sender immediately. Opinions, conclusions and statements of intent in this 
> e-mail are those of the sender and will not bind a Bertram Group Ltd company 
> unless confirmed in writing by a director independently of this message.
> Although we have taken steps to ensure that this email and any attachments 
> are free from any virus, we advise that in keeping with good computing 
> practice the recipient should ensure they are actually virus free.
> 
> --
> 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.
> 
>