Network operational tasks

The role of a z/OS network administrator can span a wide area. In some organizations you might be a generalist, looking after all z/OS networking components, printer subsystems, and even some of the hardware. However, it is more likely that you will specialize in one or two particular areas, such as VTAM and TCP/IP.

Note: This section refers to the "network administrator" as the person who might design, control, monitor, and manage the use of the z/OS networking software and the associated network.

In some organizations, this role might be subdivided. For example, a system operator might be responsible for monitoring and controlling simple aspects of the network only, while the network administrator handles design and management. Regardless, in this section network administrator encompasses effectively all aspects relating to the continuous running of a network in a z/OS context.

"Monitoring" means watching and observing, normally to see something change. This does not imply that you sit there all day watching a screen. There are network management tools installed on z/OS to capture alert and monitor messages and events. There are also network operations staff who normally are the first level filters for problems.

Note: In a mainframe environment, system automation is relied upon heavily. Operational tasks are changed, and generally simplified, by a system automation package. Some commonly used system automation packages include Tivoli NetView for z/OS and System Automation for z/OS.

System automation is used not only to handle monotonous monitoring and z/OS console watching, but also for error recovery and fault tolerance.