DSXchange

And that was addressed. As noted, the "column headings" are just the first row in the file, write them out as data so your spaces can be used. They cannot be used in Field names which is what automatic creation of the header record would use.

In my mind, the biggest question re: failing the job is - do you want to fail it when the first issue is found or after all issues are found and logged? Also, the rename can be done "after job" by checking the INTERIMSTATUS to see if the job is on its way to Abortsville.

I don't see how the user could cause this unless you were accessing a different table than you should have been.

I don't have access to a system right now but wasn't it a property of the job itself with the ability to manually change it right there in the Designer?

Can't really help but I recall discussions with colleagues who have had performance issues with Sybase that I don't believe were ever resolved. You might want to check with your official support provider and see if that's an issue with the stage itself or the version of the client software you are u...

What operating system? Could be a bug at that level...

Sorry - that was a little simplistic, wasn't it?

Do an exact search for "option is deprecated".

And by "hanging" you mean the Master Sequence job itself logs the Email Notification activity but does not complete, i.e. it stays in a Running status? You said "the sequence or the job" so unclear exactly where things get hung up - the Master Sequence, one of the child Sequence ...

So... a calendar quarter rather than any kind of fiscal quarter, yes? How about a simple Mod(MonthNum,4) + 1 computation?

Looks to be a snippet from this post.

No. It (and the companion Expand Stage) are all about data sets. Now, that doesn't mean you can't "compress" a sequential file, you'd just have to do it with a singleton call to your O/S after creating it.

It would be helpful (to me at least) if you would answer the questions I asked.

OK, no problem. We'll be here when you get back.

That's not a lot to work with and most times an "internal error" like that should be reported back to your official support provider. In the meantime, you might try doing an Exact search here for "check that 'dbx' and 'sed' are install and on your PATH" to see if any of the other...