Re: Upgrades and JWalk

It *could* be a model thing I guess, rather just a serial number issue. I know next to nothing about JWalk but I thought it was serial number dependent but not model. To make things more interesting this is a customer running JWalk (for a product called CIMS) licensed through a company called Pearson which has now sold the customer base to another vendor. So Seagull says call Pearson and Pearson says call the new vendor and the new vendor says "what?".

We are checking on the IFS folders and files. There were several HTTP 404 messages with folder paths "not found" in the log. We are running them down to see if they exist or not. It *may* have been a problem with the save and restore.

My primary query was trying to determine if there was anyone with the experience of moving JWalk from one box to another where the serial number was preserved. Doesn't look so.

Pete

Pete Massiello wrote:

I know they have a folder in the IFS as well as the library.

Are you sure it isn't model and serial number dependent?

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Tuesday, September 11, 2007 11:10 AM
To: Midrange Systems Technical Discussion
Subject: Upgrades and JWalk

Anyone use JWalk and have gone through a box upgrade where the serial number was retained? I have a customer that no longer has support on their JWalk installation but recently upgraded to a System i i5 520. Even though they have the same serial number, JWalk fails to start. Does anyone know if there is something "special" that has to be done when a system using JWalk is upgraded?

Thanks

Pete Helgren