Hello

I was needing to connect a v8 client fp2 to a v7 server fix 10, and
after the
configuration when trying to use the application, a messagem
displaying
that SYSSH200 package is missing or not found.

To solve this, i'd executed BIND BLOCKING ALL GRANT PUBLIC on CLI/ODBC
Support / CLP / Data Import/Export Utilities from v8 client using
admin key

But during the binding time, some warnings popped on the bind log as
follows :

LINE MESSAGES FOR db2clpcs.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2clprr.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2clpur.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2clprs.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2clpnc.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0595W Isolation level "NC" has been escalated to "UR".
SQLSTATE=01526
SQL0091N Binding was ended with "0" errors and "1" warnings.
SQL0001N Binding or precompilation did not complete successfully.

LINE MESSAGES FOR db2uredp.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2urexp.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.
SQL0001N Binding or precompilation did not complete successfully.

LINE MESSAGES FOR db2uimtb.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2ueiwi.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2uigsi.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2uiici.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2uiict.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2ugtpi.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2pctsp.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2dropv.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2ucktb.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2uqtpd.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2uqtnm.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2ulxld.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2uipkg.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2atld.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2clipk.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
SQL0091N Binding was ended with "0" errors and "0" warnings.

LINE MESSAGES FOR db2clist.bnd
------ --------------------------------------------------------------------
SQL0061W The binder is in progress.
172 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "960",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
176 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "964",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
181 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "968",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
185 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "960",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
188 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "964",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
191 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "968",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
229 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "960",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
232 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "964",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
235 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "968",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
238 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "2", SQLTYPE = "960",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
241 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "2", SQLTYPE = "964",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
244 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "968",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
247 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "960",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
250 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "964",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
253 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "968",
SQLLEN = "4",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
256 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "404",
SQLLEN = "0",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
259 SQL0804N The application program parameters for the current
request are not valid. Reason code "103". If a
host
variable or SQLVAR in the SQLDA is invalid then:
host
variable/SQLVAR number = "1", SQLTYPE = "408",
SQLLEN = "0",
host variable/SQLVAR type = "INPUT". SQLSTATE=07002
SQL0091N Binding was ended with "0" errors and "17"
warnings.
Bind completed with errors and/or warnings.


Since db2clipk.bnd binded fine (SYSSH00 created ok) , the application
test had run fine, but i'm concerning about db2clist.bnd.

Searching around, i found the following page
http://www.db2.jp/db2manual/en_US/in...d/r0007866.htm

So db2clist.bnd is about Common Static CLI Functions, but how is it
used by ODBC applications (how much is it needed/affects ODBC) ?

reading SQL0804N , reason 103
The length specified in SQLVAR.SQLLEN or SQLVAR2.SQLLONGLEN is
incorrect for the SQL type given in SQLVAR.SQLTYPE.

So it looks like type size problem. In this case, does DB2 convert the
parameter to the right size, or i'm missing something here?

Is there any recommendation/guide about connecting v8 clients on v7
servers?

Thanks

Alexandre