Sat, 28 Aug 1993 17:15:00 GMT

 


----------------------------

All Having now done a search thru the ibmtcp-l archives, I came across the attached post which sums up a reasonable solution to the problem I posted (getting netstat information into automation packages (in my case netview)). Since it is heading towards its first birthday, I figured I'd restate it. Don ****************************************************************** Sender was IBM TCP/IP List <IBMTCP-L@PUCC.BITNET> From was Ernst-Axel Knabbe <R01KNA@DHHDESY3.BITNET> Subject was re: restricting .../ P TCPIP,NETSTAT > Come on IBM, how about providing some tools for TSO? Throw away all > the TPUTs and TGETs and use PUTLINE/GETLINE/PUTGET everywhere. Then > we'd at least have a chance to develop some of these things. This is > not a new request. CMS users can pipe NETSTAT output. Why can't TSO > users have analogous functionality??? I find it very annoying, that our operators cannot use a MODIFY TCPIP,NETSTAT .. command to check the status of TCPIP or MODIFY TCPIP,STOP/START LCS1 to restart an interface. All MVS program products I know offer either MODIFY or use a WTOR to control their address space(s). The primary MVS operating tool is a MCS system console, not a TSO terminal. A.Knabbe



----------------------------

All Having now done a search thru the ibmtcp-l archives, I came across the attached post which sums up a reasonable solution to the problem I posted (getting netstat information into automation packages (in my case netview)). Since it is heading towards its first birthday, I figured I'd restate it. Don ****************************************************************** Sender was IBM TCP/IP List <IBMTCP-L@PUCC.BITNET> From was Ernst-Axel Knabbe <R01KNA@DHHDESY3.BITNET> Subject was re: restricting .../ P TCPIP,NETSTAT > Come on IBM, how about providing some tools for TSO? Throw away all > the TPUTs and TGETs and use PUTLINE/GETLINE/PUTGET everywhere. Then > we'd at least have a chance to develop some of these things. This is > not a new request. CMS users can pipe NETSTAT output. Why can't TSO > users have analogous functionality??? I find it very annoying, that our operators cannot use a MODIFY TCPIP,NETSTAT .. command to check the status of TCPIP or MODIFY TCPIP,STOP/START LCS1 to restart an interface. All MVS program products I know offer either MODIFY or use a WTOR to control their address space(s). The primary MVS operating tool is a MCS system console, not a TSO terminal. A.Knabbe







----------------------------

In article <IBMTCP-L%93082516392484@PUCC.PRINCETON.EDU>, "Donald.Mahler" <TSODM%EZMAIL@PYIBM1.CC.BELLCORE.COM> writes: >Having now done a search thru the ibmtcp-l archives, I came across the >attached post which sums up a reasonable solution to the problem I posted >(getting netstat information into automation packages (in my case netview)). >Since it is heading towards its first birthday, I figured I'd restate it. And what he reposted was this: >Sender was IBM TCP/IP List <IBMTCP-L@PUCC.BITNET> >From was Ernst-Axel Knabbe <R01KNA@DHHDESY3.BITNET> >Subject was re: restricting .../ P TCPIP,NETSTAT > >> Come on IBM, how about providing some tools for TSO? Throw away all >> the TPUTs and TGETs and use PUTLINE/GETLINE/PUTGET everywhere. Then >> we'd at least have a chance to develop some of these things. This is >> not a new request. CMS users can pipe NETSTAT output. Why can't TSO >> users have analogous functionality??? > >I find it very annoying, that our operators cannot use a MODIFY TCPIP,NETSTAT >.. command to check the status of TCPIP or MODIFY TCPIP,STOP/START LCS1 to >restart an interface. All MVS program products I know offer either MODIFY or >use a WTOR to control their address space(s). > >The primary MVS operating tool is a MCS system console, not a TSO >terminal. > >A.Knabbe Looks more like a problem than a solution to me. And the problem of IBM's NETSTAT not being routable to a file (except if you run it in batch) is still with us. In fact, it's also true of the new MVPXDISP command, which is excruciatingly useless as it flies by you on the tube. -- Steve Bacher (Batchman) Draper Laboratory Internet: seb@draper.com Cambridge, MA, USA



----------------------------

In article <IBMTCP-L%93082516392484@PUCC.PRINCETON.EDU>, "Donald.Mahler" <TSODM%EZMAIL@PYIBM1.CC.BELLCORE.COM> writes: >Having now done a search thru the ibmtcp-l archives, I came across the >attached post which sums up a reasonable solution to the problem I posted >(getting netstat information into automation packages (in my case netview)). >Since it is heading towards its first birthday, I figured I'd restate it. And what he reposted was this: >Sender was IBM TCP/IP List <IBMTCP-L@PUCC.BITNET> >From was Ernst-Axel Knabbe <R01KNA@DHHDESY3.BITNET> >Subject was re: restricting .../ P TCPIP,NETSTAT > >> Come on IBM, how about providing some tools for TSO? Throw away all >> the TPUTs and TGETs and use PUTLINE/GETLINE/PUTGET everywhere. Then >> we'd at least have a chance to develop some of these things. This is >> not a new request. CMS users can pipe NETSTAT output. Why can't TSO >> users have analogous functionality??? > >I find it very annoying, that our operators cannot use a MODIFY TCPIP,NETSTAT >.. command to check the status of TCPIP or MODIFY TCPIP,STOP/START LCS1 to >restart an interface. All MVS program products I know offer either MODIFY or >use a WTOR to control their address space(s). > >The primary MVS operating tool is a MCS system console, not a TSO >terminal. > >A.Knabbe Looks more like a problem than a solution to me. And the problem of IBM's NETSTAT not being routable to a file (except if you run it in batch) is still with us. In fact, it's also true of the new MVPXDISP command, which is excruciatingly useless as it flies by you on the tube. -- Steve Bacher (Batchman) Draper Laboratory Internet: seb@draper.com Cambridge, MA, USA






S
e
n
i
o
r
T
u
b
e
.
o
r
g