Attachmate Worldwide  |   Contact Us  |   NetIQ.com
Home » Support » Solution Library

Technical Notes

Unable to Connect to VMS Hosts After Upgrading to Reflection X
Technical Note 1611
Last Reviewed 30-Jun-2005
Applies To
Reflection Suite for X version 12.0 through 14.x
Reflection X version 12.0 through 14.x
Summary

After upgrading from version 8.x of Reflection X to a newer version of Reflection X, users are no longer able to connect to VMS hosts. This technical note explains the problem and provides steps for resolving the issue.

Changes to the Command Line

Starting in Reflection X version 8.0.6, the default command line for VMS host connection templates was changed. If you are using connection templates that use the Startapp or Startsm commands and are unable to connect to a VMS host after upgrading to Reflection X version 9.0 or higher, this may be the cause of the problem.

In most cases, you can simply modify the connection template to restore functionality. However, if users are running in any of the following environments, further steps are required.

  • Windows Terminal Server, Citrix, or WinFrame.
  • Windows XP with the Fast User Switching feature enabled.
  • Any version of Windows, if users are utilizing multiple X server instances (sometimes referred to as multiple X displays), of Reflection X, to connect to multiple hosts.

If users are running in any of the environments listed above, see Technical Note 1624 for further directions.

If users are not running in any of the environments listed above, follow the steps below to modify the VMS host connection templates.

Modifying the Host Connection Templates

You must modify each Reflection X default RXC file that uses one of the following commands: startsm, startapp.

The following is a list of Reflection X default templates that use startsm or startapp:

Sm_tcp.rxc
Sm_dnet.rxc
Vmsdnet.rxc
Vms.rxc

Note: Shortcuts and custom RXC files do not need to be updated, as the Reflection X upgrade will modify only the default RXC files.

To fix this problem, follow the steps below.

  1. Open the Reflection X Manager (formerly called the Reflection X Client Manager).
  2. Click File > Open Client File, and navigate to "Documents and Settings\All Users\Templates\WRQ\Reflection\X\Enu."
  3. Select vms.rxc and click Open.
  4. In the Command field, delete the # symbol (the one that appears between the two percent symbols) from the command line.

For example, in the vms.rxc template, the command @startapp %IP#% term should be edited to read: @startapp %IP% term.

  1. Click File, and then click Save.
  2. Repeat steps 1 through 5 for each of the default VMS RXC files. These files are located in the \VMS subfolder and are named sm_tcp.rxc, sm_dnet.rxc, vmsdnet.rxc, and vms.rxc.
Related Technical Notes
1227 Starting X Clients or the Session Manager on a VMS Host
1624 Connecting to a VMS Host over TCP/IP or DECnet without PCX$SERVER
1751 Getting Started with Multiple X Server Instances
9992 Reflection X Technical Notes

Did this technical note answer your question?

Yes    No    Somewhat     Not sure yet

Additional comments about this tech note:

Need further help? For technical support, please contact Support.