System iNetwork

San Jose Water has just started down the path of WebSphere. Have searched the web sites, book stores and just started reading The RedBook plus asking friends and vendors. Also, looking at training, however not sure where to fit it in yet. First we need to load it so it is available. Still seeking 'step-by-step' instructions on how to do that. Greatly appreciate your group and will continue to watch your blog. I get the feeling that it is like trying to know all the stores in Mall of American, what they sell, the price, plus being able to put your arms around the building. The team at SJW will be 2 (sometimes 3) so we look forward to your contributions. Bob

This is very interesting! Having programmed in RPG for the past 24 years myself, I understand very much what are these 5 courageous guys are going through. I look forward for the next articles. All I can say is Good Luck Guys!

Like the above two comments we are on the verge of putting the Green and Black screen behind us. I shall follow the blog closely and with interest.
I find it a shame that Big blue didnt put more effort into making the transition from Green and Black to Web a little more simpler and easier to do. Especially when we know the As400 is the machine for the future and that it can do all of these wonderful things...
However I am still left a sole manager and developer of two machines and have to keep justifying its rather dated appearance and present 'op mode' to the boss who also manages 'the buy another PC. server to do that boy'...
Tone

Hi folks! Thanks for the posts. Keep them coming. The more interaction we have on this blog, the more likely others are to join and we can then learn from each other.

IBM is getting more information together on helping programmers transition.

I'm also writing monthly articles for iSeriesNews on step-by-step ways to use WDSc.

Been using WDSC for almost 2 years now. Mostly full time for a year. The learning curve by yourself is steep, but once you get past the inital frustration period, it's a much better environment.

I especially like the CODE Designer for my DDS screens and print files. However, I'm waiting for IBM to encorporate them into the Page Designer, so it can be in the same IDE as WDSC.

I would give the suggestion to learn to use "User Actions" to set your inital library list. I have seperate user actions for all of my different development enviornments. Then learn to customize your compile options - that's especially helpful. I have different compile options that bind specific ILE service programs to my modules (ie ILE utilities that I've written).

Good luck guys - don't give up on it!

Hey, any of you reading this creating web apps using WIT files? We have yet to find anyone using this approach to creating web apps using WDSc.

The WDSCi-L email list is an excellent resource for any team learning the new development studio environment. It can be a little high volume some days (depending on what you want to call high volume). But it's an excellent place to get tips and to get answers to questions. Don't be suprised to occasionally get help from IBM developers on the list. More info on the list is at: http://lists.midrange.com/mailman/listinfo/wdsci-l

In regards to training, Tom Thomson had the opportunity to attend IBM training. An IBMer came to Gillette, WY and held a class. The class was close enough for us to send someone. I'm sure once Tom reads this post, he'll give his 2 cents worth on the training.

I will be following your adventure closely. Like Mr. Sutherland, I too am a fan of CODE Designer, but I never really took to CODE/400. I've played with WDSc but I will attest to a steep learning curve.

All source in a single member? Must be a big one <wink>!

But seriously... I'm an Eclipse fan for my Java development. I'm interested to read of the experiences of a team who is converting while still using source files on the iSeries.

Been using WDSc since the beginning of 04. The learning curve is a bit steep. I was prompted to use it as we are doing a bit of DotNet development and was having issues switching between that environment and SEU.

Once you are past the curve it is a big productivity enhancer.

Started using WDSc as primary development and support environment for our iSeries in January 2004. Learning curve at first was a little steep but once I started getting the hang of it, I quickly realized it was a huge step forward over PDM/SEU green screens and a much more feature rich, productive environemt.

Looking forward to following along as the team tackles WDSc development. Hoping to pick up a few pointers and tech tips. Good Luck with yor WDSc Survivor Weblog!

Good luck guys!. I am working with
CODE/400 and I think that it's a good tool. That's the unique tool by the moment used. I hope use WebFacing
and Java in a near future.

Hey Guys,

Looks like nothing but fun. What ever happen to you SEAGULL efforts? Did those ever pan out or was it for not?

Love the blog. Look forward to see how you turn this around.

-David

I have been using WDSCi for a year and a half now. True, it has been a slow transition but that was because I was "self-training" myself. I believe I could make my teammates more productive quicker on it just by instructing them on the basics. There is still so much in WDSCi that I am learning something quite frequently I didn't know was there before.

I am in the process of developing a business case for WDSCi for the iSeries developers. What do you feel is the ramp up time for a programmer with typical SEU knowledge and after the ramp up, what is the effeciency gains afterwards.

Just read your article on WDSc in Jan. '05 issue. Good start.

I've only been using WDSc for about 2-3 months so far but already can't
live without it. I kept seeing a message in PDM about "Information about
new tools" and decided to load it on one day. After getting it loaded I
dove in. Found out how to connect. How to download PTF's. It took about
a day for me to get comfortable with it. Still doing green screen development though. No web stuff... yet.

Just thought I'd mention a couple features I really like and not sure if
you tried them or not.

The first is the source member compare. You click on one member and then
ctrl-click on a second then right click for the pop up menu and select
compare. You'll then see both members side by side with lines connecting
the 2 showing where the source is different. The really neat thing (I
think) is just to the right of the members in the scroll bar area you
can see these little blocks. These are were the source code is different
and how big of a difference it is. You can click on one of these and
it'll take right to where the difference is.

The other thing I like is the user defined options on the right click
pop up menus. I've got things setup so I can do CLRPFM, RUNQRY, pdm
prints (I like the 400 print outs better than File-->Print), etc. all with
a click of a mouse.