DSXchange

Sequence 'General' job properties: * Enable checkpoints so sequence is restartable on failure * Automatically handle activities that fail Those two options are key, especially the first. The second maybe less so since you've already have Sequence jobs with (I assume) error handling built into them. ...

And we appreciate linguistic vividity.

Flat files can be treated as 'external tables' but I don't see how pdf files could. And you'd need to create the Directory object first in Oracle.

That would give you a count, not a list. What you'd need to capture would be the 'Identifier' record that immediately follows that record, it will contain the job's name. An example snippet: BEGIN DSJOB Indentifier "AnimalCountries" DateModified "2005-05-26" TimeModified "14...

Depending on where you are doing this, there's also a BASIC function (FILEINFO?) that would return that.

If you do change the code in the job control and someone else makes a change to the job at a later stage, will the job control be recreated i.e. will my "roll your own" change be overwritten? Of course. No-one suggested changing the generated code, merely that it be examined to help explain the iss...

At this point, seems like a call to your Support provider is in order to resolve this.

Post. Your. Code.

Holy Moly, I gots me some emails! :D

In the pipe, five by five...

I'm sure you need DIGITS(CommandActivity.$CommandOutput) and/or to strip field marks from the command output.

Pass in a job parameter that controls the layout and dynamically re-arrange what field goes where based on it. Should be fairly simple if you don't need 'Columns headings' as the first record. If so then you'll need to figure a way to 'manually' write it out as your first record. Either that or keep...

For a fixed width file, you'll need to use two different jobs. If it was just a 'normal' file, there would be some games you could play...

I know. You'll need to detect that you've just read a 'header' record and parse out the report name from it. When you do that, assign that value to the stage variable in its deviation, otherwise for any non-header record just set the value of the stage variable to itself as kind of a 'no-op'. For ex...

So... what exactly do you have in the Start Loop's Loop Definition From: property?

Sure, read it into a stage variable each time you read that record and then append that stage variable to each output record.