IBM® InfoSphere™ Classic Federation Server for z/OS® offers direct virtualized SQL access to mainframe data sources.
It supports Windows® and UNIX® tools and applications and provides federated read and write access to data stored in a wide variety of databases.
- Can access data stored in VSAM, IMS, CA-IDMS, CA-Datacom, Software AG Adabas, and DB2® UDB for z/OS® databases by dynamically translating JDBC and ODBC SQL statements into native read/write APIs.
- It is driven by metadata that contains a mapping of physical databases and files to logical relational tables, mainframe data appears to be one relational database and supports SELECT, INSERT, UPDATE, and DELETE SQL statements and stored procedure calls.
- Delivers enterprise-wide structured and unstructured data integration when combined with InfoSphere Federation Server.
- InfoSphere Classic Federation Server for z/OS includes improved DB2 data access performance, 64-bit client platforms, enhanced automation of support for redefined data, as well as improved flexibility in handling IMS PCB selection.
- Helps automate the creation of metadata for more users and extend visual metadata management to more complex scenarios - this improves the usability of the tool while also enabling more rapid metadata creation and management.
- Simplifies the management of the operational platform and performance optimization processes by providing an interactive view of the actual settings as well as a means for temporarily and permanently changing configuration settings.
- Dynamic integration of z/OS sequential file data for ETL processing with no need to unload or FTP files to the ETL (InfoSphere DataStage) platform.
Learn more
InfoSphere Classic Federation Server for z/OS
IBM Software Subscription and Support is included in the product price for the first year.
Not available to purchase online. Other ways to purchase or learn more.
Contact IBM
- Request a quote
- E-mail IBM
- Or call us at: 1800 3172 782
Priority code: 109HF03W
Features and benefits
With 60% of business data residing on the mainframe, mainframe data access is important to the success of many of today's business-critical IT initiatives including:
Delivering mainframe operational data to customer self-service Web sites
Connecting e-commerce sites with mainframe inventory data
Integrating business intelligence systems in real time with mainframe accounting data
Connecting an enterprise portal to mainframe human resources data
IBM® InfoSphere™ Classic Federation Server for z/OS® provides direct, real-time SQL access to mainframe databases and files without mainframe programming. It maps logical relational table structures to existing physical mainframe databases and files. UNIX, Windows®, and Linux tools and applications issue standard SQL commands to these logical tables.
InfoSphere Classic Federation Server for z/OS dynamically generates native data access commands that are optimized for each database and file type. Results are automatically translated and reformatted into relational rows and columns providing seamless integration of all mainframe data assets without proprietary programming.
The business benefits of InfoSphere Classic Federation Server for z/OS include:
Extending the value of existing mainframe investments. Rather than ripping out and replacing mainframe assets, clients can extend these investments to deliver new business applications or integrate business operations.
Reducing time-to-value for integration projects that require mainframe data by eliminating proprietary coding and multi-platform development and automating complex multi-source integration.
Minimizing dependence on scarce legacy data skills by empowering non-mainframe staff to automatically leverage legacy data sources without investing in the proprietary skills associated with these data sources.
Empowering IT to rapidly deliver information rich business solutions that present up-to-the second information rather than stale copied data.
InfoSphere Classic Federation Server for z/OS can also extend IBM® InfoSphere Federation Server's access to nonrelational mainframe data sources. InfoSphere Classic Federation Server for z/OS lets applications access diverse and distributed data -- including multi-vendor mainframe and distributed, structured and unstructured, public and private -- as if it were a single database.
Classic Federation Server 10.1
| Operating System | Software | Hardware |
|---|---|---|
| z/OS | z/OS® 1.10, 1.11, 1.12, or 1.13 | Run-time memory: 1 MB for each concurrent user; minimum 32 MB recommended LibraryType: Target Total Space Required in 3390 Trks: 3061 tracks Temporary storage to process user queries: Twice the size of the total result set Disk space: 2 MB Run-time memory: requirements are negligible |
Classic Federation Server Client v10.1
| Operating System | Software | Hardware |
|---|---|---|
| AIX | AIX® 5.2, 5.3, 6.1 | CLI Client requirements: - Supported on 32-bit and 64-bit systems - Disk space: 80 MB; CLI Client installer requires an additional 90 MB. - Run-time Memory: 16 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
| HP-UX | HP-UX , 11iV3 | CLI Client requirements: - Supported on 32-bit and 64-bit PA-RISC systems - Disk space: 80 MB; CLI Client installer requires an additional 131 MB. - Run-time Memory: 16 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
| Linux | Red Hat Enterprise Linux AS 4.0, 5.0 SuSE Linux Enterprise Server 9.0, 10.0, 11.0 |
CLI Client Requirements: - Supported on x86 (32-bit) systems and eServer System z™ or System z9™ (32-bit and 64-bit mode). - Disk space: 80 MB; CLI Client installer requires an additional 90 MB. - Run-time Memory: 16 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
| Solaris | Sun Solaris 9, 10 | CLI Client requirements: - Supported on 32-bit and 64-bit SPARC systems - Disk space: 80 MB; CLI Client installer requires an additional 90 MB. - Run-time Memory: 16 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
| Win XP Pro, 2003, Vista, 2008, Windows 7 | Microsoft Windows 2003 Standard Edition Microsoft Windows 2003 Enterprise Edition Microsoft Windows XP Professional Microsoft Windows Vista Microsoft Windows 2008 Standard Edition Microsoft Windows 2008 Enterprise Edition Microsoft Windows 7 |
ODBC Client requirements: - Supported on 32-bit and 64-bit systems - Disk space: 15 MB; ODBC Client installer requires an additional 90 MB. - Run-time Memory: 1 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
Classic Federation Server 9.5
| Operating System | Software | Hardware |
|---|---|---|
| z/OS | z/OS® 1.8, 1.9, 1.10 or 1.11 | Run-time memory: 1 MB for each concurrent user; minimum 32 MB recommended - WS Classic Data Event Pub for zOS libraries can reside on all supported DASD types. The values below are for 3390 DASD. LibraryType: Target Total Space Required in 3390 Trks: 3061 tracks Temporary storage to process user queries: Twice the size of the total result set Disk space: 2 MB Run-time memory: requirements are negligible |
Classic Federation Client 9.5
| Operating System | Software | Hardware |
|---|---|---|
| AIX | AIX® 5.2, 5.3 | CLI Client requirements: - Supported on 32-bit and 64-bit systems - Disk space: 80 MB; CLI Client installer requires an additional 90 MB. - Run-time Memory: 16 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
| HP-UX | HP-UX 11iV2 | CLI Client requirements: - Supported on 32-bit and 64-bit PA-RISC systems - Disk space: 80 MB; CLI Client installer requires an additional 131 MB. - Run-time Memory: 16 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
| Linux | Red Hat Enterprise Linux AS 4.0 SuSE Linux Enterprise Server 9.0, 10.0 |
CLI Client Requirements: - Supported on x86 (32-bit) systems and eServer System z™ or System z9™ (32-bit and 64-bit mode). - Disk space: 80 MB; CLI Client installer requires an additional 90 MB. - Run-time Memory: 16 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
| Solaris | Sun Solaris 9, 10 | CLI Client requirements: - Supported on 32-bit and 64-bit SPARC systems - Disk space: 80 MB; CLI Client installer requires an additional 90 MB. - Run-time Memory: 16 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
| Windows 2003, Windows Vista, Windows XP Professional | Microsoft Windows 2003 Standard Edition Microsoft Windows 2003 Enterprise Edition Microsoft Windows XP Professional Microsoft Windows Vista |
ODBC Client requirements: - 32-bit systems only - Disk space: 15 MB; ODBC Client installer requires an additional 90 MB. - Run-time Memory: 1 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
Classic Federation Server 9.1
| Operating System | Software | Hardware |
|---|---|---|
| z/OS | z/OS® 1.6 | Run-time memory: 1 MB for each concurrent user; minimum 32 MB recommended Permanent storage: Approximately 160 cylinders of DASD Temporary storage to process user queries: Twice the size of the total result set Disk space: 2 MB Run-time memory: requirements are negligible |
Classic Federation Client 9.1
| Operating System | Software | Hardware |
|---|---|---|
| AIX | AIX® 5.2, 5.3 | CLI Client requirements: - Supported on 32-bit and 64-bit systems - Disk space: 80 MB; CLI Client installer requires an additional 90 MB. - Run-time Memory: 16 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
| HP-UX | HP-UX 11iV2 | CLI Client requirements: - Supported on 32-bit and 64-bit PA-RISC systems - Disk space: 80 MB; CLI Client installer requires an additional 131 MB. - Run-time Memory: 16 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
| Linux | Red Hat Enterprise Linux AS 3.0, 4.0 SuSE Linux Enterprise Server 9.0, 10.0 |
CLI Client Requirements: - Supported on x86 (32-bit) systems and eServer System z™ or System z9™ (32-bit and 64-bit mode). - Disk space: 80 MB; CLI Client installer requires an additional 90 MB. - Run-time Memory: 16 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
| Solaris | Sun Solaris 9, 10 | CLI Client requirements: - Supported on 32-bit and 64-bit SPARC systems - Disk space: 80 MB; CLI Client installer requires an additional 90 MB. - Run-time Memory: 16 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
| Windows 2000, Windows 2003, Windows XP Professional | Microsoft Windows 2000 Professional Microsoft Windows 2000 Standard Server Microsoft Windows 2000 Advanced Server Microsoft Windows 2003 Standard Edition Microsoft Windows 2003 Enterprise Edition Microsoft Windows XP Professional |
ODBC Client requirements - 32-bit systems only - Disk space: 15 MB; ODBC Client installer requires an additional 90 MB. - Run-time Memory: 1 MB JDBC Client requirements: - Supported on 32-bit and 64-bit systems with 32-bit JRE - JRE 1.3, 1.4.2, and JRE 5; internationalized version required for locales other than US English - Disk space: 2 MB - Run-time Memory: 1 MB |
Classic Federation 8.2
| Operating System | Software | Hardware |
|---|---|---|
| z/OS | z/OS® 1.4 | Run-time memory: 1 MB for each concurrent user; minimum 32 MB recommended Permanent storage: Approximately 180 cylinders of DASD Temporary storage to process user queries: Twice the size of the total result set Disk space: 2 MB Run-time memory: requirements are negligible |
Classic Federation Client 8.2
| Operating System | Software | Hardware |
|---|---|---|
| AIX | AIX® 5.1.0 JDBC client requires JRE 1.4 or higher |
JRE 1.3 client requirements: - Disk space: 2 MB - Run-time memory: requirements are less than 1 MB CLI client requirements: - Disk space: 2 MB - Run-time memory: requirements are less than 1 MB |
| HP-UX | HP-UX 11.01 JDBC client requires JRE 1.4 or higher |
JRE 1.3 client requirements: - Disk space: 2 MB - Run-time memory: requirements are less than 1 MB CLI client requirements: - Disk space: 2 MB - Run-time memory: requirements are less than 1 MB |
| Solaris | Sun Solaris 2.7 JDBC client requires JRE 1.4 or higher |
JRE 1.3 client requirements: - Disk space: 2 MB - Run-time memory: requirements are less than 1 MB CLI client requirements: - Disk space: 2 MB - Run-time memory: requirements are less than 1 MB |
| Windows NT, Windows 2000, Windows XP Professional | Microsoft® Windows NT® 4.0, Microsoft Windows® 2000, Microsoft Windows XP, Professional (32 bit) JDBC client requires JRE 1.4 or higher ODBC client requires TCP/IP or Websphere® MQ Version 5 Release 0 or higher |
Data Mapper requirements: - Disk space: 15 MB - Run-time memory: 16 MB RAM JRE 1.3 client requirements: - Disk space: 2 MB - Run-time memory: requirements are less than 1 MB ODBC client requirements: - Disk space: 2 MB - Run-time memory: requirements are less than 1 MB |
Information integration and governance
- Data integration
- InfoSphere Business Glossary
- InfoSphere Business Glossary for Linux on System z
- InfoSphere Change Data Capture
- InfoSphere Change Data Capture for z/OS
- InfoSphere Classic Connector for z/OS
- InfoSphere Classic Data Event Publisher for z/OS
- InfoSphere Classic Federation Server for z/OS
- InfoSphere Classic Replication Server for z/OS
- InfoSphere Clinical Analytics
- InfoSphere Data Architect
- InfoSphere Data Event Publisher
- InfoSphere Data Event Publisher for z/OS
- InfoSphere Data Replication
- InfoSphere DataStage
- InfoSphere DataStage MVS Edition
- InfoSphere Discovery
- InfoSphere FastTrack
- InfoSphere Federation Server
- InfoSphere Global Name Analytics
- InfoSphere Information Analyzer
- InfoSphere Information Server for Data Warehousing
- InfoSphere Information Server for System z
- InfoSphere Information Server
- InfoSphere Information Server Ready to Launch for SAP Applications
- InfoSphere Information Server Workgroup Edition
- InfoSphere Information Services Director
- InfoSphere Master Data Management
- InfoSphere Metadata Workbench
- InfoSphere Optim Application Repository Analyzer
- InfoSphere QualityStage for z/OS
- InfoSphere Replication Server for z/OS
- InfoSphere Replication Server
Considering a purchase?
Contact IBM
Considering a purchase?
- E-mail IBM
- Request a quote
- Or call us at: 1800 3172 782
Priority code: 109HF03W