RE: Problem when running Visual Age -- JAVA400-L

we are using VAJAVA3.5 is it possible to upgrade to 3.5.2 for free?

-----Original Message-----
From: Jim Mason [mailto:JEMason@compuserve.com]
Sent: Wednesday, August 15, 2001 2:06 PM
To: INTERNET:JAVA400-L@midrange.com
Subject: Re: Problem when running Visual Age


Hi Azeem.

As Gary correctly points out, knowing the OS version is important.
I run Windows NT 4.0 with service pack 6a, a very stable environment.
I never get a blue screen of death even IF VisualAge terminates abnormally.
I am running VisualAge for Java Enterprise, 3.5.2.
It generally is VERY good.

The REALLY good news is nothing is LOST if the environment
crashes except the current method you were editing that hasn't been
saved.  All your work exists in the repository file (ivj.dat) that
you can recover to your workspace after fixing the workspace image....

When you have repeated crashes in VisualAge like you mention:

1 Your image file ( ide.icx) probably has a corruption in it somewhere.

2 You can try to clear any corrupted cached classes that may cause the
problem first:

  workbench | windows | options | general | cache
  clear memory cache
  clear disk cache
  then apply
  then ok to exit
  then exit VisualAge normally
  AFTER restarting VisualAge the cached objects are cleared.

IF this doesn't work, try unloading and reloading your custom applications

3 Unload and reload your applications to the workspace

Put all your custom applications in a single Solution object in the
repository.
Delete the applications from the workspace.
Again, clear the cache in step 2.
Exit VisualAge.
Start VisualAge.
Reload the Solution set bringing in all your applications.
If you still have a problem, it is with a Java or VisualAge class, not your
work.

IF this doesn't work, the you must rebuild your image file
from a backup copy....

4  Get a new IDE.ICX file and update your workspace

First save all your current work in a Solution object in your repository
(ivj.dat FILE) per instructions above.

Get a GOOD backup copy of IDE.ICX and copy over the one you have.
(preferrably you saved one at install time from the fix pack or the
original install that we KNOW is clean).

Restart VisualAge with the clean workspace image file.
Reload the Java and IBM features you had loaded before to your workspace.
Reload your applications from the Solution in the repository.
Save your workspace.

You should be fine.

I've never had a failure like you describe that couldn't be corrected
this way.

The "blue screen" of death is an OS failure in your fix packs and OS.
An application failure shouldn't crash the OS...

Jim Mason


Message text written by INTERNET:JAVA400-L@midrange.com
>
Sorry that you're having problems.  What version of VAJ are you on and
what platform.  I'm on Enterprise 3.5.3 and it has been very stable
under Win2K.

Gary

ashaikhhafiz@chubb.com wrote:
>
> Hi!
> I have this problem when running Visual Age.
>
> when i'm working on VAJava, when i'm making some changes and click to
save,
> it closes abruptly and all the changes that i have
> made are lost, then i have to redo them all over again. The second
problem
> is also related to this. in this case when i make some changes and click
to
> save, the crash debug blue screen comes out. nowadays it's happening like
> atleast 10 to 15 times a day. It is really frustrating because i have to
> keep doing the same changes again and again all over. so i sort of tried
to
> get over this by importing the classes everytime i make changes, so that
i
> don't forget the changes i've done and i can start from the point the
last
> import was done. but then every time either VAJava closes abruptly or the
> crash debug comes and the machine reboots, i have to import back the
> changed classes. but it so happens that when i'm importing, it closes
> abruptly. it's become very difficult for me to fix bugs and make changes.
> sometimes the whole screen hangs and the mouse and key board are locked
> out. then i have to power down and power on my machine again. It never
use
> to happen in the earlier days when i was working on java on the jdk
swing.
> but now
>  after the integration of the application codes it has started happening.
> the no of application classes and the codes are extensive. i also open up
> the ie browser to do the testing on the websphere test environment and
> connect to the AS400 to check if the datas coming to the browser are
> synchronous or not.
>
> mine is a IBM Personal Computer 300GL where the config is PIII450
processor
> and a ram of 128MB.
> I would be very happy if someone and especially from IBM help me on this
so
> that i don't have to keep worrying always that anytime either VAJava will
> close
> or the System would be locked or the crash debug will appear and the
> machine would get rebooted.
>
> now even though the RAM has been upgraded to 256 i have the same
problems.
> Thanks in Advance for the solutions.
>
> Thanks & Regards
> Azeem.
>
> Office Tele : +65 - 3359 570
> Res    Tele : +65 - 5659 761
> Mobile         : +65 - 9621 6556<

+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---