DSXchange

Sure. Set up a link to a sequential file that your 'red' records get sent down. After that there are different ways to solve the next part of the puzzle. You could write an 'after job' routine that uses DSGetLinkInfo to see how many rows went down that link and then, if it is greater than zero, use ...

i need to run datastage jobs from unix. Ok. That's what the command line utility dsjob is for. if i scheduled a job from datastage and i use a command crontab -e then i should see that job scheduled right! if it is wrong correct me. Correct - as long as you are logged on as the same user used to sc...

UserVariable activity? Must be one of those magical new things in 7.5 I have to look forward to.

Kim, the 'buffering' issue *was* a performance related server side bug with row buffering and is unrelated to anything crashing on the client side.

And 7.5A is older than 7.5.1x, so that fix would be incorporated in the version you are running.

I have yet to see much of anything 'super' about our SuperDomes. What are the specs for your machine - CPUs, ram, etc? What other things are running at the same time as your DataStage jobs? And as Kim notes, there are many factors involved and disk I/O issues can really put a kink in your hose.

You can't 'update' Job Parameters once a job starts. But what you can do is initialize a Stage Variable to the value of the parameter and then manipulate that. You can then pass the final result out via the UserStatus area which the Sequencer can automatically pick up and use as a Parameter for anot...

I don't rely on it defaulting to something on its own - I always supply a Default Value when defining them. Then there's no question about what it is or what will happen the first time it is used.

CLOB fields are not supported, especially not ones that big. I would guess that is the heart of your problem.

What happens if you take this field out of the metadata and don't try to process it? Does it work fine then?

It's all spelled out in a couple of pdf documents you have on your client pc. Check the DataStage Plug-In Installation and Configuration Guide plus the ORAOCI9 reference itself. I'm assuming you have the Oracle client software installed on the DataStage server. If not, that's your first task. After ...

Integer, string - doesn't change what the transformation needs to do. Just put the result into a string field and you should be fine.

Nice.

Or use the Transform NullToEmpty in the comparison:

Sure. At some point, we all have to decide when a VC project gets 'too big' for our particular needs and then do something about it. I didn't consider that as 'periodic maintenance' as it's nothing I worry about on a regular, recurring basis. I've only felt the need to do this once in the last three...

There are two types of annotations, a description annotations displays the job description field and you can only show one of these. I would think this is the issue. As Vince notes, once you add one of the 'Description Annotations' to your job it becomes greyed out on the menu as only one can be us...

Asked and answered in the Server forum. Why post this again here?