Post-Installation Checklist - OpenVMS Server

The following table provides a checklist of the post-installation operations you must conduct before the OpenVMS installation is complete. After each operation is complete, place a check mark in the appropriate box. Each operation has a reference to a procedure, which you can reference as needed.

 

Post-Installation Checklist – OpenVMS Server

Check here when complete

Item

 

1. Review CONNX OpenVMS Installation Procedure. If you selected Shared Images and the OpenVMS server location, then you must edit the file for your site-specific startup command procedure.

The file name depends on the version of OpenVMS or the VSM you are using: File for OpenVMS (any version).

SYS$MANAGER:SYSTARTUP_VMS.COM

File for VMS versions 5.3 to 5.5: SYS$MANAGER.SYSTARTUP_V5.COM

The following lines are added to start CONNX when the OpenVMS server starts or restarts:

DEFINE /SYSTEM CNXRMSE0 SYS$COMMON:[CONNX]CNXRMSE0.COM

DEFINE /SYSTEM CNXRDBE0 SYS$COMMON:[CONNX]CNXRDBE0.COM

DEFINE /SYSTEM CNXDBME0 SYS$COMMON:[CONNX]CNXDBME0.COM

DEFINE /SYSTEM CNXSVR SYS$COMMON:[CONNX]CNXSVR.COM

DEFINE /SYSTEM CNXDIR SYS$COMMON:[CONNX]

@CNXSVR START

For a procedure on how to incorporate these lines, see Editing the OpenVMS Site-Specific Startup Command.

 

2. Review the minimum quotas for the OpenVMS accounts that will use CONNX. The recommended minimum quotas are as follows:
 

Network Access: No Access Restrictions
Max jobs: 0
Prclm:  8
BIOlm: 512
DIOlm: 512
Enqlm: 2048
Bytlm:  82000
JTQuota: 4096
Wsdef: 1024
Wsquo: 4096
Wsextant: 16348
Pgflquo: 82000

 

For a procedure on how to review these quotas, see Reviewing the Minimum OpenVMS Quotas Procedure.

 

3. Verify that the Data Source Name (DSN) CONNX32 is on the User DSN list of ODBC drivers. Click the Start button, and then point to Settings. In Control Panel, double-click the 32bit ODBC icon. On the User DSN tab, verify that CONNX32 appears as both Name and Driver. If the CONNX32 DSN is not present, it has been erased. This DSN is essential to CONNX operation and must not be erased. To recover the erased CONNX32 DSN, repeat Step 2 – Install CONNX Administrator and CONNX Client.

 

4. Using the test data and a utility program supplied with the CONNX installation, establish a connection with the OpenVMS server for each installed database, for example, RMS, RDB, and DBMS. For a procedure on how to test the connection, see Testing a Database Connection.

 

5. To customize how CONNX is installed, see CONNX REGISTRY FILE SETTINGS in the CONNX User Reference online help file.

 

Related Topic

image\CHICLET.gif License Upgrade Registration - OpenVMS