Change, Risk, Audit and Compliance Management
zOSEM offers a methodology and ISPF interface to provide today's data center a proactive solution to the challenges of fewer systems programmers. It also offers an opportunity to make the task of managing system environments an administrative one, rather than a technical programming issue. zOSEM makes it much easier for installations to manage system resources and to control how they are used.
P-Tracker collects usage information on all program and subprogram calls under z/OS including Batch, IMS/DC, CICS, TSO and other sub-system environments. Using P-Tracker, one can focus in on usage of modules, datasets, applications and products/licenses; and with inhouse applications determine the chained calls at sub-program level. One can quickly and easily identify applications and products that are unused, under-used, duplicated or scattered. Automatically collects information on every module invocation on the system, including sub-system level transactions when required.
ICE - IMAGE Control Environment detects changes, points of failure, and risks to the integrity of the z/OS systems. ICE help systems staff to examine the system and document for management, security and audit teams, that their job is being done correctly, has been verified and does not have further unintentional adverse impact outside of where the change was made.
A background monitor activates a virtual IPL for each image (and its alternate images) using the zOS-Inspector, Sysplex-Inspector, and primary sub-system inspectors (e.g. JES, VTAM, TCPIP) maintaining in-depth change-management and documentation of your images. Additionally for DR purposes ICE runs as a started task directly under z/OS and automatically creates and maintains full screen access, ISPF/PDF, to its own z/OS sub-system when VTAM, JES or TSO are unavailable giving various system management and recovery functions.
The Control Editor environment ensures the complete picture and control of the exact changes that your administrators and operators make to your systems, while seamless to your current change management processes. Capture changes at dataset level, member level, at operator command level and security command level.
SAE - Stand Alone Environment allows access to z/OS volumes and datasets without having an z/OS active. Full range of ISPF like features, Fast DASD Erase to delete a farm in less than 30 minutes with audit report, and Dataset Utilities to ensure critical datasets are always immediately accessible including restore of datasets from DFDSS & FDR volume backups. SAE itself IPLs in 7 seconds, where normally your start-up pack requires 15 to 30 minutes. Essential to any disaster recovery plan as you execute your plan faster and have your production system up and running quicker, and avoid any backouts.
Dealing with IP and Related Issues...
TCP Problem Finder will allow you to see patterns in TCP, UDP, or ICMP traffic. As serious systems programmers know, many problems in the stack, network, or devices can be found this way. The TCP Problem Finder finds errors or inefficiencies in configuration or performance of TCP, UDP, socket applications, interfaces, network hardware, or routes.
SSL Problem Finder will allow you to decode the traces for SSL or AT-TLS traffic. Secure Sockets Layer (SSL) is being widely implemented to protect TCP application traffic. SSL Problem Finder will help you diagnose problems with connection setup and negotiation. You can view problems with certificates, encryption algorithms and much more.
IPV6 Problem Finder will not just help you diagnose problems with IPv6, it will help you learn and understand all the new protocols which are a part of IPv6. Used to perform root cause analysis; Analyze DNSv6;Explain multicast, link-local, ULA address types; Decode ICMPv6; Match tunneled packets;Compare IPv4 / IPv6 capacity and throughput, and do it lots faster than you could do it manually.
DNS Problem Finder - Domain Name System (DNS) is critical to the functioning of networks. Slowdowns in DNS can cause unforeseen slowdowns in application traffic. DNS Problem Finder allows you to see errors and response times for unicast and multicast DNS. Analysis of both IPv4 and IPv6 DNS queries is supported.
Inside the Stack provides case studies and structured knowledge integrated with live data from your z/OS system so you can solve complex performance problems quickly. Inside the Stack provides a complete TCP/IP monitor. Is your boss asking you how much FTP traffic you have? Is TCP/IP a black box to you? With Inside the Stack, you can truly view what is going on inside the TCP/IP stack!
Availability Checker provides a way to check the availability of routes and devices from the mainframe. An ICMP Ping will be sent from the mainframe to the devices defined. Availability Checker keeps track of the network response time (Hourly, Daily, Yearly) and automatically provides Unavailable Resource reports.
Application Checker - The Application Checker provides a way to check the availability of TCP applications (listening local ports) on servers or other mainframes from a mainframe in the enterprise. Application Checker goes beyond merely checking the status of the application as shown by commands! Application Checker attempts to connect to the application via a TCP socket open to make sure the application truly responds.
Early Warning System provides proactive monitoring. Do you have certain TCP connections which MUST be up for business reasons? Have you ever wanted to know if your mainframe-based web applications were running slowly? The Early Warning System provides a ‘heads-up’ for TCP connections or applications which may be heading for trouble. That is, they may be currently experiencing performance problems or will soon be experiencing performance problems. Don't you want to know where pending problems may be BEFORE your customers start calling? Early Warning System is a pure mainframe application.
Connection Log is a pure mainframe application. The Connection Log provides a simple way to view TCP connections for the mainframe TCP stack. You do not have to run programs against the live SMF datasets. Why would someone want a Connection Log? You may want to see who is using the TCP/IP network. A user may be having problems connecting to an application or you may want to make sure that activity is indeed happening for a particular application. You may also be having problems with connection failures. Some applications if they are running out of capacity will send a reset to terminate the connection. You may want to know if all connections for an application for the last 10 minutes have terminated with a reset. The Connection Log shows you all TCP activity as it happens.