DSXchange

That must have been it - plus there was a pesky unassigned variable print message that would cometimes trigger jobs to have a warning status when in fact they didn't.

DataStage opens the command window with teh attach point being the project directory; you will need to specify absolute paths in your command for it to find the files it is looking for.

Yes, you can use the DSGetLinkInfo() call to get that information. If a job has a passive to passive layout, DataStage will automatically insert a "dummy" active link between them. I use the DSGetJobInfo() to get the list of stages in a job to get the names actually generated and used.

I guess that the question about the PRINT statement generating job run warnings at 7.5x has been answered as well

Are you sure that you are entering the Administrator client as a user with DataStage administrator privileges? Do you have both sufficient privileges as well as enough disk space in your DataStage project directories?

I'm curious as to what the experts are saying about the use of stored procedures. There are some cases where a stored procedure is the only way to get things done and many where their use is going to slow jobs down.

You cannot use an after-job routine to do this. If the job gets aborted for whatever reason the after-job subroutine will not get executed. You will need to call the DSGetJobInfo() routine from the sequence that started the job which you want to measure.

Arun, the operating system is trying to execute a fork() and can't. The fork() call is used to spawn new processes from a parent {it actually duplicates a processes' complete memory space and starts a duplicate process}. If this error happens every time you run this job then most likely you have hit...

Ianm, do a full export of all your routines into a .dsx file and search for that string, or perhaps a search for "no time" might help too, that looks like a string constant. If you search for "PRINT " you might narrow it down as well - production DS code shouldn't contain any print statements; I use...

Ian, are you sure that you are running 7.x? I recall that if you put "PRINT" statements into program code in prior releases it would print the information in the phantom log file but also trigger a job warning. I am fairly certain that this doesn't happen at version 7. If you can locate the line in ...

Hello Aneel, the SEARCH facility in this forum is quite powerful, I search using the subject line of "The connection is broken (81002)" and got 48 matches! There are several common causes of this error. If you only get it when accessing the table definitions and not other parts of the repository it ...

Bala, you didn't really ask a question, just posted a statement. I will assume that you would like to know why PX is giving you this warning. It has to do with the partitioning, or lack thereof, on Sequential files as well as your lookup file set partitioning options. The message is perfectly normal...

Raj, <sigh> you can use the merge stage, it is up to your job design on what is considered to be the "middle of mapping". If you write to two sequential files (which can also be named pipes to save on disk I/O) you can then read from those using a merge stage in the same job; this is an accepted and...

sudhakar, please take a step back and tell us what you want to do and perhaps why you think it needs to be done. The quoted post you included contains the DataStage TCL commands to reset ALL read-only attributes for ALL objects, routines, transforms and data types and is something you should only do...

Raj, PLEASE read the documentation on the merge stage; it does not accept input links but uses input sequential files to do the type of join you want; so you would need to get an extract from the database table into a flat file to make that work. The hashed file lookup suggestion might perform bette...