DSXchange

See if this helps shed some light:

viewtopic.php?t=108766

Which is exactly what Arnd told you.

But again, all that presupposes the input is already a timestamp which this isn't. And the formatting mask in the TimestampToString function is what you want the string to look like.

You'd have to give us a much better idea what 'the security is taken care of' means first. Be precise.

Please to read the documentation for the IsValid() function.

Depends on who this 'we' was... here us we people have yet to DLST.

'19971001' is not a Timestamp.

And what happens when you 'correct' the metadata? You are certainly not stuck with whatever it 'takes'.

Stage variables are one way, only increment when ColB changes value. A Sort stage with the 'Create key change column' option would help, too - increment only when that column has a 1 in it.

Good. There's a long standing DSRunJob bug where the call to start the job will crash. The called job may actually start but the calling job is in permanent limbo waiting to hear back. It never will. I wonder if that's what's going on here.

OK... only ask about dsjob only because that was what you said you were using. Hard to diagnose something like this - do you clear your &PH& 'phantom' directory on a regular basis?

So, the 'controlling' job is not a Sequence but another server job? Can you post your full dsjob syntax, please? What kind of 'aborts' are you seeing in the called job?

I'm *told* that it is and that they've allegedly created files larger than that in the past. Any idea how I could verify that short of me trying to create a big ass file there? OK, I can find existing files > 2GB but not one as big as the size noted in the error message. And, oddly enough, they've a...

Except for the fact that while the client is supported under XP, the server is not.