DSXchange

I am at a different client now, but as I remember well, it had something to do with the ODBC connection from the production server to the SQL Server.

I am looking for a way to start my sequence depending on the existence of a particular row in a table that has certain characteristics. When some processes on our AS400 have finished, the AS400 sends a row with Rundate and a status to a table in our DB2 database. When this row is inserted in the dat...

If you go to the Inputs tab of the Sequential file stage and then the General tab, you can click Overwrite existing file. To me this is the same as deleting the old file and making a new one with the same name and specifications.

In version 7 of DataStage we used the Reporting Assistant with our own DB2 Database. There was a .dll supplied to get this to work. In version 7 all worked fine. We use a reporting tool (impromptu) to read from the DS tables. However, recently we have upgraded to DS 7.5. The reports still work, but ...

Thanks for your help. I have solved this issue and it was indeed simple: In the Execute Command stage I call a batchfile. This batchfile contains 1 line: db2cmd /c /w /i db2 -tvf d:\ascential\datastage\runstats\interface_tables.sql Because of the use of /c /w /i it now waits before the statements in...

I am using the conditional trigger, the wait for file stage is set to wait for a file to appear before continuing. However, what I want to accomplish is that this file appears only if a script with statements has finished running. What happens now is this: In the command stage I have this command: D...

This should be really simple, yet I am struggling with this: During a sequence, I want to run an SQL Script with statements to perform runstats on various tables. This is no problem, the SQL script containing these statements can be called from an Execute command stage or as a After-job subroutine. ...

On our test server I use MS SQL Server Load stages to Bulk load data from DB2 to SQL Server in a number of jobs. I have exported these jobs and imported it on our Production server, and without changing anything other than the connection to the correct DB2 database, I now get the errors: MS_SQL_Serv...