DSXchange

Add the $APT variable as a job parameter, then it can then be changed at runtime in that job's environment (and just for that run) just like any other parameter.

From what little I recall, "low values" would indeed be "hex zeroes" so you may not actually be setting this up correctly and thus ending up with a decimal zero instead. Can you explain exactly how you are doing this? Field data type, derivation, etc etc.

Best example would be in any existing checkpoint enabled job. Check the Job Control tab under Job Properties, the fully generated code will be there including all of the checkpointing logic. Basically, you are leaving "bread crumbs" to show where you've been and what the result of each ste...

So... what IS the case?

Oh... he's just a treasure.

What database do you have at your disposal? Are you allowed to create temp/work tables in it?

Yes, they still exist and are 'supplemented' (not replaced) by the XMETA repository.

Can't check right now but there's an option in the XML Output stage to "group" your data from what I recall. How is that set?

have somebody a hint for me, how I can analyse the problem, because I have no further idea on than issue. I'm curious how Ray's "hint" was any different from mine. Other than coming from Him, of course. :? Within the job design the invocation id is not used. I find that hard to believe, g...

Since we don't know just exactly how "same" your "same issue" is, it is always best to start a new post with your particulars and actual error(s).

Pretty close.

The 'output' conversion mask is off and needs to be more like what you have on the input side:
Technically, the IConv mask can be simplified but that should work more better for you.

Please understand - you cannot make the built-in automatic check-pointing work the way you 'need' it to work, so you should put that from your mind. For the behaviour you say you want, you'll need to (in essence) build your own check-pointing system, one which may (or more likely may not) require th...

Split the date from the time, use the IConv/OConv functions to convert each component and then cat them back together. If you really need the milliseconds then just stick the ".000" on the end. Both 'conversion' functions are well documented in the Help, give that a shot then let us know w...

That was the 'technically' part.