DSXchange

Welcome aboard. :D Segementation fault covers a wide variety of possibilities; in Windows terms it's like an access violation - an attempt to access a memory address not owned by the process. It can - for example - be caused by trying to put more than N characters into a string[N] or string[max=N] f...

Right. 10 seconds is way too long. But a NAP of 100 milliseconds wil relinquish the CPU to another process, and be close enough to immediate as makes no odds. Even 500 milliseconds probably wouldn't be noticed. After all, you don't use Wait For File in real-time enabled applications.

True, too true. Just got out of bed early Saturday morning. You know how it is.

Check the "job starting" entry in the log file to see what parameter values are actually being passed.

None, really, apart from import into a protected project.

Put a short SLEEP (or even a NAP) in the ELSE clause of OPENSEQ, otherwise this routine will eat lots of CPU cycles.

The StartLoop activity can be set to process a "list of things". The list can be generated by any means, such as a regular expression or a script. Read the manual chapter or on-line help on StartLoop activity.

Is your client Windows XP SP2? If so, you might need a patch from the DataStage vendor.

Is this a server job (as per the original post) or a parallel job (the forum on which you posted it)? If you reset your change does it work again? If so, the change is the culprit.

Are you posting on both fora because you can not read from OCI stage both in server and parallel jobs? Doesn't this give a faint hint as to the cause? Oracle client configuration, maybe?

That answer is not correct. The Tunables values are the default (not maximum) size to be used for hashed file cache - not hashed files. What you set in the Administrator is the default value; these can be overridden on a per-job basis using the job properties dialog. The upper limit is theoretically...

It doesn't.

You can disable prompting for specific parameters by going to Director and selecting Set Defaults from the Job menu. The rightmost column in the grid is the "whether to prompt" flag, and can be set to "Y" or "N".

Moderator: please delete this post. It does not belong here. It is a duplicate of one posted and answered in the parallel forum.

You don't automate Version Control. It's intended to be a manual process, with some brainpower involved. You have to think up a meaningful description of the promotion batch, for one thing! You can't automate creativity.