|
Oh, there's a recovery facility in CODE? Another April Fool's joke I'm sure...I crash 2x-4x daily and a recovery facility is news to me. I've always had to go digging into TMP to recover to source. Then I have to kill the server job with the lock on the member so I can replace the source member. Sorry to be cranky, but it's the way it is... -rf -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On Behalf Of Joe Pluta Sent: Wednesday, October 09, 2002 5:33 PM To: midrange-l@midrange.com Subject: RE: Tabs in SEU > From: rob@dekko.com > > The biggest problem is that SEU is so full of bugs compared to Code/400. > However the SEU bigots call these bugs 'limitations'. And they believe > that if it can't be done in SEU then it really can't improve their > productivity. I guess I'm clueless here. I use both SEU and CODE/400, but if you had to classify me, I'd be more towards the SEU end of the spectrum. And while I've created thousands of source members with SEU, I must not be a power user because I can't remember the last time I saw an SEU bug. And I love the PDM interface. One relevant issue: if I'm in CODE/400 in one window and SEU in another, and my PC crashes, I'm far more likely to be able to recover my changes with SEU than with CODE. Personal experience of course, but I still think SEU is a really productive interface. Joe _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-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.