|
I have been investigating this problem and I think I might have a fix for it. This is what I have done to simulate the problem. I opened a host file on my CODE editor, and made a change to it. Then on my AS/400, I ended the server job. When the job is completely gone on AS/400, then I did a save. In my case, I even got an exception, and CODE editor crashed. I just wonder if Tom or Peter would help me to verify if my changes have fixed their problem by trying out my personal copy of the CODE dll and exe? Thanks! Hak Lui AS/400 AD, IBM Canada Ltd. e-mail: haklui@ca.ibm.com Hak Lui/Toronto/IBM@IBMCA@midrange.com on 12/21/2001 01:01:29 PM Please respond to code400-l@midrange.com Sent by: code400-l-admin@midrange.com To: code400-l@midrange.com cc: Subject: Re: Code 400 ate my program I think the problem here is that when the line is down, 'save' should be able to detect it and and re-connect. If 'save' failed, then the copy should be kept on the editor window. I am investigating it now. Hak Lui AS/400 AD, IBM Canada Ltd. e-mail: haklui@ca.ibm.com "Larry Paque" <larry@paque.net>@midrange.com on 12/20/2001 11:14:31 AM Please respond to code400-l@midrange.com Sent by: code400-l-admin@midrange.com To: <code400-l@midrange.com> cc: Subject: Re: Code 400 ate my program I definitely have problems with timeouts and our firewall. I've gotten into the habit of saving every time I leave my desk. I also set the autosave parameters to be very short. It sure would be nice if code did some sort of keep-alive activity so that the firewall did not close the connection. Larry ---------- Original Message ---------------------------------- From: P.Goovaerts@Clipper.Be Reply-To: code400-l@midrange.com Date: Thu, 20 Dec 2001 10:12:48 +0100 > >Same happenend here twice! > >At first, I though it had something to do with having loaded a program in >Code/400 over midday-break. When I went back and saved the source, I got >the same type of error (not sure about the number). Result: source lost, >we had to retrieve the backup version. Luckely the changes were minor... > >Last week, it happened again. This time I was working on the code, went >for a coffee and when I came back and saved my source, I got the error >again. Result, source lost! This time I lost 3 hours work! I found a >temp-version on my PC but still, a lot of work was lost. > >btw, I noticed that the source on the AS400 was (almost) exactly cut in 2. >First crash: approx. 2400 sourcelines, approx. 1200 left >Second crash: approx. 4300 sourcelines, approx. 2150 left > >I tried to check what has changed on both PC and AS400 because it never >happened before. The only thing I could trace is that the 'connection time >out' for AS400-folders were changed to 10min. iso 2 hours. We changed it >back to 1Hour and awaiting if it happens again. > >anybody else having this behaviour? > > __________________________________________________ D O T E A S Y - "Join the web hosting revolution!" http://www.doteasy.com _______________________________________________ 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. _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.