DSXchange

Definition of deprecation as it refers to software in case that term is unfamiliar to people. As noted, from what I've read IBM assumes you will switch over to Connector stages in all cases as the old ones are technically there for backwards compatibility and may go the way of the wind in a future r...

Noted:The only reason i opted to perform above because xml input stage requires XSD stored some where and results the warning stating "The primary document entity could not be opened". No, it doesn't. The new XML stage does but the older ones certainly do not require them. Leverage, yes, ...

Just want to point out that the Trigger Column has nothing to do with 'grouping'. It is simply a value that - when it changes - forces a change in output filename, closing the current file and opening a new one.

And we still need a clarification from Roopanwita as to what exactly it is they are needing help with.

Then you are firmly in the Camp Substring. You can use Index() to find the information that Substring() will need. What does "grow on demand" mean?

Exactly. That should be part of any home-built "job running script" that your scheduler is leveraging.

You reset an aborted job to get it back to a runnable state. Since your job is not Aborted, that is a 'bad state' as far as the reset is concerned. The default mode is to run in NORMAL mode, which is why it works when you take the mode out.

Details here.

eostic wrote:Sequential stage in 9.1 does this. Folder Stage in Server also does this, in any release.

Thanks... 9.1, eh? Was going to mention the Folder stage but it is somewhat of a PITA to use as a target and tends to confuse the crap out of people attempting to use it.

Yah... you're right, that's just adding the column name to the input stream. I'd be curious what Andy or Ray have to add because I could swear it was added 'recently' to the product and one of them mentioned that fact. Or perhaps Vincent^H^H^H^H^H^HErnie. Could be wrong, however. :? Old School would...

Come on... how about you put a little effort into solving the problem first? Then show us what you've tried and what's not working and we'll help nail it down for you. If the Field() suggestion is throwing you, you can use it to take the first field from your "@" delimited string. The rest...

Sorry, can't seem to find the details at the moment but did find this in my searches:

ray.wurlod wrote:Sequential File stage has the ability to generate the file name into an output column.

Hopefully someone can provide details on the 'how' of it.

asorrell wrote:I've never done it, but I believe using a Sequencer you could funnel Job#2 back into the "loop" prior to the EndLoop so you could continue the "Test / Sleep / Execute" cycle.

I have and yes you can via a Sequencer set to 'Any'.

Sorry, I have nothing useful to say other than - dang, I would have thought they would have fixed / handled that by now.

Well... you could probably handle this via sed / awk / grep in the Filter option of the stage.

That topic is specifically about multiple "pipelines" - jobs within a job. Is that what you have? Or do you have a single (quote normal unquote ) job that writes to multiple target tables with FK dependencies between them?

So answer is no, at least not directly. I've done "time based" loops by setting a duration for each loop and then looping how ever many times it would take for that number of loops to hit my end time. You can also use a custom routine to check the current time inside the loop and exit (bra...