My first posting in that old thread said OBEYFILE, and Alan had some juicy comment at that idea. He suggested NETSTAT OBEY, which I have not looked at yet, but is apparently an easier way to deal with OBEYFILE.
I mentioned that nowadays I use IFCONFIG <if> DOWN or UP. These commands require that you have a R/W mdisk currently accessed, but I don't remember running into TCPIP link problems. (Or maybe that is just because VM:Secure gives TCPIP r/o rights to my mdisk?) In any case, I believe there is an option to pass a password (<g>). I am home... so I am not checking this right now. I definitely remember in the past tearing my hair out trying to get TCPIP to do something, and having it come up against this 'link to the mdisk' problem. What it really needs is a better command interface, such as SENDFILE, where it can accept and run the file (if it comes from an authorized user), or perhaps just accepting SMSG commands. And what is so terrible about SFS? Who has an MDISK??? Shimon On 26 Jul 2006 at 15:31, Tom Cluster wrote: > I'm sorry, but I'm really sort of confused. > > Shimon pointed out that I could use OBEYFILE, and I went to the > section in the Planning and Customization Guide that he mentioned, > with some trepidation, because I had vaguely remembered that there's > a whole issue about getting TCPIP to see the minidisk where the file > being obeyed is placed, and of course I've run right smack into > it. > > Can someone please remind me where I put the file? The userids on > my > system who can issue the OBEYFILE command are TCPMAINT and MAINT. I > tried TCPMAINT's 191 but I got "Unable to read file..." So I figure > that's because TCPIP hadn't accessed this mindisk when he came > up. Fair enough. But he DID access TCPMAINT's 198 as D, so I put > the file on TCPMAINT's 198, and issued the following command from > TCPMAINT: > > obeyfile stopit tcp d (rtcpip tcp tcpip > > and I get a VM READ. When I press ENTER I get "Unable to read > file..." > > The fact that I got a VM READ in the one situation and not in the > other tells me that there's a difference between the two > situations. Like maybe I'm getting warmer. What is TCPIP looking > for in order to allow him to re-access a disk that he already has > linked? > > And I'm completely blown away by NETSTATE OBEY ... - how does this > relate to OBEYFILE? > > - Tom. >
