DSXchange

True dat. No clue what the limit is any more but back in the day when we were processing "large" XML files, it seemed better to just pass the URL to the XML Input stage and let it do all of the work. From what I recall.

Don't see why not, that's not especially "large" in my book. If you are really concerned, I'd say that would be a support question.

Can you confirm for us what the first stage in your job is - sequential file stage? If so, suggest you replace it with a Folder stage (ideally just passing in the filename and letting the XML Input stage do the reading) and see if the problem persists.

:D

SURA - almost 1200 posts and you are still quoting entire messages to reply? Please learn to love the Reply to topic button, less for me to clean up that way.

Seriously, it's not like you're the first person to ask this over the years. Short answer? Today's date in internal format, subtract 1, convert to external.

Hello? Is someone there?

<odd, could have sworn I heard something>

Right. No-one said there was no difference, just that's there's no need to do both.

You job's running user will certainly NOT have grants to analyze anything owned by sysadm... that is strictly DBA Only territory. If that is a "user" table, get it out of that schema.

rkashyap wrote:Could you share the requirement in words. Examples are good, but only in conjunction with a requirement description.

Real examples are good. Made up ones? Not so much.

Concur - why? One or the other, zero need for both.

Yup.

Clearing all cookies may help, me thinks.

As already noted, there's no such API. Hence the other suggestions.

Why not just run a 'find' on the server, let it locate it for you?

There's a way to check the "interimstatus" of a job to see if it is going to abort when it wraps up, that might be helpful but AFAIK it's only available from a routine, not from the command line. Just a thought but don't you know if it is "executing inside the Exception Handler" ...