DSXchange

Exactly. And that's literally the only change you need to make after you copy it to a new name.

Put @FM where you have " ".

I know it will. I've tested this and watched it go back to the iteration it failed on when restarted. I was shocked when it did this, fully expecting to have to code something in, but it wasn't needed.

Then it seems you need to report this as a bug, see if this is a known issue and if there is patch available for it.

That will happen automatically if you make the Sequence restartable - i.e. enable checkpoints.

For PX you should be using the PX-specific tool, sorry but I don't recall the exact name or syntax off the top of my head.

Chuck explained how to do that.

Chuck explained how to do that.

No. S1 needs to notice that S2 aborted and then abort itself.

Assign a number to each "group" of input records. Build a hashed file with the group number and "Label" for each 07. Run back through the data and use the group number to get the label for the group.

What tool are you using for importing?

I don't see how you would do something like this without making two passes through the data. But with two passes it wouldn't be all that hard.

For an "optional" parameter, you are much better off (IMHO) leaving the default empty and only supplying a value when it is actually needed. If you can.

Or set the default value in the job to a space and then don't mention the parameter name/value pair on the command line.

My point is you don't need a routine to "wait for file" as you know the name to wait for, there are no unknown components like time. So the normal WFF stage can be used in a normal Sequence job. Write a routine to turn the current date into the variable part of the filename and leverage that as a pa...