System Requirements

The following table lists CONNX system requirements, including hardware requirements, for applicable databases and their operating systems.

 

Adabas SQL Gateway (CONNX for Adabas) - Some of this information can also be found in the Adabas for Unix and Windows  Installation Guide, Version 3.3.1, 1999-2003.

Windows

Hardware

N/A

Network

TCP/IP

Operating System

z/OS, Windows

Memory

40 MB

Hard Drive

N/A

 

IBM z/OS

Hardware

z/OS - FTP server required for installation only

Network

TCP/IP (OE stack)

Operating System

z/OS

Memory

 

Hard Drive

 

Security

OSS segment must be defined for the user ID in the security system (RACF / ACF2 / Top Secret) or it must be available by default.

 

VSE

Hardware

IBM VSE

Network

TCP/IP or Barnard TCP/IP Communications Stack

Operating System

VSE

Memory

 

Hard Drive

 

Security

 

 

HP-UX

Hardware

Processor: PA-RISC, 512 MB

Disk space: Installing the optimized version of Adabas requires approximately 45MB. An additional 30 MB are required if a demo database is created during installation. An additional 60 MB are required if you install the trace version of Adabas. These figures do not include disk space requirements for other databases that you will create.

CD-ROM drive: Required.

Software

HP-UX 11.0 (64-bit) or HP-UX V11.11i (64-bit) or  HP-UX 11.11 (32-bit)

Remote Access: ENTIRE-NETWORK 2.1.1 or above is required for remote access from other machines.

 

Solaris

Hardware

Processor: UltraSPARC

Memory: 512 MB

Disk space: Installing the optimized version of Adabas requires approximately 45MB. An additional 30 MB are required if a demo database is created during installation. An additional 60 MB are required if you install the trace version of Adabas. These figures do not include disk space requirements for other databases that you will create.

CD-ROM drive: Required.

Software

Operating System: SUN Solaris Version 7 or SUN Solaris Version 8

Remote Access: ENTIRE-NETWORK 2.1.1 or above is required for remote access from other machines.

 

AIX

Hardware

Processor: IBM e-Server P-Series or RS/6000

Memory: 512 MB

Disk space: Installing the optimized version of Adabas requires approximately 45MB. An additional 30 MB are required if a demo database is created during installation. An additional 60 MB are required if you install the trace version of Adabas. These figures do not include disk space requirements for other databases that you will create.

CD-ROM drive: Required.

Software

Operating System: IBM AIX5L Version 5.1 system maintenance level 2 (64-bit) or Version 5.2

Remote Access: ENTIRE-NETWORK 2.1.1 or above is required for remote access from other machines.

 

Linux

Hardware

Processor: Intel

Memory: 512 MB

Disk space: Installing the optimized version of Adabas requires approximately 45MB. An additional 30 MB are required if a demo database is created during installation. An additional 60 MB are required if you install the trace version of Adabas. These figures do not include disk space requirements for other databases that you will create.

CD-ROM drive: Required.

Software

Operating System: Red Hat 7, Red Hat 9, Suse, Linux 390

Remote Access: ENTIRE-NETWORK 2.1.1 or above is required for remote access from other machines.

 

RMS (any version)

Hardware

Compaq VAX Server, Compaq AlphaServer, Itanium

Network

TCP/IP, DECnet, Phase IV and above

Operating System

OpenVMS

Memory

12 MB VAX, 32 MB Alpha

Hard Drive

20,000 blocks available (10 MB)

 

Codasyl DBMS

Hardware

Compaq VAX Server, Compaq Alpha Server

Network

TCP/IP, DECnet Phase IV and above

Operating System

OpenVMS

Memory

12 MB VAX, 32 MB Alpha

Hard Drive

20,000 blocks available (10 MB)

 

Oracle Rdb

Hardware

Compaq VAX Server, Compaq Alpha Server

Network

TCP/IP, DECnet Phase IV and above

Operating System

OpenVMS, Unix

Memory

12 MB VAX, 32 MB Alpha

Hard Drive

20,000 blocks available (10 MB)

 

Oracle

Hardware

Compaq VMS Server (VAX or Alpha), Personal Computer (Intel)/Alpha Sun/Unix Workstation

Network

SQLNet 2.x

Operating System

OpenVMS (any version), Windows, Unix/Linux (any version)

Memory

N/A

Hard Drive

N/A

 

DataFlex version 2.3 and above

Hardware

Personal Computer (Intel)/Alpha, Unix Workstation

Network

Any file-sharing protocol

Operating System

Windows, Novell Netware, Linux

Memory

N/A

Hard Drive

N/A

 

POWERflex

Hardware

Personal Computer (Intel)/Alpha, Unix Workstation

Network

Any file-sharing protocol

Operating System

Windows, Novell Netware, Linux

Memory

N/A

Hard Drive

N/A

 

OLE DB Providers (Sybase Informix, Microsoft SQL Server, Microsoft Access)

Operating System

Windows, MDAC 1.5 or later (See Notes below.)

 

ODBC Providers (Must support ADO and be fully ODBC Level 2 compliant.)

Operating System

Windows, MDAC 1.5 or later (See Notes below.)

 

C-ISAM

Hardware

HPUX, SCO, Solaris, AIX, Linux

Network

TCP/IP

Operating System

HPUX 10.2+, HPUX64, SUN OS 5.6, SUN OS 5.7+, SCO Openserver release 5, AIX 4.3+, AIX 4.2, Linux 7.2 and 9, or Tru 64 (Unix)

Windows XP/2003/Vista/2008/2008R2/Windows 7/

Memory

N/A

Hard Drive

1 MB

 

DISAM

Hardware

HPUX, SCO, Solaris, AIX, Linux

Network

TCP/IP

Operating System

HPUX 10.2+, HPUX64, SCO Server, SUN OS 5.6, SUN OS 5.7+, AIX 4.3+, AIX 4.2, Linux, or Tru 64 (Unix)

Windows

Memory

N/A

Hard Drive

1 MB

 

Micro Focus 2.2

Hardware

HPUX, Solaris, AIX, Linux

Network

TCP/IP

Operating System

HPUX 10.2+, HPUX64, AIX 4.3+, AIX 4.2, Linux, or Tru 64 (Unix), SUN 5.8 and 5.9 with Micro Focus 4.0 SP1 only

Windows

Memory

N/A

Hard Drive

1 MB

 

Redshift

Hardware

Personal Computer (Intel)/Alpha, Solaris, Linux(Unix)

Network

TCP/IP

Operating System

Linux, SUN 5.8 and 5.9, Windows

Memory

N/A

Hard Drive

N/A

 

DB2 Product

Operating System

Network

DB2/6000; DB2 UDB for AIX

AIX 4.3 and above

TCP/IP and SNA/LU 6.2

DB2/MVS V4R1 and above;

MVS

SNA/LU 6.2 only

DB2 UDB for z/OS and OS/390

z/OS and OS/390

TCP/IP and SNA/LU 6.2

DB2/400 V3R1 and above

OS/400

SNA/LU 6.2 only

DB2/400 V4R2 and above; DB2 UDB for iSeries

OS/400 and iSeries

TCP/IP and SNA/LU 6.2

DB2 UDB Enterprise Server Edition

Windows

TCP/IP and SNA/LU 6.2

DB2 UDB for Linux Enterprise Server Edition

Linux

TCP/IP

 

VSAM Product

Operating System

Supported File Types

Network Software

CICS Version/Release

CONNX for CICS/VSAM

z/OS

VSAM

TCP/IP V3R2 and above

V4R1 or TX 1.x and above

CONNX for VSAM / QSAM / PDS

z/OS

VSAM / QSAM / PDS

TCP/IP V3R2 and above

N/A

CONNX for CICS/VSAM

VSE 2.3 and below

VSAM

TCP/IP (CSI / IBM) or Barnard TCP/IP Stack

V2R3 and below

CONNX for CICS/VSAM

VSE 2.4 and above

VSAM

TCP/IP (CSI / IBM) or Barnard TCP/IP Stack

TS 1.1.1 and above

 

IMS Product

Operating System

Supported File Types

Network Software

CICS Version/Release

CONNX for IMS

z/OS

IMS

TCP/IP V3R2 and above

V4R1 or TX 1.x and above

 

Note: CONNX has been tested or certified with the following TCP/IP software products on OpenVMS: UCX 3.0 and above, Multinet, TCPware, and Pathworks.

Note: OLE DB/ODBC providers use third-party data providers which have their own hardware and network requirements and are installed on the client machine.

Important: The server requirements are dictated by the third-party driver selected for operation.

Important: Place the license files on a server that allows for the same number of simultaneous connections as the license count purchased.

CONNX requires that all computers using the CONNX ODBC driver use the same license path for all licensed databases. Do not choose a local hard drive for a license path unless you are using CONNX on a single computer or if you are using CONNX over a remote TCP/IP connection or Remote Active Service (RAS). If two or more computers have a license path that points to a local hard drive, the connection to CONNX may be rejected.

In previous versions of CONNX, if an N-tier license was being run on a machine that was connected to a remote desktop using an application such as PC Anywhere, Terminal Services, or Remote Desktop, an error appeared stating that the license count had been exceeded. This has been changed so that the license now reverts automatically to a database license.

CONNX periodically checks to make sure all computers using CONNX are configured to the same license path. If CONNX  determines that one or more computers are not configured to the same license path, the connection may be denied.