VitalSigns for VTAM, Specifications
VSV 5.1.4 provides monitoring, diagnostic, and performance management capabilities for TCP/IP and SNA environments.
VitalSigns for VTAM provides comprehensive monitoring of any and every host connected, however remotely, to your z/OS, MVS machine by TCP/IP and SNA.
Mainframe Environment:
- z/OS, OS/390, MVS/ESA.
- 8 Mb, minimum, virtual memory for the VSV region.
- 155 cylinders, minimum, 3380 disk space, or equivalent.
- 327x (or compatible) terminals.
- IBM VSAM access method.
VSV Web Server:
- Runs in Unix, Linux, Windows 2000/NT4, or Unix System Services on z/OS, OS/390, or MVS/ESA.
- Includes an Apache Tomcat HTTP Server.
- Runs in ASCII or EBCDIC environments.
- Requires Java 2 Platform, version 1.2 or greater.
- Can run as a service of its host.
Additional requirements vary, depending on what you ask VSV to do:
|
VSV Feature |
Requirement |
|
Monitor
FTP and telnet.
Write SMF records. Password security exit. NetView Interface. |
APF authorization for the VSVLOAD library. APF authorization will set VSV non-swappable. |
|
Monitor TCP/IP, FTP, telnet, sockets. |
IBM TCP/IP 3.4 or higher |
|
Monitor a TCP/IP stack.
|
SNMP agent or daemon (SNMPD) configured and active. Know the IP address, port number, and community name for that agent. |
|
Monitor socket activity. |
TCP/IP configured to create SMF records. SMF configured to allow TCP/IP data. |
|
Monitor Network Token Ring Interface (NTRI)
|
NCP 5.3.1 or higher |
|
Monitor X.25 Network Packet Switching Interface (NPSI) |
NCP 5.3.1 or higher |
|
Reconfiguration support
|
NCP 4.3.1 or higher |
|
Monitor NCP session and gateway accounting |
NCP 4.3 or higher |
|
NetMaster interface
|
System Center’s NetMaster 2.2 or above licensed for ANM and NEWS |
|
NetView interface |
NetView 1.3 or higher |