RE: error window on compiles @ v5r1 OS

[Violaine Batthish <batthish@xxxxxxxxxx>]

Joel,

I haven't been able to get enough time to prove my theory but here it is:
In V5R1M0, the userspace is of a different size.  When the V5R1M0 backend
tries to read the old user space (created prior to V5R1M0), it can't handle
the old data, and therefore can figure out the remote location to send the
compile completion message and events file. Deleting the old user spaces
seems to clear up the problem.

As for rebooting, I'm pretty sure that was overkill :-)
Shutting down the Communication Daemon and all CODE processes would have
done the trick (to properly close down CODE Editor do a File->Exit or is
the window is closed issue CODEEDIT /CM EXIT in a DOS window to ensure all
editor processes are terminated).

Hope this helps!

Violaine Batthish
CODE Project Lead
batthish@ca.ibm.com          IBMCA(BATTHISH)


WDT/400 page:  http://www.ibm.com/software/ad/wdt400
WDT/400 Support : http://www.ibm.com/software/ad/wdt400/support





                      Joel Fritz
                      <JFritz@sharperim        To:       
"'code400-l@midrange.com'" <code400-l@midrange.com>
                      age.com>                 cc:
                      Sent by:                 Subject:  RE: error window on 
compiles @ v5r1 OS
                      code400-l-admin@m
                      idrange.com


                      07/15/2002 02:28
                      PM
                      Please respond to
                      code400-l





Thank you--worked like magic.  The one thing I needed to do in addition was
sign off and reboot.  Would shutting down my code server and restarting it
have had the same effect?

What was in the user space that made the compiles behave that way?