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


Sample network configuration

Networking on z/OS

See the latest information on:

Organizations run many of their mission-critical applications on the mainframe and system availability is a key factor in maintaining an organization's business. To meet this goal, organizations duplicate hardware and software components.

There is no single solution that fits all, but the general principal of hardware and software failover and dynamic takeover is very attractive to organizations.

The key points are:

  • Most organizations will have two or more central processor complexes (CPCs) to allow for scheduled and unscheduled outages.
  • Most organizations will have a geographically isolated site to allow for disaster recovery situations.
  • OSA cards can be shared among LPARs on a CPC.
  • TCP/IP VIPAs are not associated with a physical interface, and they assist in maintaining availability for applications and users.
  • Requirements for a mainframe network
    Businesses require their networks to be reliable, always available, and fast. They invest a great amount of time and money creating an IT infrastructure that supports these goals. The extent to which an organization implements a solution depends very much on availability and performance goals balanced against the cost of the solution.
  • Example: the ZOS Company data center
    The sample configuration illustrates a medium-to-large z/OS data center. Processing is divided up physically by central processor complexes and logically by logical partitions.
  • Key mainframe network availability aspects
    The extent to which organizations go in order to ensure a high availability z/OS networking environment varies.
Parent topic: Introduction to networking on the mainframe

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS



Copyright IBM Corporation 1990, 2010