DSXchange

Using search you could have found viewtopic.php?t=115038&highlight=code+141

The first thing you need to do is to get a DOS command working; once that functions you can get it working from DataStage. There are several compression packages available, from the old PKZIP to the UNIX type gzip, compress and bzip. Which one you decide to use is up to your site.

You have 2 issues, one is just that the date is being displayed in another format, and that has nothing to do with the contents. The other is that you seem to be losing the time portion. This could be either display format related or be happening when you modify or fill the column. How are you doing...

Yes. But no method that I can think of is easy to implement and would be silly to use - i.e. putting in a dummy column with a fixed value of 1 and then using some other stage such as a modify to perform the action.

"improve" is vague term without knowing which metric to improve. The transaction frequency is probably a synonym for "commit frequency" and refers to how many actions are bundled together to form an atomic transaction (this is a common database term). A transaction is neither goo...

What stage type is generating this error?

With just 4 formats you could use a transform with the following logic If position 5 is a '-' then convert with '%yyyy-%mm-%dd' else if position 6 is a numeric digit user '%dd-%MMM-%yy' otherwise use 'xxx'. I can't remember how to specify 1 or 2 places for the day in PX; I know I haven't found it in...

try opening up an DOS (cmd.exe) window and trying it; or changing your settings to not automatically close windows upon completion. It looks like you don't have "cxx" installed or in your path.

Awesome link!

Are your date formats limited to the four mentioned, or are they only examples? When it comes to this type of conversion effort, I would prefer to use a Server job, if the customer and configuration allow it; since it much simplifies the logic required - Server has the ICONV() function which is very...

What is the data type? The display format is independant of how the data is actually stored; this is what I am assuming your problem is. What tool are you using to display your data?

You can do it easily from an after-job call. Just do an ExecSH and pass the ZIP command to the command line. If you are using WinZip you will need to download their command line extension.

There is only one command "cxx", everything else in there is parameters. What happens when you just try "cxx" from the command line?

Did you try to kill the job from the DataStage front end or via the command line? In this case I also recommend to activate the deadlock daemon and let the system take care of the problem for you. Edit your $DSHOME/dsdlockd.config file and set "start=1". After that, you can start the deadl...

Perhaps the wrong version of the compiler, or the wrong compiler. What is your error when calling from the command line?