DSXchange

No, not that I've seen yet... you need the job to Abort so the checkpointing can restart at that point. And your issue with 'applying the limits for warning messages to 1 does not help since the server is unable to respond in time' has been discussed here before and seems to be unique to PX jobs. Pe...

Perhaps you are.

A couple of suggestions. Look in your 'Docs' folder and read the 'XML_PACK_20' pdf that is there, it will help tremendously. Also, if you didn't do this the first time, trying using the 'auto check' option in the metadata importer rather then selecting individual fields yourself.

No worries, Ray *is* everywhere it seems. You didn't answer the metadata question, but I'm guessing the answer may be 'no' as I don't really see a problem processing a file like that. Can you get your hands on an xsd for the file? Then use that to import metadata and generate the appropriate XPath e...

Nope, it's the milliseconds which the current mask does not include. Hence the message about running out of 'format picture' before running out of timestamp.

You may need to use TO_TIMESTAMP instead of TO_DATE for that field type. Or not.

Well... sorting not equal grouping, that's typically an Aggregator task. You might want to get into a little more specifics on what kind of 'grouping' you are doing, as the XML Output stage can do some of that for you.

Examples are always good.

It will fire when it first sees the file, complete or not. That's why most people would use a 'flag' file ftp'd after the completion of the large file to actually trigger the load.

Why not convert the inserted data into a sequential file and then use a 'regular' job to process it? Why the 'need' to do it this way?

Good point - it will be 'empty' when there is no job open as the pallete is built based on job type. Now, if it's still empty after opening a job, you've got a real problem.

Reinstall the Client.

Yikes! DataStage help from beyond the grave!

And then there was Jules, gone for almost a century from what I recall.

Thanks Chuck!

No, you need to create a script to 'wrapper' it and log into your command line sql tool of choice. Can't get more specific than that as you've haven't mentioned what database you are using.

As to the where, put it after the End Loop.

You can also leverage the 'Checkpoint restart' capability of a Sequence but mark individual activities as 'Do not checkpoint' so they always run. Perhaps that is another approach that would help.