01.01.2013 Views

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

CICS Transaction Gateway V5 The WebSphere ... - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

92 <strong>CICS</strong> <strong>Transaction</strong> <strong>Gateway</strong> <strong>V5</strong><br />

In our example, we were using the TCP/IP stack TCPIPMVS on our z/OS<br />

system. However, because we specified ALL for the IPADDRESS of our<br />

TCPIPSERVICE, our <strong>CICS</strong> region is listening on both TCP/IP stacks.<br />

To display the TCP/IP sockets in use by <strong>CICS</strong>, you can use the TSO NETSTAT<br />

command as shown in Example 5-6. This will give you similar information that<br />

you got from the client side. <strong>The</strong> output shows our <strong>CICS</strong> region listening on port<br />

8018.<br />

Example 5-6 MVS NETSTAT<br />

EZZ2350I MVS TCP/IP NETSTAT CS V1R2 TCPIP NAME: TCPIPMVS 18:25:59<br />

EZZ2585I User Id Conn Local Socket Foreign Socket State<br />

EZZ2586I ------- ---- ------------ -------------- -----<br />

EZZ2587I SCSCPJA1 000085F2 0.0.0.0..8011 0.0.0.0..0 Listen<br />

EZZ2587I SCSCPJA1 000085F4 0.0.0.0..8018 0.0.0.0..0 Listen<br />

EZZ2587I SCSCPJA1 000085F0 0.0.0.0..8010 0.0.0.0..0 Listen<br />

To display the TCP/IP sockets in use by <strong>CICS</strong> on the TCP/IP stack TCPIPOE,<br />

you can use the OMVS command netstat /a as shown in Example 5-7. <strong>The</strong><br />

output shows our <strong>CICS</strong> region listening on port 8018 on the TCPIPOE stack.<br />

Example 5-7 OMVS netstat<br />

MVS TCP/IP onetstat CS V1R2 TCPIP Name: TCPIPOE 14:48:01<br />

User Id Conn Local Socket Foreign Socket State<br />

------- ---- ------------ -------------- -----<br />

PMAPOE1 00000037 0.0.0.0..111 0.0.0.0..0 Listen<br />

SCSCPJA1 00000B09 0.0.0.0..8078 0.0.0.0..0 Listen<br />

SCSCPJA1 00000D90 0.0.0.0..8018 0.0.0.0..0 Listen<br />

SCSCPJA1 00000B03 0.0.0.0..8010 0.0.0.0..0 Listen<br />

Traceroute<br />

If the ping command fails to reach a host, then the tracert command can be<br />

used to discover more about the problem. Like ping, tracert tests connectivity<br />

between two network hosts; however, tracert lists each router in the network<br />

between the machine running the command and the destination host.<br />

Sometimes an inability to contact a host is due to one of these routers not<br />

forwarding IP traffic, so tracert can be used to discover which router is<br />

preventing a connection to a remote host.<br />

In Example 5-8 on page 93 we traced the route from our Windows workstation to<br />

our z/OS system using the command tracert wtsc66.itso.ibm.com from a<br />

Windows command prompt.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!