|
Are the mainframes/remote computers all trying to connect using the same profile? Is your network bandwidth pegged from one mainframe connection thus a second connection timing out? Can you increase the mainframe FTP client timeout value? How many simultaneous connection are present when the failure happens? Is there routers and or bridges between the systems? Hopefully this raises enough question to help you solve your problem. Please let us, (the list), know what fixes the problem. Christopher K. Bipes mailto:ChrisB@Cross-Check.com Operations & Network Mgr mailto:Chris_Bipes@Yahoo.com CrossCheck, Inc. http://www.cross-check.com 6119 State Farm Drive Phone: 707 586-0551 x 1102 Rohnert Park CA 94928 Fax: 707 586-1884 -----Original Message----- From: D.BALE@handleman.com [mailto:D.BALE@handleman.com] Sent: Wednesday, May 09, 2001 8:50 AM To: MIDRANGE-L@midrange.com Subject: "Cannot Connect" FTP Invariably and unpredictably, a mainframe FTP job will abend with "Cannot Connect". A few minutes later, another mainframe FTP job will run successfully. I've been asked to look at the AS/400 side to see if there's anything we can do to keep this from happening. This is NOT my area of expertise. What I've noticed is that our branch boxes have numerous QTFTPnnnnn jobs, for example, our Indianapolis box has 13 of these jobs "active". When I prompt CHGNETA on this box, the "Number of initial servers" is set to 5. I presume (awaiting correction from the list) that somewhere along the line since the last IPL in October, we had 13 FTP server jobs actively transferring files from the mainframe to the AS/400. So, I have been asked to consider changing the "Number of initial servers" to the maximum of 20, with the goal of minimizing the "Cannot Connect" mainframe abends. This doesn't make complete sense to me, but I'd be willing to try it if there's no downside to doing so. I presume that if a server job is not in use, eventually it gets paged out of memory with no hit on performance. Or are we slaying the wrong dragon? +--- | 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-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.