DSXchange

Ramesh We use the HASH file stage mostly as a lookup stage in our DS jobs. this means that we populate the HASH stage with a key column and the detail columns required if a lookup is successfull. for example, we will place cust_id and cust_name in the HASH stage with cust_id defined as the key. When...

depending on how many records you are working with, you have various options open to you. 1. use the ODBC stage and specify the db and select USER defined query and paste this select into the SQL box. you need to specify the column names in the columns tab, once that is done you can run the select. ...

I am getting error insufficient privilege for unlocking inode. does your user have permisions to do this task? Im not sure you want to release all locks - there might actually be valid locks out there. Have you looked at the user reference manual for BASIC. I believe the site is documented on the f...

they prefer build a very large hash file which will be used along the whole process it is tempting to do that, but in the greater scheme of things it is not good practice. Rather have them plan the job design a little more. Do you have any ideas about my secon question ? Is is possible to define a ...

Can you also give more information regarding the manual strategy for unlocking the job. (this is how it is for Server Jobs. Paralell might be different) Using DS administrator. select project wherein the job is locked select COMMAND button type DS.TOOLS select 5 (Administrative tasks) select 4 (lis...

does anybody know if there is a maximum number of columns in a hash file. If its anything like a transformer then i would stay away from 1000 columns. I killed DS when i tried this with an occurs depending field from a CFF. We are working with Hash files which have more than 150 columns, and the re...

What I would probably do if I would write your job. Every day load the input file to a database table. Put a materialized view in place (in Oracle), or a automated summary table (in DB2) to do the aggregation. And look ma... no hands... aggregated values at the end of the month trust me - I would d...

I've seen sequencers that were also very complicated, and then one upgrade they just didn't work anymore as they should. :cry: Some of the things we now do couldn't be done with sequencers anyway (or would make the sequencers enormously complex). I'll keep my eyes open for this one - the sequener w...

ray.wurlod wrote:best is to make it automatic by enabling the DataStage deadlock daemon, which wakes periodically to check for deadlocks and also to clean up after defunct processes

Ray - this sounds great. which manual do we read to get on this!

For all the projects we are facing the following problem. How stable is the network? It could be that developers have jobs open, network conn is lost briefly and on UNIX the job is still 'open' but the client has lost the handle on the job. To test this, have a client ping -t server while developin...

lebos wrote:In our case we are using DS to convert from Sybase to Oracle.

Have you looked into proxy tables from Sybase DB side for this kind of transfer? It might be worth looking into.

strange syntax.
while waiting for support, can you write your own SQL - user defined?

could it be a right outer join that is somehow specified in the plugin? Without the plugin, i cant offer much help.

I like my old BASIC scheduling jobs too much. the code is great, but if you develop the code and then leave the poor client with BASIC code that is complicated to the untrained eye, you arent doing them any favours. Ive seen a pretty complicated sequencer a colleague of mine put together; and it wo...

Thanks ogmios I was reading about performance related issues with the bulk stage. I am going to suggest then that we write out SEQ files and use a generic load script parsing the .dat and table names to the script and have the script load the data. I wonder if it was a DB2 issue that they decided to...

Example.. JobName: Job1 Table to be loaded: CUSTOMER SOURCE ------- TFM -------- DB2BULK In the DB2BULK stage, the .sh, .clp and .dat files created are: uload.sh cmd.clp inpdata.dat JobName: Job2 Table to be loaded: PARTNER SOURCE ------- TFM -------- DB2BULK In the DB2BULK stage, the .sh, .clp and ...