Prerequisites for IMS - DLI

  • Verify APF Authorization if required.

  • If your system has a security manager like RACF installed, and you wish for all sessions to be authorized, set CNXNOPREAUTHORIZE to 0.

  • If CNXNOPREAUTHORIZE is set to 0, the following is required:

  • Verify that IMS.RESLIBL and the optional IMSUTIL.SHPSLMD0 (zero) are APF authorized.

  • The CONNX load library will need to be APF authorized

  • The TCP/IP started task must be running.

  • The IBM IMS TCP/IP sockets interface, including IMS 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).

  • CONNX fully supports the IMS add-on product IMS Library Integrity Utilities for z/OS to make the importing of metadata easier.  If you wish to use this feature, verify that the utilities are installed on your system.  Note: this feature is optional.

  • Verify that each PCB within the PSB is either labeled or is identified with a PCB name. The PCB is accessed by name and not by relative PCB number within the PSB. The PSB can be named in two ways:

  1. Add a label to each PCB macro line (columns 1-8). We recommend you use this method.

  2. Add a PCBNAME= parameter to the PCB macro.

  • Regenerate each of the modified PSBs so the PSBLIB reflects the identifier for each PCB.

  • The DLI interface does not require an IMS Control Region but will run concurrently with an IMS control region if one exists.

  • After installation, you may need to add DD statements for your IMS data sets into the CNXDLI member.

Verifying TCP/IP Connectivity

 

Before you install CONNX on your IMS 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