Networking on z/OS
Previous topic | Next topic | Contents | Glossary | Contact z/OS | PDF


TCP/IP clients

Networking on z/OS

z/OS supports all the well-known servers. In addition z/OS supports all of the well-known IP client applications.

Some of these applications are:
ftp
The FTP client can be run from either a TSO environment or from the z/OS UNIX environment. The FTP client is heavily used on z/OS because it runs very well as a batch job. Large file transfers are scheduled for running on weekends or in the evenings and the JCL is submitted, and often evaluated for success, automatically.
telnet
The line mode telnet client is a TSO application only. This application does not get a tremendous amount of use because z/OS is not a platform that lends itself to being a client (using z/OS to run your telnet client is overkill).
ping
No IP implementation is complete without the ability to perform rudimentary connectivity tests. The ping command can be run from either the TSO or z/OS UNIX environments.
tracerte
traceroute
On the MVS side of z/OS, there is a limit of eight characters for the length of a command. So, traceroute had to be shortened to tracerte when executed from a TSO environment. However, within the z/OS UNIX environment, the command is traceroute as would be expected. The traceroute command performs the UDP expired datagram method of testing the reachability of every hop in a network path.
snmp
If an end user wants to perform rudimentary Simple Network Management Protocol queries, the z/OS UNIX snmp command can be used. It can also function as a trap (alert message) destination, but on z/OS, there are far better SNMP management environments available.
netstat
The netstat command is probably the most essential IP command used by network administrators. Technically, it is not a client at all, but it is such a well-known and well-used tool that it is included in this list. It runs as a z/OS UNIX command, a TSO command, and it can also be issued as an z/OS system console command.

Character sets - TCP/IP

Although the mainframe uses the EBCDIC character set, this is a not an issue, as all TCP/IP clients do the translation from ASCII to EBCDIC and from EBCDIC to ASCII automatically and transparently to both the end user and the remote application with which it communicates. Of course, some of these applications, like ping, traceroute and netstat, do not require any translation at all.





Copyright IBM Corporation 1990, 2010