DSXchange

Anything... unusual... about the SQL you are using? Anything 'extra' in the stage, before / after / open / close perhaps? Also curious what stage this is.

In other words, no, it does not support wildcards. Nothing stopping you from rolling your own solution though, typically something scripted for instance.

In general there shouldn't be a problem doing what you are doing, check with your SysAdmin re: their sendmail configuration and see if there is an issue there.

PhilHibbs wrote:Is there any reason not to use a Row Generator stage in a production job?

Nope. Category be damned.

What "basic routines" are you thinking need to be reused? Can you not convert them into something more PX appropriate?

:!: I've removed your code tagged example data due to concerns over exposing PHI/PII in the forums here. Please feel free to edit your post and replace your previous examples with something more appropriate - redacted / masked or completely made up values for example - for things like name, phone nu...

<relocated>

Nice find! Make sure people notice this bit, though:

To perform this procedure you will need the DStageWrapper script which is a utility that can be obtained through Information Server Support.

When use | delimiter its working fine. only issue with Fixed width If it has delimiters, then it's not really a "fixed width" file. Stick with a delimited read. If you really want more help with this, post some sample records as requested so we can see exactly what it is you are dealing w...

Sorry, needed to move you down to the proper forum for things of this nature.

What's important is that it aborts and the Terminator is one way to make that happen.

What does your actual file look like? Can you post a small number of rows from it?

The Sequence must abort for the checkpointing to work and you'll find it in an Aborted/Restartable status in that case. You can leverage the Terminator stage for this, amongst other things.

A "reducer" is a function which causes fewer rows to exit than entered, sum() for example. The error should mean you are trying to sum on a grouping (key) field.

That's my understanding anyway.

Double-quotes are the right answer, that or the 8.3 original short name that's still there. Try "\Jobs\TEST\00 SAMPLE\"* instead, that or \Jobs\TEST\00SAMP~1\* as a guess. Note the number at the end may be different depending on 'duplicates'.

Parallel job? Server job?