Thanks for the info.
I am moving right along, again.
I downloaded and upgraded to 5.0.1. It only took about 24 hours.
I downloaded and installed WSAD 5.0.1. Interim Fix 003.
As Kyle predicted, the old bug has vanished.
Now there's a new one.
Sure wish I could copy and paste the error message.
[IBM][CLI Driver]SQL1013N The database alias name or database name "SAMPLE" could not be found. SQLSTATE = 42705
If I remember right I created a sample ( lower case ) from the command center. Sample is listed in the Database selection box as shown in figure 24.7
I select the database box and strike F1 ( Help ).
A yellow box appears, three hotlinks DBs, DB Conns, and Connecting to DBs.
Click DBs. it says ... You can define the name and type of the database, and select a project to store the database design. Once you add a database in the Data Definition view of the Data perspective, you can add schemas and tables to the database. ....
In the data definition view there are what I suppose is a bunch of open projects: OIDGen, TimeApp, TimeAppTestClient, TimeSheet-AppLogic, TimeSheetGroup, wasbook and wasbookServer. Just for fun I created a database under wasbook. Should I have created more? Do web and ejb projects generally need databases associated with them?
Search for "SQL1013N" on the WSAD Library page returns 49 hits. The best of the freely available is this FAQ page.
from that page A: The SQL1013N error indicates that the database could not be found in the client or the server database directories. The net driver will use the native libraries on the server, so it will be using the server database directory to locate and connect to the remote database.
The SQL1013N indicates that the net driver is unable to locate the database. Ensure that the database URL is correct; that is, the server name and database name are correct. Also ensure that the DB2 JDBC Applet Server on the server is running on a port that does not conflict with port of another process (i.e., the port numbers should be different.). By default, the DB2 JDBC Applet Server on the client is started on port# 6789 when the 'db2jstrt' is issued. In this case, it is most likely that the DB2 JDBC Applet Server's port is conflicting with the port of another process, since the remote database is accessible from the DB2 command line.
From figure 24.7 my connection URL is grayed and reads jdbc:db2:SAMPLE. No way appears possible to set the host
from the info center is interesting too. Use the Client Configuration Assistant on your local machine to create a database alias to the remote server.
What's that mean?
[ March 29, 2004: Message edited by: Sondra Colagrossi ]