Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error "-470"

32 views
Skip to first unread message

ridu...@hotmail.com

unread,
Jan 15, 1999, 3:00:00 AM1/15/99
to
Hi

I am currently involved in an Integration project between
DB2 MVS and Lotus Domino via DB2 Connect. I use DB2 LSX as
an interfacing to send and receive my data.

These few days, I 've been receiving the following error quite a
number of times. The error is:

[IBM][CLI Driver][DB2] SQL0969N There is no message text
corresponding to SQL error "-470" in the message file on this
workstation. The error was returned from module "DSNXRIC "
with original tokens "007 ".
SQLSTATE=39002 720 LSXDB2- Database driver could not
complete the requested operation.


Anybody out there know how to solve this problem?

thanks and best regards
Riduan

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

stem...@my-dejanews.com

unread,
Jan 15, 1999, 3:00:00 AM1/15/99
to
In article <77n850$vbe$1...@nnrp1.dejanews.com>,

ridu...@hotmail.com wrote:
> Hi
>
> I am currently involved in an Integration project between
> DB2 MVS and Lotus Domino via DB2 Connect. I use DB2 LSX as
> an interfacing to send and receive my data.
>
> These few days, I 've been receiving the following error quite a
> number of times. The error is:
>
> [IBM][CLI Driver][DB2] SQL0969N There is no message text
> corresponding to SQL error "-470" in the message file on this
> workstation. The error was returned from module "DSNXRIC "
> with original tokens "007 ".
> SQLSTATE=39002 720 LSXDB2- Database driver could not
> complete the requested operation.
>

This is an DB2/390 Error Code it means:

SQL Code: -470 SQL CALL STATEMENT SPECIFIED A NULL VALUE FOR INPUT
PARAMETER number, BUT THE STORED PROCEDURE DOES NOT
SUPPORT NULL VALUES.

SQLSTATE Code: 39002

Description: DB2 received an SQL CALL statement for a stored procedure
that could not be processed because a null value was detected
in the incoming parameter list. The DB2 catalog table
SYSIBM.SYSPROCEDURES contains an entry for the stored
procedure which indicated that it will not accept null values
(LINKAGE=' ').

number - identifies the parameter from the PARMLIST field in
SYSIBM.SYSPROCEDURES

User Action: Retry the SQL CALL statement after correcting the problem


It Seems you have some problems with stored porcedures ?

> Anybody out there know how to solve this problem?
>
> thanks and best regards
> Riduan
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

Ciao Matthias

0 new messages