DSXchange

You'll have to build into the job any mechanism to pick up where you left off, something not all that trivial. It involves keeping track of your last commit point and then leveraging that after a restart to skip all of the committed rows, typically by a transformer constraint that only lets rows pas...

You'll have to do something to ensure you get an empty file from a non-empty source. For example, put something in the where clause that ensures you select zero records, where 1 = 2 for example. Or use a contraint in the transformer that ensures no records get past, @FALSE comes to mind.

So, you could compile the job but this error is thrown when you try to run the job? :? I find it odd that your path has things that look like assignments, is that normal? I would expect to see segments like this: E:/Ascential/DataStage/Engine/bin: Rather than this: /E=/Ascential/DataStage/Engine/bin...

You could just search here for them, they will turn up. For example:

viewtopic.php?t=131992

1. No clue
2. Client connections
3. rpc daemon, allows #2 to happen

So... still confusing. Are you saying that you can only see the records in the target when you stop/disable the service? If that is the issue, can you confirm for us how you are handling commits in the target? Typically in a service you'd have to issue explicit commit (or rollback) actions when each...

I'm afraid you might be confused about what exactly a web service is and the meaning of "deploy" in this context. It seems to me that when you say "deploy" you actually mean "run", especially if you are saying that step takes an hour. Sounds like you have just a regular...

Ah, sorry... missed the "in sql" part. Yes indeed, the "call" syntax would be the correct answer here.

They are all the same "ps" command which gets everything as a full listing (ps -ef) they just filter different parts of the results out based on the expression being grep'd for.

Not sure that is supported, we would always zip any files to be sent so we could send it out with a single attachment.

Please be clear in your requirements. You have two jobs and need to run one or the other based on a parameter? Or run the second using a parameter from the first? Or ????

You can't "retrieve" anything from a proc run before/after sql. Can you not use the Stored Procedure stage for these?

Use Sequencer job... or is that the part you need help with?

Really would not recommend that. Run a cron script once a day to prune it back as noted instead.

How is that one different from any other record? :? You should standardize your Oracle dates so they extract in that same ISO Timestamp format you mentioned in your derivation. Make the source column a Timestamp data type and (if the sql doesn't automatically generate this) use the to_char function ...