DSXchange

The Manager will show you last modified. Search the forums for DS_AUDIT for examples of what activities are tracked by DataStage.

He can't with NLS enabled - here is the original thread where that came to light. With the assumption that the data will be in EBCDIC with NLS enabled, perhaps you actually have ASCII data in the file and now they are getting converted to garbage? Can you look at your source file outside of DataStag...

Depends on what section you found it in - 'Fixed in this release' or 'Known issues'.

If you are US-American and you beleave - as nearly all co-citizens do - fully that neither behind pacific nor behind atlantic nor behind the great seas in the north nor behind the caribean sea there is any kind of intelligence than you can leave it untouched. Come on, don't hold back... tell us how...

attu wrote:No one can edit or compile jobs or execute them.

So... would this be some kind of 'archival' project?

It would help to search for 'infinite' rather than 'indefinite' as well.

Can't help you there. Is your install disk... full? Or highly fragmented, perhaps? Anything else behaving oddly or literally just this?

Checkpoints are a feature of Sequence jobs, is that what you mean? I don't see how that could take anything other than moments.

Yah... still trying to nail them with that rusty six inch nail, I see.

Ah... one of those 'gory details' people don't seem to want to burden us with. Perhaps the question is: is there an equivalent in TeraData?

I guess 'INPUT VAL' is what you substituted for the actual parameter markers in the job? As Ray notes, you'll need to use a different name for the second version of the 'same column' to hold the old value. Then custom sql is required to map everything into the corresponding parameter markers so you ...

gillu wrote:Both sequencers are "Any"

Double check. That message only comes from 'All' Sequencers in my experience.

Silly question, but why not just continue to do that in Oracle?

swati1_sinha wrote:Any suggestions???

Search. It's been discussed here a number of times.

Which job are you checking? The current job? Then use DSJ.ME for the handle. For another job, you'll need to 'attach' to it first to establish the handle and there is a specific function for that. However, you'll need to write a routine to handle all of this correctly - attach, get job information (...