DSXchange

Still not a control table. If you need to run the two jobs in a particular order one after the other, that's what a Sequence job would let you do. If you need one job to run another, you'll need to be more explicit as to what exactly that means. One time thing? Technically you can use dsjob from the...

I think that's a great idea, Kim. A 'lite' version could be an awesome framework for others to expand on as needed.

All we could do is guess. Have you involved your DBA, had them monitor the session while it runs to see if they have any idea why it might be "hanging"?

Nothing ever equals NULL, you need to stick with the same IsNull() function you used in the constraint.

Sorry, I should have said something... noticed the strange "+" syntax but figured you were posting "psuedo-code" rather than what you were actually doing (math) especially when you said the end result was NULL in the first post rather than zero. My advice still stands, however, i...

That error is detailed here along with the 'user response' suggested.

It's standard NULL handling, once you introduce NULL into any operation, the end result is NULL. Assuming only the second field can be NULL, wrap it in a NullToEmpty() transform during the concatenation.

Your issue could be resource related, if I'm understanding all of your steps. Are your sequence jobs running many jobs? When some jobs running under a sequence fail but work fine if run individually or rerun from the point of failure, that is very typically a resource constraint... too much going on...

So nothing to do with memory but rather a shared library format error / load failure. In your shoes, I would get that in front of your official support provider to help track down the cause. What exact parameters are you passing in to the job? I still don't think that is the issue as they really sho...

v_bhaskar wrote:still is it the problem with memory

How do you know it is a problem with memory? I never said that, nor did I suggest you clear your logs - specifically noted you should check the diagnostic log file that was named in the linked thread.

If you did, what were the contents?

I don't really see this as being a parameter issue. Any searches for those two SQL error codes say to "look in the db2diag.log file" to see the actual problem. One such example here where the problem was an inability to allocate memory.

But that's all fine as long as you have something that is working for you. And If after you search you would still like to talk about BASE64 encoding, please start a new conversion on that topic.

Other than here, which is the only reason the "B" variant was mentioned:

may and may wrote:Thanks for your reply Ray.
but MX0C is converting it to Hexadecimal format but not binary

MX0B is giving the result as is the input. MB0C is giving the correct Binary Conversion. So... which is it? First MB0C was wrong and now it's right? [confused as to which one is giving you the conversion you were looking for] As to your new question, you can shine your own light on the subject by d...

Everything that's already been suggested still applies, it just needs to be... adjusted to fit. You just have two things to check now rather than one which doesn't really complicate it all that much more. Meaning... your change is not a fundamental "gotta go back to the drawing board" kind...