Sorry, but I have no clue if Profiler works with DB2. It’s been since the early 90’s when I worked with Natural for DB2. I assumed it would, but maybe not. But since you get the error without even starting Profiler, I would think there is a problem between Natural and DB2. NAT3700 is the catchall Natural error for errors returned from DB2. The Action description for 3700 says:
I suggest you try that and see what the SQL error is. And ask your tech people what’s up with the Natural-DB2 linkage. Maybe they broke it when they added the Profiler. If your site is still under a license and support contract, they could also call SAG support if necessary.
I would also suggest you start a new thread for this new problem. Repost your question with a Subject of some thing like “Need help with a Natural for DB2 NAT3700 error”. That may attract a few new eyes to the problem, from members/moderators with more DB2 knowledge.
I think you’ve milked this thread for all it’s worth. I’m sure the moderators would appreciate it if you would pick one of the more relevant answers, about the Debugger I guess, and mark it “Answered”.
Thanks, and good luck.