But it's actually my experience that packages are often better at using the
joblog than custom code.
I have developed packages for the System i5 and I only log when a config
flag for debugging is turned to "on". I don't think you should find lots of
job log entries when things are going well, but maybe that's just me.
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?
I would agree that a CHAIN not %found shouldn't be in the job log, but it
should be sent back to the screen stating something to the user. That can
then be debugged by doing a simple SQL statement against the table (nothing
new to you or I here). I think we were just on totally separate pages
concerning what a job log should and should not be used for.
Aaron Bartell
http://mowyourlawn.com
-----Original Message-----
From: web400-bounces+albartell=gmail.com@xxxxxxxxxxxx
[
mailto:web400-bounces+albartell=gmail.com@xxxxxxxxxxxx] On Behalf Of Walden
H. Leverich
Sent: Monday, June 04, 2007 9:03 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400]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.)
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a
message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit:
http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.
midrange.com
