Re: Error: [SQL0804] SQLDA not valid. -- JAVA400-L

SQL0804 is:

Message ID . . . . . . . . . :   SQL0804
Message file . . . . . . . . :   QSQLMSG
  Library  . . . . . . . . . :     QSYS

Message . . . . :   SQLDA not valid.
Cause . . . . . :   If the error type is 2, 3 or 9, the entry in error is
&2,
  the value of SQLTYPE is &3, and the value of SQLLEN or SQLLONGLEN is &4.
  The specified SQLDA is not valid because of error type &1. A list of the
  error types follows:
    -- Error type 1 indicates that the value of SQLN is less than zero, the
  value of SQLD is not between 0 and 8000, the value of SQLD is greater than
  the value of SQLN, or that the value of SQLD has not been initialized in
  REXX.
    -- Error type 2 indicates that the value of SQLTYPE is not valid or that
  the value of SQLTYPE is not supported or has not been initialized in REXX.
  The types that are not supported in REXX are NUL-terminated graphic
string,
  NUL-terminated character string, PASCAL L-string, sign leading separate,
and
binary with precision and scale.
  -- Error type 3 indicates that the value of SQLLEN or SQLLONGLEN is not
valid or that the value of SQLLEN, SQLPRECISION, or SQLSCALE has not been
initialized in REXX. If REXX and SQLTYPE is decimal or numeric, then either
SQLPRECISION or SQLSCALE has not been initialized.  Otherwise, SQLLEN has
not been initialized.  If SQLTYPE is a LOB variable, then SQLLONGLEN is not
valid.
  -- Error type 4 indicates that size of the SQLDA area was not large enough
for the number of entries specified in SQLN statement.
  -- Error type 5 indicates that the SQLDA area was not on a 16-byte
boundary.
  -- Error type 6 indicates that the value specified for SQLDABC is not
valid. The value is either not large enough for the number of entries
 specified in SQLN or the value is greater than the maximum allowed.
   -- Error type 7 indicates that the value of SQLN was not at least twice
 the size of SQLD and LOB host variables were found in the SQLDA.
   -- Error type 8 indicates that the seventh byte of SQLDAID was not a '2',
 '3' or '4' and LOB host variables were found in the SQLDA.
   -- Error type 9 indicates that the SQLDATAL pointer was not null for a
 DBCLOB host variable, but the length value referenced by the SQLDATAL
 pointer had an odd value.
   -- Error type 10 indicates the SQLTYPE for a LOB locator did not match th
 type associated with LOB locator.
ecovery  . . . :   Correct the error in the SQLDA and try the request again.


----- Original Message -----
From: "Mike Silvers" <msilvers@hbs-inc.com>
To: <java400-l@midrange.com>
Sent: Friday, May 10, 2002 3:15 AM
Subject: Error: [SQL0804] SQLDA not valid.


> All,
>
> I am using JDBC for data access to the AS/400.  I am using a prepared
> statement.  When I execute the prepared statement to add a new record, I
am
> getting the error: [SQL0804] SQLDA not valid.  I am not sure what this
error
> is indicating.  Any ideas?
>
> Thanks
>
> Mike
>
> ================================
> Mike Silvers
> AS/400 Senior Programmer/Analyst
> AS/400 IBM Certified RPG IV Developer
> AS/400 IBM Certified Solutions Expert
> Hainey Business Systems
> 8 E. Canal St
> Dover, PA 17315
> Branch Office:  (410) 397-8739
> Phone:  (800) 932-3380 ext. 237
> Fax:  (717) 292-9474
> Web: http://www.hbs-inc.com
> ________________________________
> Providing E-Commerce, EDI, AS/400
> Development, Java Development,
> and related services nationwide.
> ================================
>
>
> _______________________________________________
> This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
> To post a message email: JAVA400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
> or email: JAVA400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.
>
>