You have to specifically tell VM:Secure to give TCPIP rights (I gave it R/W because I was in a hurry at the time and didn't want to take the time to experiment w/ R/O and then maybe R/W) to link to your 191 disk.
And, the message you get when you don't have that authorization set, as I recall, is very cryptic. I only discovered the link access problem when my IFCONFIG command failed and I saw a password prompt message in the TCPIP console log and guessed at what it was trying to do.
I agree the mdisk link technique is pretty crude; it would be nice if IFCONFIG could communicate via SMSG or some other messaging facility, but that's an enhancement, I guess.
Dennis Schaffer
-----"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> wrote: -----
To: IBMVM@LISTSERV.UARK.EDU
From: "Shimon Lebowitz" <[EMAIL PROTECTED]>
Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU>
Date: 07/27/2006 12:58AM
Subject: Re: How to diagnose a gateway problem in TCP/IP?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?)
