Re: What are you doing with .NET and integrating into IBM i?

Dave

Quite frankly, the level of complexity you can get with VB code far

exceeds anything I've ever seen in RPG

How would you draw a 3D bar chart Image in RPG?

Maurice O'Prey


-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of David Sager
Sent: 20 December 2012 19:22
To: .net use with the System i
Subject: Re: [SystemiDotNet] What are you doing with .NET and integrating
into IBM i?

Matt, I can answer a couple of those...

1. Database interoperability. I am pretty sure Scott Klement's stuff for
accessing other databases suffices. I know we use the JDBC version to
access Oracle databases on a regular basis. The only snag we ran into was
with DNS servers - evidently it tries all of them you list rather than
stopping after the first hit. We had our back-up DNS server defined, not
realizing our network guys would take it down without notification. Response
times ground to a halt while the JVM had to go through its timeout logic.

2. Again, it's all how your web services are defined. If you set up a
procedure to handle it, then a single line of code in your application
should be all that's required.

3. Indicators are both a boon and a bane. We still use indicators here to
interact with our display files, and I have a couple of what I would
consider *state of the art* applications that use all of them (to handle
presenting the appropriate fields on a build-your-own search). Yes, having
display attributes as methods and properties would be great, but then again
I've heard you can imitate them with display files. We've just never taken
the time.

4. Cyclomatic complexity? You can write garbage code in any language.

5. Testing frameworks? We don't need no stinking testing frameworks! Quite
frankly, the level of complexity you can get with VB code far exceeds
anything I've ever seen in RPG. The only thing I can remember that's come
close are the old IBM MAPICS programs that would use a variety of *unique*
processes to get the job done. But then again, most of those were designed
to run on multi-user systems that had a whopping 64KB of memory (those were
also the days that you were severely chastised for writing any program that
compiled into more than 14KB).

- Dave Sager
Solus Christus

On Dec 20, 2012, at 1:03 PM, "Matt Olson" <Matt.Olson@xxxxxxxx> wrote:

Awesome, we can get rid of that program maybe. I guess some better

examples would have been in order:

1. database interoperability. Without unsupported addons such as ARDGATE

how to read/write from external databases?

2. Interact with web services with one line of code?

Webserver.AddTwoNumbers(x,y)?

3. Indicator hell, we have some programs that use all 99 indicators.

Code spaghetti! Obviously this is just a bad coding issue.

4. Built in code metrics (cyclomatic complexity, etc) 5. Unit
testing! We have a wealth of unit testing frameworks, where are the

dozens for RPG?

Etc...


-----Original Message-----
From: whatt sson [mailto:whattssonn@xxxxxxxxx]
Sent: Thursday, December 20, 2012 7:39 AM
To: .net use with the System i
Subject: Re: [SystemiDotNet] What are you doing with .NET and integrating

into IBM i?

I remember a discussion about leap years, we have this really old
RPG

program

that had to calculate leap year logic, and I showed them the one
line of

code in

.NET to do the same thing.

I can do that also in one line with RPG :

if IsLeapYear(y) . . .

or even translate a gregorian date to a week date like this:

wdt = Gdt2Wdt(date);


in ONE line !!



On Wed, Dec 19, 2012 at 9:54 PM, Matt Olson <Matt.Olson@xxxxxxxx> wrote:

We are doing a lot things with .NET nowadays. You look at the
program difference in reduction of lines of code, testability,
readability between a .NET program and an RPG program that does the
same thing and it makes the RPG guys cry.

So with that being said, we generally don't talk about it anymore,
RPGers get upset. I remember a discussion about leap years, we have
this really old RPG program that had to calculate leap year logic,
and I showed them the one line of code in .NET to do the same thing.
There are so many examples like this it isn't even fair to compare
.NET to RPG, hands down .NET will win every time.

That's just the nature of technology. Things progress.

-----Original Message-----
From: Mike Wills [mailto:mike@xxxxxxxxxxxx]
Sent: Wednesday, December 19, 2012 2:41 PM
To: .net use with the System i
Subject: Re: [SystemiDotNet] What are you doing with .NET and
integrating into IBM i?

I was trying to pull out issues people are having. Maybe it's so
perfect that there are no problems. ;-)

--
Mike Wills
http://mikewills.me


On Wed, Dec 19, 2012 at 12:55 PM, Maurice O'Prey
<Maurice.Oprey@xxxxxxxxx

wrote:

Well Mike

That was certainly a pot boiler! Haven't read such a debate in a
very, very, long, long, time :-)

Why don't we just mention .NET over in ("the other list"). Always
attracts attention... IMHO

- Maurice O'Prey


-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Mike
Wills
Sent: 18 December 2012 16:25
To: systemidotnet@xxxxxxxxxxxx
Subject: [SystemiDotNet] What are you doing with .NET and
integrating into IBM i?

Since this list isn't very busy lets get a conversation going!
What are you using .NET for?

--
Mike Wills
http://mikewills.me
--
This is the .net use with the System i (SystemiDotNet) mailing
list To post a message email: SystemiDotNet@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/systemidotnet.

--
This is the .net use with the System i (SystemiDotNet) mailing
list To post a message email: SystemiDotNet@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/systemidotnet.

--
This is the .net use with the System i (SystemiDotNet) mailing list
To post a message email: SystemiDotNet@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/systemidotnet.
--
This is the .net use with the System i (SystemiDotNet) mailing list
To post a message email: SystemiDotNet@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/systemidotnet.

--
This is the .net use with the System i (SystemiDotNet) mailing list To
post a message email: SystemiDotNet@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at

http://archive.midrange.com/systemidotnet.

--
This is the .net use with the System i (SystemiDotNet) mailing list To
post a message email: SystemiDotNet@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/systemidotnet.

--
This is the .net use with the System i (SystemiDotNet) mailing list To post
a message email: SystemiDotNet@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/systemidotnet
or email: SystemiDotNet-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/systemidotnet.