Connect-Star installation requirements

Overview

The Connect★ Suite supports three communications interfaces:

• .NET Framework
• JDBC
• ODBC

Each interface has its own database connectivity program that supports both SQL and RCL connections. The Connect★ Visual Interface is provided to populate the SQL catalog file (CCACAT) and for quick query capability to Model 204.

SQL conformance level

The SQL conformance level is ANSI 89 with most ANSI 92 functionality.

Communication protocol

Each interface uses the TCP/IP protocol to connect a PC workstation to Model 204 running on a mainframe.

IPv6 address support for Connect^★

All Connect★ clients support Internet Protocol Version 6 (IPv6) 128-bit addresses as well as IPv4 32-bit addresses.

Connect★ clients have the option of specifying explicit server addresses in either of the following formats:

• IPv4 dotted decimal format; for example:

  74.6.238.254

• IPv6 colon-separated hexadecimal format; for example:

  2001:0DB8:AC10:FE01:0000:0000:0000:0000

  Consecutive zero halfwords can be replaced by a double colon, for example:

  2001:0DB8:AC10:FE01::

If an application specifies the host address as a symbolic name, then the client first attempts an IPv6 connection to the server. If that fails, the client attempts an IPv4 connection. An error is not returned to the application unless both attempts fail.

Requirements

In order to take advantage of IPv6 addresses, you might have to install and enable IPv6 support on your client operating system. See your client operating system documentation for instructions.

System requirements

Model 204 mainframe

• IBM^® operating system: IBM z/OS^®, IBM z/VM^®, or IBM z/VSE^®
• TCP/IP for operating systems z/OS, z/VM, or z/VSE
• IBM TCP/IP V2 or higher
• Model 204 V6R1 or higher, configured for use with Connect★ SQL and/or RCL connections. For more information, see the Rocket Model 204 installation instructions for your operating system and the Rocket Model 204 SQL connectivity documentation.

Connect^★ workstation or server

The Connect★ ODBC interface is 32-bit and provides compatibility with any program or operating system capable of running or supporting 32-bit applications. This includes Windows XP (32-bit or 64-bit), Windows 7 (32-bit or 64-bit), Java Virtual Machine (32-bit or 64-bit), or other similar environments.

The Connect★ JDBC driver operates with either a 64-bit or 32-bit Java Virtual Machine.

The Connect★ .NET interface version 7.5 and higher provides both 32-bit and 64-bit drivers that can be used with any Web or GUI-driven application.

ODBC support

• Microsoft^® TCP/IP
• Microsoft platforms:
  • Windows^® XP^®
  • Windows 2003^®
  • Windows 7^®

JDBC support

• Microsoft TCP/IP
• Model 204 7.4.0 or higher is required if you are using BLOBs and CLOBs

  Otherwise, Model 204 7.4.0 or higher is not required; Connect★ is compatible with previous supported versions of Model 204.

  Model 204 is compatible with previous supported versions of Connect★.

• Java SE Development Kit (JDK) or Java SE Runtime Environment (JRE) Version 1.5 or higher
• Platforms: Any operating system that supports Java Runtime Environment

.NET Framework support

• Microsoft TCP/IP
• .NET Framework 2.0 or higher
• Microsoft platforms:
  • Windows XP
  • Windows 7
  • Windows Server 2003
  • WIndows Server 2008

Preparing to install

Before installing Connect★, perform the following tasks, consulting your documentation or TCP/IP manager as needed.

Connect★ preinstallation tasks

Task	Consult...
Install TCP/IP software on the mainframe and the PC	the Model 204 installation instructions for your site and the appropriate installation guide for your PC
Get an IP address for the z/OS system Model 204 runs in. There is only one IP address for each system.	the TCP/IP manager at your site
Get a SERVPORT number, the local port number that remote clients use to connect to the Model 204 link.	the TCP/IP manager at your site
Define input threads, such as IODEVs 19 and/or 49, and setting CCAIN parameters	Defining the user environment (CCAIN) List of Model 204 parameters
Define links and processgroups for your applications	DEFINE LINK and DEFINE PROCESSGROUP commands for TCP/IP
Make sure you have your username and password for ftp.rocketsoftware.com	Rocket Technical Support
Remove your existing copy of Connect★ ODBC	Uninstalling a previous version of Connect* for ODBC
Remove your existing copy of Connect★ for JDBC	Removing a previous version of Connect* for JDBC
Remove your existing copy of .NET Framework	Uninstalling a previous version of Connect* for .NET Framework

Most of the tasks in the previous table are handled by the Model 204 system administrator or Model 204 database administrator. The person who installs Connect★ might or might not also be the Model 204 system administrator or database administrator.

TCP/IP software requirements

To connect using TCP/IP, define a TCP/IP link in the Model 204 Online using a DEFINE LINK command. For correct coding, see DEFINE LINK command.

Security interfaces for UNIX System Services (formerly OpenEdition)

If you are running with the sockets interface (IBM stack and z/OS 1.4 or above) then you must make security definitions within Open MVS to define Model 204 as a sockets application.

A useful reference manual is the IBM document SC28-1890, UNIX System Services Planning manual (formerly OpenEdition Planning). Among other subjects, this manual deals with security issues, including the setup of user IDs (UIDs) and group IDs (GIDs). This planning manual illustrates the security setup from a Security Server (formerly RACF) point of view.

As the planning manual mentions, you can use an equivalent security package instead of Security Server (RACF). However, you must verify that the version of the security package that you are running can handle UNIX System Services security.

Sample definitions for Security Server (RACF) users:

• For the owning USERID for the ONLINE address space, specify the following to define it to the OMVS segment:

  UID=0000000000 HOME=/ PROGRAM=/bin/sh

  When defining UNIX System Services users to Security Server (RACF), such as assigning a UID to the user, the USERID must have a UID of 0, as shown in this first example.

• For the group that owns the owning USERID, specify a group ID:

  GID=0000000002

  The value of 0000000002 in this example is the ID of the particular Security Server (RACF) group as defined to UNIX System Services.

In Security Server (RACF) terms, you can set up the UID and GID definitions with certain panels under TSO/ISPF that are used to maintain users and groups. There is an equivalent facility for Top Secret or ACF2.