DSXchange

Worst case just type them in. Or if you have the Oracle metadata imported and stored, drag it from the browser to the link in question or 'Load' it from inside the stage.

I would imagine it will be frustrating, have you involved your official support provider yet? And keep in mind the fact that 'resources' can involve more than server CPU/disk/memory, there's also internal DataStage resources and possible engine configuration issues that could come into play as well.

My understanding is that the information about your DataStage jobs are stored in both places, and logs can be in one, the other or (seemingly) both as well but I don't think anyone would suggest storing logs in both places. The log options come with 8.1, for 8.0 they're still in the Universe reposit...

Did you not do the search I suggested? The cause and solution have been repeated here many times, and as noted your 'dud data' is a Field Mark.

Well... there very well may be but you'd need to better explain your needs and what precisely this 'control job' did for you. There are always other approaches, up to you to decide what's "easiest" or "best".

It will only store "one" value and yes, overwrites so last one in wins. Most people use a delimited string to pass multiple values and then parse out the appropriate piece for each parameter.

Would that work for you?

That's... odd, so no clue why it thinks you've got a decimal on the target end? When I've seen unexplainable things like this, I generally delete the stage in question from the job and set it up again from scratch and that typically resolves the issue.

Worth a shot here.

Excellent. :D

Hard to tell for certain, but it sounds like a job for the USERSTATUS area. See if an exact search for that and/or DSSetUserStatus helps you out.

While that used to be the case, the last time I checked with support they insisted that they needed to exactly match. Otherwise they mostly work OK but expect to have... issues. I did.

Ah... thanks for posting that!

That's a limit of your operating system, not DataStage. Talk to your SysAdmins to see if that limit can be raised.

Nope.

You've got no control over the filename aside from the "base" name that is used, and the trigger option will always append an incremented number to every file other than the first one as you've seen. I've been in the same boat where I needed something different, name-wise, for the various ...

Exactly. And if you look at the transform code you'll see they're both just wrappers for the OConv function, something that's easier to remember and self-documenting.

Please mark your post as Resolved using the button at the top of the page.