midrange.com – In My Humble Opinion

Words of wisdom and insight from the IBM i (System i / iSeries / AS400) community

Browsing Posts published by Mike Wills

I have been in the Midrange.com community since around 2001. In those 10 years, I have been helped by many in that community countless times. Today, I got to see several of those people and I am sure by the end of the week, I will meet many more. Today was a whirlwind of events going from the First Timer session to a couple other sessions. Both very informative and valuable information I can bring back to my workplace. I knew going in that not only would I learn a bunch, but I would met new people.

I met someone from IBM who happened to grow up in Nicollet, MN. I found out that she is (if you stretch it quite a bit) is related to me. I talked to several vendors about bringing our IBM i Apps to the web and received information that I can use when we start our “modernization project” in the coming months. Most of all, I found out what I knew already, this community, this IBM i community is very friendly and very helpful. They are willing to strike up a conversation about just about anything.

I’ll write more as I have time.

Cross-Posted on my personal site.

For our new billing system (AR), we wanted to store account numbers for so that our customers could auto-pay their bills. After some searching and seeing how complicated the APIs are to use, I found these SQL functions: ENCRYPT_RC2(data, password) and DECRYPT_CHAR(data, password) . These looked promising and being that this is an internal-only system, we thought that this should be okay.

Now the challenge, we don’t want to have to use SQL INSERT and UPDATE statements every time we create or update a new record. RPG (Report Program Generator) has built-in commands to do that: WRITE and UPDATE. I found this article that talks about some work-around options. One of which is a trigger. This makes the most sense for our scenario.

continue reading…

I finally figured out the major points for working with teams in WDSc. It uses a combination of CVS (Concurrent Versioning System) and WDSc. I will go over the major points in getting this setup and working. I am learning as I go and may update this article as I gain more knowledge in how this works. Feel free to leave comments and suggestions to make this article better.

continue reading…