|
Maybe you should have just removed the STRTCP from your startup program when you upgraded to V5 and leave the IPL attribute (see CHGIPLA press F4) to start TCP. I'm sure when you do that IBM has resolved the old timing issue. ...Neil Tom Jedrzejewicz <tomjedrz@xxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 2004/12/15 16:18 To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Re: gateway unreachable On Wed, 15 Dec 2004 14:13:44 -0000, Jonathan Mason <jonathan.mason@xxxxxxxxxxxxxxxx> wrote: > A number of years ago I worked for a company that had problems starting > TCP/IP on a model 520 during the IPL. If they had the STRTCP command in the > start up program TCP/IP would fail and they had to start it manually. The > solution they used was to have the start up program submit a CL program to > batch that did a DLYJOB for 60 seconds and then the STRTCP. You may be > having a similar problem. V5R1 TCP/IP is at times finicky; after upgrading we had troubles with Telnet and some sockets apps not responding. We have a DLYJOB in our startup program to let it settle down before starting the TELNET server and sockets jobs, and it has worked like a charm since. -- Tom Jedrzejewicz tomjedrz@xxxxxxxxx
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.