DSXchange

Pavan,

the -s <size> lets you specify the size. The exact description can be retrieved by checking the man pages for xargs. I think this does differ from environment to environment and also on different platforms.

And your command is running correctly when you manually test it from UNIX with the appropriate values? Might you use the xargs -s option to get this to work? It doesn't seem to be a DataStage issue here, just a UNIX one.

This type of lookup is common so there is no technical reason why it isn't working the way you expect. Could your key contain leading or trailing spaces or perhaps unprintable characters? You can confirm that it doesn't have that data by putting in a dummy output link with a constraint looking like ...

I'm not quite sure what you are looking for in this case. Each project has it's own DS_JOBS hashed file so you cannot directly query this file across several projects.

kollurianu, If you put this in a test routine you should know what the result is when you put in an empty and a null input string. The "D/E" format is European and will format to and from a date with order day, month and year with a "/" separator. This is not your source date and therefore it isn't ...

RaviM, this is a volunteer forum; the terms "urgent" and "ASAP" have the effect that many of the real experts won't even bother to respond, or will wait a day or three. If you have an urgent problem then go to your support provider - you are paying them for the privilege of getting ASAP responses. I...

the error you are getting is coming from the UNIX command xargs. The command that you are generating is bigger than what your environment can handle.

What are you doing in the stage "GridFiles"?

Your "after-job" call is causing this error and aborting; which explains why all the records have loaded.

What are you calling in your after-job routine?

ICE, there are different ways of getting a job's status and the 3 most common means have been touched upon in this thread: 1. Read it from the Director 2. Retrieve it from UNIX using the dsjob command 3. Retrieve it from insideDataStage using DSGetJobInfo(). None of these seem to work for you and I ...

Chandra,

in your Manager you can use the standard windows functionality of selecting, dragging and dropping. If you select one or more elements and right-mouse-click you will find the "move to" that Ken has referred to.

The program that is failing at line 122 is DSP.OPEN (I wasn't paying attention to your first post...); at line 122 it issues call to the globally catalogued routine "$DSP.Open"; so the line number doesn't help much further.

Are you able to get any MSOLEDB stage to work on your system?

Out of the context of your environment this list isn't useful. It is better for you to use the unix fuser command on the file DS_STAGETYPES/DATA.30 in your project to see which other process might have the file open. Once you have that pid you can see what sort of process this is and take it from th...

What functions/derivations are you doing before your first "decimal_from_string "? Can you remove columns that perform more than a straight field copy one at a time until you identify the one causing the problem?

Both statements will work. If C_ACCT is a string then the right-hand side will also be converted to a string and a string comparison done; if C_ACCT is a number then the opposite is done. In order to speed up runtimes it is best to avoid implicit type conversions so try to avoid unecessary conversio...

Is this the only job with an error in compilation or do you have aproblem if you create a simple dummy job as well - in that case it would lead one to believe that the configuration needs to be corrected as opposed to a problem in the one job.