AS400 -> Win NT ODBC -> MS IIS connection ???

[Joel Eikenhorst]

Lieven De Samblanx wrote:
>
> Hello,
>
> We have an RISC AS400 V3R6, an Win NT 3.51 server with microsoft
> internet information server (MS IIS).
> I installed CA for Win NT (september bčta).
>
> We want to query the AS400 via a intranet browser (MS IIS should
> execute a script, querying the AS400 via ODBC)
>
> I created a user 'ntserver' with enough privileges, a file GUFILE with
> several fields including GUVN01 and GUAN01.
> On the NT server I created the 'Web SQL' (system)datasource
>
> * when I connect to the AS400 on the NT server, I can query the AS400
> via ODBC and retrieve the data from the GUFILE file.
>
> * when I connect the MS IIS (via a browser) and try to execute one of
> the scripts to query the AS400, I get nothing but error messages.
>
> ---> the script used :
>
> Datasource : Web SQL
> Username : ntserver
> Password : ntserver
> Template : viewbook.htx
> SQLStatement :
> +SELECT GUVN01, GUAN01
> +FROM GUFILE
>
> ---> when I try to connect (with a browser) via MS IIS :
>
> - when I use a datasource that doesn't exist (I change 'Web SQL' in
> 'Web'), the error says (correctly) that the datasource does not exist.
>
> - when I use the correct datasource I get the error :
>
> Error Performing Query
> * [state=08S01][Error=-3][IBM][Client Acces ODBC Driver
> (32-bit)][DB2/400 SQL]Communication link failure. COMM RC=0x3
>
> ---> IBM does not know of an error 0x3.
>
> Can anybody help us ?
> Does anybody know how to query the AS400 via MS IIS ?
> Or knows what the error means ?
>
> THIA.
>
> Lieven De Samblanx.

The failure happens because the ODBC driver attempts to access
configuration information about the connection, from the current user
registry key. Since IIS runs as a NT service under the profile of
"system user" the current user profile is set to .default. Since there
is no configuration information available under the default user profile
the connection fails. I've tried copying the configuration information
from a different user then setting the permissions to all access for
anyuser and have gotten closer, but still cannot make a connection. I
saw something about being able to run IIS as a console application. If
this is possible then ODBC drivers should be able to make the
connection, but I've not had time to try this.

[cl mcrae]

Communication Link Failure COMM RC=0X3

This can mean any of the following:

· The user ID is missing or not valid.
· The password is missing or not valid.
· One or more of the socket servers is not started.

How to check host socket server status
How to start AS/400 host socket servers

· An AS/400 connection is already active under a user ID different from the one you are trying to use for an ODBC connection.  There are three ways to correct this:

1 Use the same user ID as the one shown as the current user in the AS/400 connections window.
2 Make an ODBC connection to a different system.
3 Use the AS/400 Connections window to disconnect the selected system.  Then make the ODBC connection with the users ID you want to use.

How to connect an AS/400 connection
How to disconnect an AS/400 connection

'copy and paste' from the Client Access Users Guide Help System. The shortcut is in the Client Access folder. Get there from Start/Programs... Search on '0x3'

 cl



... snippage ...

[Robert Foyle]

Try downloading the dbweb add-on to IIS from MS. It supposedly
allows access to any database via ODBC through IIS.

I haven't actually done it but in theory, it should work with ODBC to AS/400.

Bob Foyle

[Lieven De Samblanx]

"cl mcrae" <cmc...@powerbond.com> wrote:

>Communication Link Failure COMM RC=0X3

>This can mean any of the following:

>· The user ID is missing or not valid.
>· The password is missing or not valid.
>· One or more of the socket servers is not started.

You are right, the error message is mentioned in the CA for NT help
file. This was the one I did not try . (I searched the CA for W3.1
help, the online books on my CD, called several people and even IBM),
because it resides on the NT server wich isn't that easy reachable

I do not have the sulution to my problem yet, however. But the
postings from Joel Eikenhorst and Robert Foyle allso contain some
interesting tips (thanks to all).

I am going to try all (if there are still other suggestions, please do
so !) next week. Keep you all informed (if you want to).

Lieven De Samblanx.