CONNX Data Integration Suite 14.8.0 | Installation Guide | Installation Steps | Post-Installation Procedures | Troubleshooting Post-Installation Procedures | Troubleshooting with RMS, Oracle Rdb, and Codasyl DBMS Databases
 
Troubleshooting with RMS, Oracle Rdb, and Codasyl DBMS Databases
*The network connection to the OpenVMS system is not working or your OpenVMS login information is incorrect.
Make sure you can access the OpenVMS system from your computer using the server name, user name, and password you are using with CONNX. If you are using TCP/IP to make the connection to your OpenVMS system, use a TCP/IP utility such as Telnet or FTP to verify that you can connect to the system.
Use the same server name or address, OpenVMS user name, and password that you are using with CONNX. If you cannot make a connection from your computer with any of the utilities, contact your network administrator for help in resolving network problems.
*The OpenVMS login information stored for your CONNX integrated login account in the CONNX CDD is incorrect.
Use the Database Account Management option under Security on the File menu to verify that the stored OpenVMS login information for the CONNX integrated login account is correct. Modify the information for your account and save your changes by selecting Save on the File menu.
*The CONNX TCP/IP Spawner process is not running on your OpenVMS system.
The CONNX TCP/IP Spawner process listens for incoming connection requests from computers running the CONNX client software. The process creates CONNX server processes in response to connection requests from the CONNX client software.
The name for the server process is CNXRUN90_MAIN or CNXRUN90_MAIN. The following DCL commands will determine whether the process is running on a selected OpenVMS system:
$ SHOW SYSTEM /OUTPUT = TEMP.TXT
$ SEARCH TEMP.TXT CNXRUN
If the second command generates the message “%SEARCH-I-NOMATCHES, no strings matched,” then the CONNX TCP/IP Spawner process is not running on the system. Start the CONNX TCP/IP Spawner process with the following DCL command:
$ @CNXSVR START
This command requires that the CONNX logical name CNXSVR be defined as equivalent to the OpenVMS file specification for the CNXSVR.COM file (normally, SYS$COMMON:{CONNX}CNXSVR.COM).