|
I wish I could remember better the exact circumstances where I lost source. Each time has involved cases where a record format contained errors. The result was that most of the record format disappeared. I can't remember if it was a compile or a save. Designer crashed a couple of times today when I was moving fields from one record format to another in a print file. I really like this, or its ideal, better than the green screen tools. -----Original Message----- From: hockings@ca.ibm.com [mailto:hockings@ca.ibm.com] Sent: Wednesday, April 24, 2002 3:01 PM To: code400-l@midrange.com Subject: Re: designer reliability was RE: Another Code Oddity This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Designer is very reliable, if you do the same thing it will crash the same way. But I'm (slowly) working on changing that, one crashlet at a time. You can also make checkpoints of your code either manually (file->make_checkpoint) or automatically (tools->settings->saving). That might save you a bit of work. I'd like to understand better why source is being lost at save time. Currently what Designer does is to generate the source to a local (temp) file then call the comm layer to send it to the iSeries. What I don't know if it is the writing to the local file that is failing or the transport to the iSeries that is failing. Maybe I need to create an auto-checkpoint out of the temporary file generated at save time. If you are not seeing any errors at save time then Designer isn't detecting any problems but maybe you notice a difference between a "good" save and a "bad" one? Any insight might be helpful... Kind regards, Mike Mike Hockings, P.Eng. WebSphere Development Tools for AS/400 - CODE/Designer & WebFacing ! IBM Canada Ltd. Laboratory hockings@ca.ibm.com voice 905 413 3199 Joel Fritz <JFritz@sharperimage.com> Sent by: code400-l-admin@midrange.com 24/04/2002 05:10 PM Please respond to code400-l To: "'code400-l@midrange.com'" <code400-l@midrange.com> cc: Subject: designer reliability was RE: Another Code Oddity The windows and buttons are fine--some of them actually make it easier to work. Many of the field attribute/property things that require going through a couple of layers of menus in SDA are easily available. It's the little incidents that result in lost source that are more annoying. I've learned not to delete the spool files from my most recent compiles. They've saved me two or three times in the last month. I'm working on a print file right now and have had two crashes (non-destructive) in the last three hours. v5, latest service pack. -----Original Message----- From: Chris Proctor [mailto:cproctor@gartsports.com] Sent: Wednesday, April 24, 2002 1:59 PM To: 'code400-l@midrange.com' Subject: RE: Another Code Oddity This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Right on, John! I'm with you there. I've went into it a few times, but then I see all the windows and buttons and say to myself, "It ain't worth it!". ha ha Chris -----Original Message----- From: John Taylor [mailto:jtaylor@rpg2java.com] Sent: Wednesday, April 24, 2002 2:54 PM To: code400-l@midrange.com Subject: Re: Another Code Oddity Mark, > The number of these 'bugs' goes up in orders of magnitude in Designer. Agreed. The only thing I use Designer for is reports, because it's less painful than RLU. But I still find myself firing up SDA for screens. I prefer Designer over SDA, but it's just not stable enough yet. Way too many bugs. Regards, John Taylor _______________________________________________ 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. _______________________________________________ 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.
midrange.com
