So if I could sum up everything you just said it sounds like you want an
integrated system with an integrated language that runs in an integrated
runtime? Man do I have the language and OS for you! :-)
I feel your pain as I have been in the scenarios of programming through
"hand-shakes" (i.e. data queues, SQL stored procs, etc).
What you are describing is exactly the reason I try to steer people away
from glam and glitter technologies like Java and .NET as a way to modernize
their existing RPG apps. Sure you can do things easier on the front end,
but you lose a lot of the backend stuff that will cause major headaches for
maintenance programmers and all of a sudden it takes three people to debug a
problem on your web site. It doesn't sound like you are real fond of RPG
CGI, but in this case RPG CGI running under Apache on i5OS created an
incredibly integrated environment that is very straight forward to debug.
Debugging for RPG CGI just got better with Service Entries Points being
introduced with WDSC 7.0 (not sure when they came into i5OS).
Aaron Bartell
http://mowyourlawn.com
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [
mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Walden H. Leverich
Sent: Monday, June 04, 2007 8:57 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Windows vs i5/OS as a platform
I have to agree with you here, Aaron. No offense meant, Walden, but I
think
you may be missing one of the primary points, which is that any time a
system error occurs, a message is sent to the joblog. Even more
importantly, that error is consistent, and verifiable, and usually can
be
monitored.
Not really missing the point. I get (and greatly enjoy) the joblog. I don't
know that I'd agree with "any time a system error..." but it is damn close.
However, you do get a decent level of logging in windows event logs too, or
at least you can. But I'm not trying to compare them.
That is, WHENEVER a file doesn't match the program, I get a 4131 error
telling me to recompile the program. Similarly with program not found,
or
file not found, or record locked, or even pointer error. This level of
consistent error reporting make debugging a world easier.
Yes! When system-level problems like these occur you do get the messages.
But as systems get more complex that's not really a help at times. If you've
got a n-tier setup (as you're well familiar with) and the web tier talks to
the business logic which updates the database which fires a trigger with
hits a locked record you will get a message, yes. But in what job? On what
system? To debug these more complicated systems we need better logging and
that's usually in the form of some sort of .log file system.
All I'm saying is, would the joblog be nice on windows? Sure! But is the
lack of the joblog really a problem? No. You're going to get the same level
of information from a (properly implemented) logging system that you'd get
from the job log, if not more. Log4j (commons logging now?) and Log4Net
being the two that come to mind.
-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
