Tom--We use RACF, so I have to do a RACF PERMIT for TCPIP to have read
access to my 191 disk in order to read an OBEYFILE file. Apparently, TCPIP
will re-link and access your disk with every OBEYFILE command. If I
remember correctly, one of the IBM Endicott people said, probably at SHARE,
that TCPIP does not reaccess the TCPMAINT disks after it has started so
that's why TCPIP couldn't find the OBEYFILE on the TCPMAINT 198 disk.
Jim
At 06:31 PM 7/26/2006, you 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.
At 02:40 PM 7/26/2006, you wrote:
>The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> wrote on
>07/26/2006 02:16:19 PM:
>
> >
> > That's the whole point of NETSTAT OBEY and the OBEYFILE commands. They
> > allow you to dynamically change the stack configuration. So my NETSTAT
> > OBEY MORETRACE IPDOWN starts the trace and NETSTAT OBEY NOTRACE IPDOWN
> > stops it. Though I like OBEYFILE for traffic tracing since I want to use
> > TRACEONLY to restrict the traced data.
> >
> > Alan Altmark
> > z/VM Development
> > IBM Endicott
>
>No reason you can't use NETSTAT OBEY in this case as well (unless
>your TRACEONLY statement is too large for the command line):
>
>NETSTAT OBEY MORETRACE IPDOWN TRACEONLY 10.10.10.1 ENDTRACEONLY
>
>NETSTAT OBEY NOTRACE TRACEONLY ENDTRACEONLY
>
>Regards,
>Miguel Delapaz
>z/VM TCP/IP Development
Tom Cluster
County of Sonoma
Santa Rosa, CA
(707) 565-3384 (Tuesdays and Wednesdays only)
Jim Bohnsack
Cornell Univ.
(607) 255-1760
