DSXchange

That might mean you imported the source but do not have an executable. What error do you get when you attempt to compile your routine?

Your routine isn't compiled or is defined incorrectly.

when i use line feed the output is as follows: 1|One|2|Two|3|Three2|Two|3|Three|4|Four| when i use carriage return, the output is as follows: 1|One|2|Two|3|Three| {spaces}2|Two|3|Three|4|Four| the problem still exists. Regards r How are you viewing your file? If you put a line feed in there it migh...

Most often this happens when there were still processes running when DataStage was restarted. Have your admin shutdown DataStage and ensure that all processes and connections are terminated prior to restarting. A "ps -ef | grep ds" should show any remaining processes. In addition, you can check usin...

When your company purchased DataStage they had the option of getting a support contract with the purchase either directly with the manufacturer or through a third-party support organization. Most companies will purchase this support contract not only to get telephone/email support but also to ensure...

To ensure your environment variables are kept, you need to run it as ". ./dsenv"

A database query can be called in a routine by using a DSExecute() call to your operating system to call whatever command you use at your terminal window to issue SQL queries.

It usually is much better (and more efficient) to do this with the appropriate DataStage database connection stage.

The "libodbc.so" is in the $DSHOME/uvdlls subdirectory, which should be set by the "dsenv" script into the LIBPATH environment variable. Either that has gone wrong or perhaps you don't have sufficient UNIX access to that library.

It looks like you haven't got your path set correctly. Have you executed the ".dsenv" in your project directory?

Hello Gautam, unfortunately job parameters cannot have their values changed once a job has been called. If you need to have a changed value visible in your job you could use the value of a stage variable to indicate the recovery status within a transform stage - I'm not sure if that adresses your qu...

You have a "Generate Columns" stage to add constant values, and I would think that you might be able to do some concatenation in a modify stage, but I'd have to check up on that to make sure (I'm not at a DataStage machine right now - but someone else might correct me before I get to a client workst...

Har,

I am trying to see what your scheduler thinks it has, this is better than posting your command line. If you enter the at command without any options it will show you what is in the schedule and how it has interpreted your submissions.

To answer the question you didn't ask - it's something 63 significant characters to the variable name.

To answer your real question

You can keep on adding length to DataStage variables until you run out of virtual process memory. The space is not allocated contiguously, either.

I seem to recall that the length can be quite long, but only the first 32 characters are used to differentiate.