DSXchange

Please post the generated OSH script.

Thanks,
BP

Sometimes a really long OSH script (generated by PX, in your case) can lead to random timeout errors. Two suggestions: 1. Contact your ASC rep and ask them about an undocumented environment variable called APT_TIMEOUT (or something similar). You maybe to set that and run your jobs to completion. 2. ...

Are you sure this is a DataStage problem? If you write to the table outside of DS, does the table get a read-lock?

- BP

Does your SMP and your MPP have the same C compiler?

- BP

I would like to see an "Uncheck All" radio box on the "Column Display" window in the View Data screen. It's a real pain to go through a 100-column table def and uncheck 99 of them so you can see the one column you want.

- BP

If the timestamp column is fixed width, you could read it in a character string and just manipulate the characters that encode the hours.

- BP

Can you pass the reject link to another transformer? If so, try this --> rejects --> sequential_collection --> transform -->db2 In the transform, set the id = OUTROWNUM (which I believe is available in the PX transform, if not - use the server transform). Please see a post in the PX forum regarding ...

I think you're right about the jobmon.. It might be 'timing out' b/c nothing is being sent to it. I don't know exactly how to turn off the job mon, but if you root around the PX Engine bin and utilities directories on the server, you might find a script related to jobmon. Then, you can back it up an...

Please post the entire error. Which compiler are you using? What kind of UNIX OS? Also, please post the generated transformer code.

Thanks,
BP

For Server Jobs, using hash table lookups has been considerably faster for us than looking up straight to Oracle. I had a job with 6 Oracle lookups and it took 9 hours to complete. I replaced the 6 Oracle lookups with hash files, and the job took 6 minutes.
-BP

FYI.. back in the day, the output of a OSH step (a smaller unit of work than a PX job) could be put into a virtual dataset. The virtual dataset was kept in memory and could be used as an input to multiple OSH steps within an OSH 'job'. Unlike a server hash file, it couldn't be used by other jobs. Ma...

All- I used to believe that tsort was faster than sycnsort most of the time, but from the recent posts, I'm wondering which is truly faster. Maybe this community can come up with a heuristic for determing when to use each sort. To do this, I propose that PX users post sort statistics, and then we ca...

Ken, Thanks for your help. I do have a '#' issue on the #pInputFile param, but I fixed that and it still doesn't work. I have tried doing: sed '1d;$d' path/file >> path/newfile and it works file.. Which set of quotes do you think is the problem? The set encasing the entire statement (it was generate...

I have seen a PX FTP stage in the works that does exactly what you want. You might want to ask Asc engineering for it. However, I agree with Ken that your best bet is to land the files to your server before your ETL process starts. What happens if the FTP connection is suddenly cut? Then PX would pr...

Thanks for all the input. Below is an example of generated sequence code in which there are 2 execute command stages (at L$5$Start, L$6$Start) and one JobActivity(at L$4$Start). In this example, both L$5 and L$6 use params to generate commands. L$5 always works (i.e. the before_count log gets create...