DSXchange

The repository is corrupted and needs to be "fixed". From a recent post on a similar issue:

ray.wurlod wrote:Search also for VERIFY.SQL command, and UV.ACCOUNT table.

How are you starting your jobs? If from the command line, you can add "-warn 0" for unlimited warnings. However, this (IMHO) falls into the Very Bad Idea camp as Server jobs should never need to log any warnings.

It would be a "user written" routine, so you'll need to find it in the Manager and double-click on it to reveal its secrets.

Short answer? No, not supported. A while there are some 'tricks' for CLOB handling, not sure about BLOBs.

:? Perhaps you can expand on what "capture the result in other job" means? Seems that you would just need to call it in another job and then you can "capture" the result however you like - write to file, log, table, etc. You'd need to use the BASIC Transformer for this in a Paral...

Sorry, I don't. Just seem to recall people posting a similar issue in the past. Perhaps one of the DB2 gurus here will be able to lend a hand.

Exactly, as already noted.

myukassign wrote:Is it possible?

Short answer? No.

Long answer? Yes, sortof. Export the whole project and then hack it up into the pieces you need. People here have written similar things, searching for "dsxcutter" (I believe) should turn one of them up.

That sounds vaguely familiar... bug? You might want to ask your official support provider and see if that's the case.

Best if you use the Contact link at the top of the screen to ask questions like that of the "MembershipDirector".

Come on, of course there is an Update action on your update link - that is what is used to build your sql or what allows you to supply 'user-defined' sql. And nothing you've posted leads me to believe your inserts are the problem seeing as how you only get errors when it should be updating based on ...

You must have missed the "nologging is ignored" part, but ok - whatever works for you.

One thing - stick with the Exact match. The other two seem to be 'broken' in that they appear to be date limited in order to cut down on the results returned. Those volume warnings on the Search page are there for a reason. Problem is, I've searched for posts I know I've made, and while the Exact se...

I did an Exact Search for "sequential operator cannot preserve the partitioning". You need to search for enough to find what you are looking for without searching for "too much" or anything specific to your data / problem.

Was just wondering because, from what I recall (right or wrong), most times I've seen "LDR_CNTRL" mentioned here the issue was on an AIX box.

Thanks for posting the solution.