DSXchange

So... the first date range is three days but the others are actually four days?

ps. The opposite of a 'cold' backup is a 'hot' backup.

And there's literally no warnings logged when this happens? Anything about the value being 'not appropriate'?

What have you tried? IConv/OConv can handle getting your Date into the same format as your Timestamp but how will you handle the 'compare'? Meaning, will you need to convert your constant date to a zero time timestamp or do you need to compare it to just the date portion of the timestamp?

From the ".ds." in the name, that would be a dataset.

More questions - are they 'large' files? Wondering how safe it will be if you start your processing when you see the 15 files or if you'd need to do an explicit 'wait until the file completes the transfer' step as well? Me, I would probably hand code this into a DataStage job on the Job Control tab....

Can you identify those 15 files via a pattern that does not include any strays, or do you have 15 fixed names, or something else entirely? Need a better idea what the options are here.

Not without some help from them - a trigger or CDC, for example. Otherwise you're right, it's a full table scan each time. Depending on the system, however, that may not take all that long.

That would mostly depend on if these are 15 files with distinct fixed names or if you'd need to do any 'wildcard' pattern matching to wait for them. For the former, you could literally use 15 WFF stages. For the latter, you'd typically want to code up something yourself. That something could be a sc...

No-one ever said it would be simple.

As noted, they meant the "dsenv" file rather than "uvconfig". It lives in the main $DSHOME directory called DSEngine as an editable, plain text file.

Best to start a new post for new questions. No, you won't be able to use the WFF stage as it only waits for a single file and doesn't support wildcards. Well, actually... I guess you could put 10 of them in the Sequence job and run them into a Sequencer set to 'All'!

The trigger is on the first stage, yes.

Ah... so no sending involved, it seems. For process control, just check the return value in the trigger to the second Execute Command stage:

Choose "Return Value (Conditional)" as the trigger type and set it to "=0".

Can you let us know what commands they asked you to run? Also, what kind of UNIX is your server O/S and what is your exact version of DataStage? Any ideas on what patches you installed?