DSXchange

You got mail. Also, here's the skinny of what I did: [row generator] -> [transform] -> [peek] In Row Generator, provide a single field of a VarChar(whatever), and provide the hex values on the "Edit Column Meta Data" (Columns tab, double click on #1). In Transform, output the regular field...

Actually, in my experience with Tru64 and AIX (unsure about other OSes), kill -14 have been very successful in telling DataStage, "Hey, clean up your stuff then close down." Just killing the "dscs" process (the parent process for DataStage client session) will unlock the jobs for...

Umm. You can contact Ascential about this. After all, it is an evaluation copy they provided for you to determine whether you should buy DataStage for your company, right? Right? Trust me, they will definitely be glad to help you make sure everything's working because they definitely want your busin...

I wonders what "MX" stands for. Mex? "A hex on your mex!"

Whoops. Duplicate posts.

Sounds like an interesting challenge. You will most likely need to split the process into two separate stream, obtain your necessary information on the alternative stream, and then match the resulting information with the main stream. Ray's suggestion of the Aggregation Stage is also my suggestion t...

1. APT_STRING_PADCHAR plays a very important part on this. 2. If you want to use NULL as a value to identified failed matches, you need to ensure that BOTH input and reference link fields are Nullable, along with the output link field for the lookup. Yes, you do need to set the 'Continue' option as ...

Plus just killing your process is far easier. Just find the dead process and do a kill -14. Never a kill -9. EVER!

99.99% of the time, it solves the deadlock problem for me.

The dataset itself already contains the configuration information. Take a look at its header file (although it's pretty garbled, you can see the important parts)

Are you running DataStage in MPP mode?

If it works fine...

Then it works fine.

This is not really a DataStage question. This is more of a "How does things work in this company" question, where administrators, your managers, and other peers would have FAR better answers than us here on DSXchange.

Even the pro know to ask the people within the company.

nodes != CPU.

Nodes = Processing flow.

Please read up on Parallel Extender Configuration File (Chapter 11) on your DataStage Manager guide (man_gde.pdf). By reading this, you will gain an important insight on how Parallel Extender (EE) works.

In Version 6.x, it was required, at least up to 6.0.2.

In Version 7.x, it is not required.

Suggestion:

Why don't you just try it yourself instead of asking us? Create a Dataset file without the .ds extension. If it doesn't do what you expect, and you don't know why, THAT is when you ask us.

This question goes along with the e-mail from RStone posted March 3, 2005. Is there a way for Datastage to communicate with Unix to initiate a script? Yes. There are a number of methods that you could use (before job, after job, ExecSH, execute command, et cetera) to call scripts. Please feel free ...

You either have way too much time on your hands or your screen resolution is way too low. =P

Nerd.