|
The reason for the 2 systems on in PA the program that WAS primarily running our company wasn't y2k which resided on the F50. So they bought the 620 to run JDE. The goal was to just unplug the F50 but another program runs on it and the timing to take it off isn't appropriate now. The bottom line is there is a LACK of funds going into my department. We have no maintenance on the F50. We just got it on the 620. I just came here a year ago and we are literally cut and pasted together. They don't have the F50 on the network. We don't even have all our users on the network. They are not big e-mail users either. get the picture? Chris - you had some good ideas and maybe I'll take the time to get the F50 on the network because even if we got everything off the F50 today, our acct dept is still running year end reports off that system to compare w/ the new. We just closed our year last month. Thanks for the great response from all. It just helps my case. -----Original Message----- From: nina jones [mailto:ddi@datadesigninc.com] Sent: Friday, April 07, 2000 2:49 PM To: MIDRANGE-L@midrange.com Subject: Re: communications > Please convince my mgmt what the problem is. > > I have remote users in NY residing on an E10 V3.2 passing through (appc 64K) > to an F50 V3.2 in PA, some using a program called ELKE on the F50. These > same ELKE users (off the F50 from the E10) are passing through via Modem > Eliminator to the 620 V4.2 (which physically sits next to the f50) using > JDE. > > Problem: The NY users say ELKE responce time is fine but JDE responce time > stinks.... To draw it out for you: > > E10(NY) -> F50(PA) -> 620(PA) then sending splf etc back > 620 -> F50 -> E10 > > Why do you think? My mgmt wants explaination. I told them we are using an > F50 as a server and it is NOT intended for this use. Maybe if they hear it > from 20 other opinions it will help my case. any reason there are two systems in pa? and the maintenance on the f50 must be a killer. nj +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.