DSXchange

The first command you should run prior to stopping the DS rpc daemon is netstat -a | grep dsrpc

if you didn't wait until the close/wait session disappears to stop ds, now you can check and kill the processes with the commands
ps -ef | grep phantom
ps -ef | grep slave
ps -ef | grep dsapi

Hi, i'm getting this warning message in one ODBC reference:
TRANSLATION FROM CCSID 1252 TO 937 NOT DEFINED

any help will be appreciated.

thanks,

Thanks anil, the port number was locked (:twisted: unexpected ).

Best Regards.

To pronounce that just do a copy/paste
(and believe me that is not one of my abbreviations)


I know that the bind error 7505 means a connections problem, but anybody know what 7500 mean?

$./bind20 dsnname
Package creation failed!: 7500

You need to set the correct Location Value, run the "WRKRDBDIRE" command on your as400 and use the one that is type *LOCAL.

You also need to set the correct Collection tables.

7505 mean that you have a wrong IP or Port number. To be sure about the port number, you should connect to the AS400 and see the port number for the DRDA listener. DRDA is the communicating protocol for communicatingwith DB2. To determine the correct port number, execute 'NETSTAT' from an AS/400 com...

It wasn't my intention to create confusion for dsx users (sorry DSXchange users)

:D

u r wlcm.

by the way to test the driver you should go to "branded_odbc/bin" directory (instead DSEngine/bin -sorry) and run ./ivtestlib DriverName

mat

you can find the pdf " What's New In DataStage 7.5.1.pdf " in ascential developernet site, under File Library -> Documentation or Instructions.

mat

Hi, did you try to test the connection and the driver? cd `cat /.dshome` . ./dsenv cd ../branded_odbc/demo ./demoodbc ./demoodbc dsnname -uid username -pwd password (or run ./bin/dssh and then >LOGTO project_name >DS_CONNECT DSN) then test the driver cd DSEngine/bin ./ivtestlib DriverName for AS400 ...

1- check that you are using the same hash name.
2- check that you have the same metadata structure and the same column number.
3- first column should be a key.

If these dosen't help... delete the hash file and create another one.

good luck

Hi, thanks for your aswer.

That is what I found: In the .odbc.ini file, the SqlServer driver options contains a property called "QuotedID". I changed the default 'NO' to "" and this solve my problem.

Hi Rajasekhar,

you can track the phantom in the PH file. Also when you reset the job in Director you get the line "From previous run" with more detail.

Matias

After we migrate an ODBC conection from sequelink to wireprotocol, the quote character in the sql statement change from "" to 000. Is the same database (sql server), so i asume that this configuration is at driver level (?). Anybody know how to modify the default quote value in the datadir...

It could be related with your Ora stage or constraint key violations (but it shouldn't), because the DSP.Close is the routine in a plug-in that is called to close it and the ORA plugin seems to be closed by this routine. Did you try recreating the stage? I'm not sure what "Error -2" means,...