Skip to end of metadata
Go to start of metadata
 Click to expand table of contents...

Content



Created  

Updated 


Summary

Below are the minimum requirements and recommendations for optimal z/IRIS processing.


z/IRIS Linux Server (a.k.a. IronTap)

Requirements and recommendations below should achieve an average processing throughput of 10,000 SMF records per second. Users should adjust the following requirements as needed to achieve the required SMF processing throughput in each environment.

Hardware requirements 

CPU

Quad Core Processor (2,5 GHz) x86_64 compatible (e.g.: Intel® Core™ i5-2400S Quad-Core Processor 2.5 GHz, Intel® Core™2 Quad Processor Q8300, AMD A6-6310 Quad-Core Processor or higher)

RAM2 GB
Storage10 GB

Software requirements

Recommended Linux distributions

Ubuntu 16.04+, Debian 7+

Compatible with virtual machines.


Important

Supports operating systems with English language support only.

Java platform

OpenJDK 11

AdoptOpenJDK is recommended


z/OS Client

zFS mounted file system

Minimum allocated space2000 KB

Mainframe software requirements

Supported z/OS releasesz/OS 2.1, z/OS 2.2, z/OS 2.3, z/OS 2.4
Required Java platformIBM SDK, Java Technology Edition, Version 8 64 Bit
SMF mode

At least 1 SMF in-memory resource must be defined for any SMF record types that will be streamed via z/IRIS. 

SMF Logstream mode is required to activate SMF in-memory resources.

TCPIPTCP/IP must be active and configured on z/OS.

Depending on SMF record sizes and SMF record type generation frequency, users should ensure that the number of SMF record types in a single SMF in-memory resource will not result in a loss of SMF records due an exceptionally high SMF in-memory wrap-around rate.


Apache Kafka

Supported Version

2.1.0 or newer

Since version 0.10.2 Apache Kafka provides a bi-directional compatibility policy. This means that older versions may work as well.  We recommend always using the latest generally available libraries as they include vital security patches and performance improvements.

Throughput Capability10.000 SMF Records/s (~35.000 KB/s depending on Record Type)

Supported SMF records

SMF Type 30 (1-6)

Common Address Space Work records used to create z/OS Work Traces for partner APM ISVs.

SMF Type 70Mainframe processor utilization
SMF Type 101Db2 (v11, v12) for z/OS accounting records. See Distributed Db2 trace streaming for APM integration for more details.
SMF Type 102Db2 (v11, v12) for z/OS performance records. See Distributed Db2 trace streaming for APM integration for more details.
SMF Type 123 version 1 and 2z/OS Connect auditInterceptor records

Distributed Db2 trace streaming for APM integration 

Db2 for z/OS ReleasesDb2 for z/OS v11, Db2 for z/OS v12
SMF Record Types101-102
Supported JDBC FeaturesJDBC 4.0
Supported IFCIDs

3 (TRACE(ACCTG) CLASS(1-3))

172 (TRACE(PERFM) CLASS(30-32))

58-66 (TRACE(PERFM) CLASS(30-32))