RE: ODBC and V4R5

     Did you uninstall the old versions of Client Access before 
     installing the Express client? I completely hosed my PC once 
     because I forgot that. Also, I think I saw similar problems once 
     when someone/something screwed the RDBDIRE. Use WRKRDBDIRE and make 
     sure there's an entry for *LOCAL.
     
     hth,
     Eric DeLong


______________________________ Reply Separator
_________________________________
Subject: ODBC and V4R5
Author:  "AIV" <SMTP:aiv@ctv.es> at EXCHANGE
Date:    1/25/01 12:11 AM


Folks,
we migrated from V4R1 to V4R5 short ago. As mentioned in previous 
messages we had some trouble with NetServer, POP Server, SMTP, ... but 
it is's all OK, up and running.
     
The only thing that remains is quite strange: ODBC keeps giving us 
problems:
     
As instructed by the documentation, we installed some CD (SK3T-...) with 
PTF's "before migration",  then installed new release, then latest 
Cumulative available, then DataBase Group PTFs, then ...
Everything went smooth, no problems, and checking with DSPPTF all PTFs 
show as installed Temporary.
We installed ClientAccess Express on AS/400 as part of the Release 
migration
Also installed CA Express in 3 PCs, one with Win95, one with Win98 , one 
with Win NT4.0 and SF64217 in all thre of them.
The rest of PCs remain with either CA/400 3.1.3 with ServicePacks as 
when were workin with V4R1 on the Host.
     
We have AS/400 NetServer , SMTP, POP, servers up and running.
Also, STRHOSTSVR *ALL gives no problem (except for the IPX message as 
before) and any PC operations like Transfer, etc work fine
     
Everything now goes smooth... BUT... we have tried ODBC with Access and 
:
     
(all Client Applications have the default access, as shown through 
OpsNavigator, and ODBC is allowed to everybody for all types of 
access... which we will restrict in the future, but left open now for 
the testing):
     
In all PCs, when using previous DataSources (*.dsn) and/or new ones 
created after (because of these tests), all "import/link" fail with 
message PWS0006 with some different return codes (sometimes # -235, some 
-7778, some 39765, ...)
     
One of the PC's, the one with CAExpress and Win98, can IMPORT with no 
problems, but can't LINK...
Strange enough, if we CRTDUPOBJ from any of the existing files and 
create a clone (!!!) in same or different Library (!!!), then no problem 
with ODBC, neither with Express, nor with old 3.1.3, except for some 
"special"(???) files that, for some unkown reason, will not work, even 
after the CRTDUPOBJ
And so on, trying different things, like CRTDUPOBJ, new DataSources 
*.dsn, etc give so many different results, we are LOST.
As for IBM, they have ckeck in their files and say there are no 
reportings like this.So, no available PTFs...
     
Any ideas, suggestions?
--
Antonio Fernandez-Vicenti
aiv@ctv.es
     
     
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com. 
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.

| Questions should be directed to the list owner/operator:
david@midrange.com 
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---