|
FYI, This bug is fixed in WDSC 5.0 --------------------------------------------------------------------------------------------- Edmund Reinhardt, AS/400 AD Tools, reinhard@xxxxxxxxxx Dept 607, IBM Canada Lab TL 969-4392 Phone 905-413-4392 "jim essinger" <esinger@xxxxxxxx> To: <code400-l@xxxxxxxxxxxx> Sent by: cc: code400-l-bounces@x Subject: Re: CODE400 Lockups idrange.com 17/01/2003 06:06 PM Please respond to CODE/400 Discussion & Support Greetings, I have had this problem for a long time. It seems that it saved, even when the window did not go away. There was a thread to this affect (started by me if I remember right) that should be in the archives. I have not used the designer for a long time, because of other problems I was having, and I have not revisited it since I installed V5R2 on my iSeries and WSDc on my laptop. I have other issues that are slowing me down, so I do my screen coding via the old SDA. I like the concept of the designer, but when it won't do logical files, and has performance and other issues with screens and printers, I'll wait for a bit to let it be fixed. Jim Essinger Senior Programmer/Analyst Student Loan Fund of Idaho esinger @ NOSPAM fmtc . com > We have CODE Designer V4.0 interfacing to V5R1 system (but this > happened when we had CODE V3.5) When you go to save your work or close > the window I get the little "Generating DDS Source" with all the correct > Lib/File/Mbr info , but "Time elapsed" always stays at 00:00:00 and the > window never goes away (unless I click on Stop). > > Most of the time my source does get saved, but I sure don't get any warm > fuzzies from this. How long should I wait? Is it really saving this > time? etc., etc., etc. > > I had hoped that this would go away with the new CODE, but it hasn't. > Is this a known bug? A PTF available? or am I the only one getting this > kind of thing? > > Thanks, > > -- Jim LowAry > HPS - Hubbell Power Systems > > > ********************************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they are > addressed. If you have received this email in error please notify the > system manager. > > This footnote also confirms that this email message has been swept for > the presence of computer viruses. > > www.hubbell.com - Hubbell Incorporated > ********************************************************************** > > _______________________________________________ > This is the CODE/400 Discussion & Support (CODE400-L) mailing list To > post a message email: CODE400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo.cgi/code400-l > or email: CODE400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/code400-l. > > NOTE: WDSc for iSeries disucssion has it's own mailing list. > Information can be found at > http://lists.midrange.com/cgi-bin/listinfo/wdsc-l _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo.cgi/code400-l or email: CODE400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. NOTE: WDSc for iSeries disucssion has it's own mailing list. Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-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.