Prerequisites - CONNX for CICS/VSAM - OS/390 / z/OS

  • The IBM OS/390 mainframe must be set up for TCP/IP communications.

  • The TCP/IP started task must be running.

  • The IBM CICS TCP/IP sockets interface, including CICS configuration files, programs, maps, and transactions, must be installed.

  • Both the install PC client and the target host (OS/390 / z/OS) should have FTP enabled (optional).

Refer to the following links for more information on installing the IBM CICS TCP/IP interface:

 

OS/390 V2R8.0 SecureWay CS IP CICS Sockets Guide©

Document Number: SC31-8518-01

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1AI4010/CCONTENTS

 

2.0 Chapter 2. Setting Up and Configuring CICS TCP/IP©

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1AI4010/2.0?DT=19990706130612

 

Verifying TCP/IP Connectivity

 

Before you install CONNX on your CICS/VSAM server, we recommend that you verify the TCP/IP connectivity to your OS/390 z/OS system. To verify connectivity:

  1. Open a Command Prompt window.

  2. On the task bar, click Start and then click Run

  3. 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