RE: SP3 Error - can't use WDT

Hi Buck,

Actually, the problem you are describing is most likely a different one.
I would bet that the host you connect to probably IPLs/reboots at some
point in the night.

Basically, the problem is that the comm link to the host is unable to
properly detect that the job you were running yesterday, no longer exists.
You are correct in your solution; all CODE processes must be terminated
before being able to reconnect properly to the host.

However, if you did manage to get SP3 applied correctly, you should just be
able to shutdown the server (now available for auto-connect servers in SP3)
and try to access the server again.

I am hoping to have improved recovery from such situations in SP4.

Thanks,

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




                    Buck Calabro
                    <Buck.Calabro@comm       To:     code400-l@midrange.com
                    soft.net>                cc:
                    Sent by:                 Subject:     RE: SP3 Error - can't 
use WDT
                    code400-l-admin@mi
                    drange.com


                    10/02/2001 12:16
                    PM
                    Please respond to
                    code400-l





>Why should this stuff happen EVERY time one upgrades or does most
>anything to WDT?  Am I the only one who feels this way?  Once it's
>working, it's great, but I can sure see why so many try and give up.

I am running W98.  Just installed SP3 and rebooted.  Works for me, no
problems.  However, I have had an odd communications type problem since
SP2.
I mention it now because it may have some bearing on the SP3 problems you
folks are having.  I leave my PC powered on 24x7.  In the morning when I
come in, I need to:

open the comms daemon
  shutdown all servers
  close the daemon

open task manager
  kill EVFWSP40
  kill EVFLGEN

open CPO
  go about my business.

If I open CPO without doing that, I get no error, but the editor doesn't
start.  I looked at the comm log a long while ago but it wasn't that
helpful.  I chalked it up to some oddity of our installation and waited for
SP3 to clean it up.  I don't use a STRCODE session unless trying the
debugger.

May I suggest that you try the same concept?  Kill ALL the Code tasks, then
start CPO.  Let it "auto-start" the comms daemon.

W98 128 meg 67% free with Code editor running.
CAE V5R1 w/SI01907
OS/400 V4R5 TL01100

  --buck
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.