DSXchange

But if the scheduling user is not in the appropriate 'allow' file then the scheduling attempt will fail, not the running of same. Need a better explanation of what 'hang' means.

But I am facing this problem only when I use Varchar(2000), this problem disappears when I use Longvarchar(2000). Why? Because Longvarchar is the proper datatype to use with a CLOB. Use it and stop worrying about it. If you really want to use a Varchar then you'll need to CAST the CLOB to a VARCHAR...

No, dual is a perfectly valid 'pseudo' table and can be used in the manner that the OP showed. However... I don't understand what 'at the end of each step' means and where exactly this SQL is being executed. And as Ray notes, by itself this SQL doesn't update anything. This seems like an awfully clu...

Is your hashed file in an 'account' or is it a 'pathed' hashed file? This utility will only work with account based hashed files, hence the question.

This is a two year old topic. Sheesh... I would think they've solved their problem by now.

They take them beyond the realm where I am going to worry about it... too many other fires burning. Just grateful one was put out.

No, that's fine. If you have no record terminators then you won't be able to use things like 'head' or 'tail' to trim out headers or trailers and will need to let the CFF stage do it for you. Carter has been trying to drive that point home. All I was trying to point out is that EBCDIC and record/lin...

Thanks for your help with all this, Arnd. I've got something that seems to be working fine and giving them what they want - inspired by your code and guidance. I've stashed yours away for a rainy day, copyright and all, in case I find a need for it. They ended up wanting something more displayable (...

Problem is, not all Aborts are created equal. Jobs can crash or suffer timeouts and other problems that are not considered as 'Aborted'. That's why I prefer to specify the good stuffs and then let all the bad stuffs get caught by the Otherwise trigger.

Now when I put "Otherwise" in the second link and 'Finished Ok' in the first link, when warning occurs the "Otherwise trigger gets kicked off and the next sequence dies not run. Of course... think about your trigger values. There are three basic status codes a job could finish with: 'Ok', 'With War...

I'd be curious to see your routine as I'm not having alot of luck duplicating what you are saying here. Sorry.

I can find an 'MB0C' conversion code (zero not oh) but that seems to output a giant binary number. Did you perhaps mean "MO0C" to get Octal?

My point in ebcidic format is - if its in ascii i can manage to read the header and use head command till n-1. But iam not sure wheater i can use 'wc' for this purpose and will it procduce same output for ascii and ebcidic Yes, you can use 'wc'. EBCDIC (only one 'eye') isn't magic or something that...

It is an interesting solution, unfortunately I don't believe it will work for us. I've made the classic newbie mistake of not giving you 100 percent of the information needed to solve my problem. I was looking for an function because it needs to be repeatable by the business partner we are creating ...

Really - why go through all of these shenanigans to remove something that a simple change of record terminator in the sequential file stage will automatically handle for you?

Ken's suggestion is the way to go - specific reject links for specific errors or groups of errors. That way you can control how many it takes per link before it aborts the job.