DSXchange

What exactly is the question you have; from your captured text output the SELECT command correctly output both your jobname and category name separated by one (or more) spaces.

That is not good at all. Make a backup of the directory now (just to be on the safe side). Can you think of any condition in DataStage or the System that happened between the time your project was OK and now?

You can certainly give it a go. The best approach to take is: 1. create an empty new project on the new machine with the same name as the original project and with the same absolute path. 2. copy the original project directory and subdirectories to the new machine and make sure to include all hidden...

This means that the references inside the repository are incorrect. The most common cause of this error is broken indices. You can reindex the project using the Admin command tool or the TCL command line and enter the "DS.TOOLS" command to get the menu, then choose the option for "reindex"; you need...

The core file that controls a DataStage job's runtime configuration is the $APT_CONFIG file. There is usually a default file that your jobs point to, but any PX job and point at it's own configuration file with a different number of processing nodes.

Ken - IBM's use of dynamic LPARs is a good example of quickly and seamlessly changing CPUs from one UNIX instance to another. It takes seconds and is great for load balancing. Unfortunately, shifting the memory back and forth is an entirely different matter. It can take a large part of an hour to sh...

New2DS,

If a question has been asked and answered many times before then no matter what the status or level of the poster the answer should be "please use the search facility" or "see post xxxx". Being a premium member does not mean that one doesn't need to check the forum for prior answers.

The tool with which you write a routine in DataStage not only allows you to write and compile it, but it also has a "test" button which lets you call it independantly from a DataStage job. and to pass parameters to it. This is what is used to debug most routines. The DataStage engine has a source-le...

If you are running the job, the status is the integer value of the return code.

If I issue a "dsjob -jobinfo {project} {job} >> abc.txt" the information gets written correctly to the abc.txt file.

If you only want the status, I think you don't need the "-run" in the command line. Does it work correctly if you don't redirect your output?

The DataStage compiler will put a dummy active stage between two passive stages such as your job has ( ODBC -> Sequential). Could you put in a transform stage that does nothing but pass the input to the output and see if the error persists? If not, then it sounds like a bug, if yes, then it might ma...

It should work even in DOS, what is your "dsjob" command line?

Job logs are not stored as UNIX files; they are part of UniVerse hashed tables. Access to the log information is through the visual information presented in the Director, using a routine such as the DSGetLogInfo() call in BASIC or through the UNIX command "dsjob", which has several options to help y...

Vinod, urgent request need to go to your support provider. Nobody responded to your original question because the answer is not self-evident and more information is need to try to diagnose the issue. Error - 1213 seems to be "invalid number", but the error seems to be happening when the system is tr...

We have just had the same problem on our system, that the error message "...interrupted system call..." is cropping up. In our case it was in a multi-instanced job in which some of the instances ran through without a problem and others did not. After much looking around we discovered that the proble...