|
We did in a previous release. I think it was V4R1 or 2, but I can't remember, exactly. We are now at v4r5. The issue was that tcp was not fully started when netserver was starting up, and we had to add a dlyjob and some specific commands to our startup program to get it going. I may have communicated those commands here, if you do an archive search you might find them. Sorry I can't be more helpful, but I don't remember the exact syntax. On 7 Feb 2003 at 8:44, Urbanek, Marty wrote: > While you've got you TCP/IP hats on, I don't have a problem starting > TCP/IP, but I have a V5R1 system where the NFS servers will not > autostart. We just began using NFS. I have the checkbox checked in > OpsNav, but it doesn't work. Every time we IPL I have to go manually > start NFS. The manual start works fine every time. > > Has anybody run into this? Is there a green-screen way to set the > autostart for NFS? I've never been a fan of Ops Nav because you don't > know what it's really doing. You check the check-box and it doesn't > work. > > Thanks, > -Marty >
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.