Re: Recommendationsof webdevelopmentarchitecture/tool fordiverse i5access...

Maybe we are just dealing with different debugging approaches, but

yes, I

use the joblog ALL the time for errors. You can go in and learn

exactly

what line of code threw the error. You can also learn when the job

entered

the subsystem among other helpful info when debugging an error. I

would say

you are missing out on a very nice feature of i5OS for debugging

purposes,

though it sounds like you run mostly pre-packaged software on your

i5OS??

where I am doing a lot of custom development.

Actually we're all custom development, not package. But it's actually my
experience that packages are often better at using the joblog than
custom code. As for debugging approaches, perhaps they are different, or
the problems are different. I'm less concerned w/the issue of
system-level problems (locked row, missing table, etc.) and more
concerned with logic errors. How does the joblog help you debug a
missing customer? Not the entire table, just a missing row... You know,
debugging those inevitable "the row must be here... but it's not..."
errors? Or help you deal with errors in logic in computing the price of
an item? Or it's shipping weight, etc.?

The joblog is great for system-level stuff. There's no argument there.
But I'd guess most "bugs" aren't system-level issues.

-Walden

--
Walden H Leverich III
Tech Software
(516) 627-3800 x3051
WaldenL@xxxxxxxxxxxxxxx
http://www.TechSoftInc.com

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)