DSXchange

Just do it. Declare it as a parameter and enclose the parameter name in hash/pound signs in your derivation.

From the manual:

To implement a DOS newline, use the Record delimiter string property set to "\R\N" or choose Format as -> DOS line terminator from the shortcut menu.

In other words, nothing specific for timezones exist, you'll need to spec out and write your own.

There was no suggestion, simply explanation. You need to decide how long of a wait is appropriate and what happens when that time expires without the file arriving.

Interesting, it's different for HP-UX, PA_RISC v. Itanium? I'll have to remember that.

I'd wager you could find something locally or online as well. XML is XML, DataStage or no.

thanks craig..so I guess it wont be staraightaway possible to replace the job design with the recent version of it from a versioning tool. Certainly possible, it's just that (as noted) you'd need to export the job design first to a .dsx (or .xml) file and them import that back into the appropriate ...

yollsonlegrand wrote:ANy idea will be helpfull.

You could always open a case with your official support provider and have them help you.

AFAIK, that compile that you are doing is how one must remove instances from the Director. As for the timing, depends on your job design... perhaps a Sequence job would help?

Define huge. Default (32bit) hashed files cannot grow beyond ~2GB. For hashed files larger than that, you'd need to create them as 64BIT, something you can't do via the stage so you'd need a routine or script.

Not possible. You'll need to loop through all of the jobs in the project, a call to 'dsjob' per job to fetch the job's log.

What are the Key fields in the hashed file? That is the pertinent information needed here.

Why wait only 5 seconds for the file to arrive? The error simply means the file did not arrive, you did not have a failure trigger and have enabled 'Automatically handle activities that fail' in the Sequence job.

Ok, I'm seeing the same behaviour as you are, Sequence running Sequence. After the first stand-alone run post abort/reset of my "B", it still shows the original controller when interogated. However, if I run it stand-alone after that again, then it comes back empty. It's almost as if it is reporting...

I don't recall this coming up before, so I built a quick harness. Ran a test with a Sequence job running an existing Server job and it behaved as one would expect - run it under Sequence control and it showed that when interogated, run standalone before or after that and it returned an empty value. ...