DSXchange

You're losing data because 000012345.00 would require decimal(11,2) rather than 9,2.

Try setting the APT_OSL_PARAM_ESC_SQUOTE environment variable to preserve single quotes in job parameters as outlined in the tech note:

IBM InfoSphere DataStage reports error when using parameter with single quote in a SQL statement in any Database Stage.

See above.

Right click, stage variable properties, it will open a metadata table. In there you can also choose to set initial values. Stage variables are executed once per row in top to bottom order. Here is some pseudo-code example of one way (run this in sequential mode after you have sorted according to you...

When you login, enter the host name rather than the IP address, then you know. Also check the title bar of your client any time to verify which host.

Stage variables can do that. What did you try?

I still see the same info in 8.5 with the same commands. I see project locks, jobs locks with job names, RT_CONFIGxx locks, RT_LOGxx locks, etc. You may not always see the job name. If you only see an RT_CONFIGxx entry, you can take the xx number and determine the job name if you need to or just unl...

Compare dsjob's file permissions and ownerships as well as users and their groups across both servers.

DataDirect 6.1 ODBC drivers do offer native / bulk load for SQL Server. It appears that DataDirect 7.0 and 7.1 versions are also available. It looks like you're on Windows platform. I think if the Windows ODBC drivers say IBM, they're still made by DataDirect. Someone can correct me if wrong. Mabye ...

:idea: Clearing &PH& weekly is good if the project has a high level of activity. uvsh / dssh / DS Administrator project command (run per project): CLEAR.FILE &PH& A few related tech notes: Commands to delete files in &PH& directories in IBM InfoSphere DataStage Clean up space...

If you are licensed for IA then you could create a new DS project for IA with some other project name, point IA to it, and delete the default project.

On columns tab list the column names and data types according to how your query returns them. The metadata should take into account any column alias names or casting of data types from your SQL.

Check your client docs (PDFs) for a Programmer's Guide if it exists or not. Many of the command options given in the above link will work on 7.x.

I think changing file owner 23186 in your specific case to dsadm is fine. Just backup the system before making any massive changes, especially recursive changes.

Good, then consider upgrading to DataDirect 6.1, the release bundled with 8.7, or DataDirect 7.0 or 7.1 which appear to be the most current releases as of now.