CONNX for VSAM / QSAM / PDS requires that:
The target system be set up to support TCP/IP communications.
The TCP/IP Started Task must be running.
Read/write FTP access be configured and available on the target system.
Both the installation PC client and the target host (OS/390 z/OS) must have FTP enabled.
CONNX for VSAM / QSAM / PDS can access any VSAM, QSAM, or partitioned data set defined on the target OS/390 / z/OS system, as long as the host user ID has the necessary privileges as defined via IBM RACF (Resource Access CONTROL Facility) or a RACF-compatible product such as eTrust CA-Top Secret Security for z/OS & OS/390®. COBOL copybooks for the target files must reside in partitioned data sets defined for FTP read access.
Before you install CONNX on your VSAM server, we recommend that you verify the TCP/IP connectivity to your OS/390 z/OS system. To verify connectivity:
Open a Command Prompt window.
On the task bar, click Start and then click Run
Type or select:
ping hostname
where hostname is the TCP/IP symbolic address or dotted numeric address.
A successful ping (connectivity) will generate output in the command window similar to the following:
Pinging 123.123.123.012 with 32 bytes of data:
Reply from 123.123.123.012: bytes=32 time=10ms TTL=63
Reply from 123.123.123.012: bytes=32 time<10ms TTL=63
Reply from 123.123.123.012: bytes=32 time<10ms TTL=63
Reply from 123.123.123.012: bytes=32 time<10ms TTL=63
Ping statistics for 123.123.123.012:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 10ms, Average = 2ms