<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Problem with x windows login to a vms server in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063006#M24665</link>
    <description>PCX$SERVER.COM is provided by eXcursion, I'm fairly sure. There are instructions at the top for copying it and installing it on other systems.&lt;BR /&gt;&lt;BR /&gt;Whether there is an explicit (or implied) licence for you do do that, I couldn't say. &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 15 Aug 2007 05:10:40 GMT</pubDate>
    <dc:creator>Richard Brodie_1</dc:creator>
    <dc:date>2007-08-15T05:10:40Z</dc:date>
    <item>
      <title>Problem with x windows login to a vms server</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063005#M24664</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;Some people use X windows (Exceed, Reflections, and my old favourite, Xcursion).&lt;BR /&gt;&lt;BR /&gt;They connect within the same vlan to a server, There is no NAT or firewall between the users and the server.&lt;BR /&gt;&lt;BR /&gt;The command used to connect is:&lt;BR /&gt;@sys$manager:decw$startsm&lt;BR /&gt;&lt;BR /&gt;Here is a log from eXcursion:&lt;BR /&gt;14/08/2007  10:40:18 AM  X Server        Information  eXcursion V7.2.177 (Intel) logging enabled.&lt;BR /&gt;14/08/2007  10:40:18 AM  Network         Information  WSAStartup(1): "WinSock 2.0", "Running"&lt;BR /&gt;14/08/2007  10:40:18 AM  Network         Information  WSAStartup(1): "WinSock 2.0", "Running"&lt;BR /&gt;15/08/2007  6:46:31 PM  X Application Startup   Information  rexec: connection succeeded&lt;BR /&gt;15/08/2007  6:46:31 PM  X Application Startup   Information  DCL-E-OPENIN, error opening SYS$SYSROOT:[SYSEXE]PCX$SERVER.COM; as input  -RMS-E-FNF, file not found&lt;BR /&gt;1&lt;BR /&gt;&lt;BR /&gt;The procedure fails and no Xwindows starts, because it is looking for pcx$server, yet pathworks is NOT installed, to my knowledge, on the server.&lt;BR /&gt;&lt;BR /&gt;If they run this exact same command on another server in the same vlan, they can connect without a problem. I think this rules out any network issues?&lt;BR /&gt;&lt;BR /&gt;Any help would be greatly appreciated.&lt;BR /&gt;Thanks,&lt;BR /&gt;Mark</description>
      <pubDate>Wed, 15 Aug 2007 04:44:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063005#M24664</guid>
      <dc:creator>MarkOfAus</dc:creator>
      <dc:date>2007-08-15T04:44:54Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with x windows login to a vms server</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063006#M24665</link>
      <description>PCX$SERVER.COM is provided by eXcursion, I'm fairly sure. There are instructions at the top for copying it and installing it on other systems.&lt;BR /&gt;&lt;BR /&gt;Whether there is an explicit (or implied) licence for you do do that, I couldn't say. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 15 Aug 2007 05:10:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063006#M24665</guid>
      <dc:creator>Richard Brodie_1</dc:creator>
      <dc:date>2007-08-15T05:10:40Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with x windows login to a vms server</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063007#M24666</link>
      <description>Richard,&lt;BR /&gt;&lt;BR /&gt;" PCX$SERVER.COM is provided by eXcursion, I'm fairly sure. There are instructions at the top for copying it and installing it on other systems."&lt;BR /&gt;&lt;BR /&gt;Ok, I don't have access to the other one, so I will get them to copy it to the server in question. Thanks!&lt;BR /&gt;"&lt;BR /&gt;Whether there is an explicit (or implied) licence for you do do that, I couldn't say.&lt;BR /&gt;"&lt;BR /&gt;Hmm, me neither. &lt;BR /&gt;&lt;BR /&gt;I guess my next question is how did the pcx$server.com file arrive on the other server? The other server, according to my product list, has no pathworks installed on it.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Mark.</description>
      <pubDate>Wed, 15 Aug 2007 06:12:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063007#M24666</guid>
      <dc:creator>MarkOfAus</dc:creator>
      <dc:date>2007-08-15T06:12:05Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with x windows login to a vms server</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063008#M24667</link>
      <description>Mark,&lt;BR /&gt;    I had a similar problem with ReflectionsX.    Cut and paste the attached file into a text file (STARTAPP.COM), in your VMS system, and place it in SYS$COMMON:[SYSMGR].    This was supplied by ReflectionsX, and works for me.&lt;BR /&gt;&lt;BR /&gt;Make this the "command file for X-Windows to execute"&lt;BR /&gt;&lt;BR /&gt;Dave</description>
      <pubDate>Thu, 16 Aug 2007 14:28:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063008#M24667</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2007-08-16T14:28:36Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with x windows login to a vms server</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063009#M24668</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Some extra information from the eXcursion (Pathworks 32)installation guide.&lt;BR /&gt;&lt;BR /&gt;Handling Expired OpenVMS Passwords&lt;BR /&gt;&lt;BR /&gt;eXcursion displays a DECterm that lets users supply a new password if their&lt;BR /&gt;old password has expired, thus allowing them to start X applications from&lt;BR /&gt;OpenVMS accounts This facility is not enabled by default, and a short&lt;BR /&gt;procedure is required to enable it.&lt;BR /&gt;&lt;BR /&gt;To enable checking for expired passwords:&lt;BR /&gt;&lt;BR /&gt;1. On the OpenVMS system, copy the file PCXPWD.EXE to&lt;BR /&gt;SYS$COMMON:[SYSEXE]PCX$CHKPWDEXP.EXE.&lt;BR /&gt;The file PCXPWD.EXE is located in the \HOST\VMS_A(for&lt;BR /&gt;Alpha) or \HOST\VMS_V(for VAX) subdirectory of your&lt;BR /&gt;eXcursion directory.&lt;BR /&gt;&lt;BR /&gt;2. Set the file protection to allow world RE access.&lt;BR /&gt;&lt;BR /&gt;3. Install the new version of PCX_SERV.COM (located in the&lt;BR /&gt;\HOST\VMS_A or \HOST\VMS_V subdirectory of the eXcursion kit&lt;BR /&gt;tree).&lt;BR /&gt;&lt;BR /&gt;4. Rename the PCX_SERV.COM file to PCX$SERVER.COM.&lt;BR /&gt;&lt;BR /&gt;During a remote start, PCX$SERVER.COM searches for the executable&lt;BR /&gt;file (PCX$CHKPWDEXP.EXE) required to check for expired&lt;BR /&gt;passwords. If found, the executable file runs.&lt;BR /&gt;&lt;BR /&gt;If the user's OpenVMS password is expired, an error message is&lt;BR /&gt;displayed, and a DECterm is started to allow the user to log in and&lt;BR /&gt;change his or her password.&lt;BR /&gt;&lt;BR /&gt;If the password is not expired, and you have selected the appropriate&lt;BR /&gt;logging settings in the Control Panel, the following message appears in&lt;BR /&gt;your SYS$LOGIN:NETSERVER.LOG file:&lt;BR /&gt;&lt;BR /&gt;PCX$SERVER_MSG: check for expired password enabled.&lt;BR /&gt;&lt;BR /&gt;This message indicates that the facility for checking passwords is&lt;BR /&gt;functioning correctly.&lt;BR /&gt;_____________________ Note______________________&lt;BR /&gt;You will receive no error message in the log file if&lt;BR /&gt;PCX$SERVER.COM searches for the executable file&lt;BR /&gt;PCX$CHKPWDEXP.EXE and cannot locate it.&lt;BR /&gt;________________________________________________&lt;BR /&gt;&lt;BR /&gt;/Regards&lt;BR /&gt;Leif J</description>
      <pubDate>Fri, 17 Aug 2007 01:26:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063009#M24668</guid>
      <dc:creator>Leif R. Jansson</dc:creator>
      <dc:date>2007-08-17T01:26:51Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with x windows login to a vms server</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063010#M24669</link>
      <description>Thanks to all for their superb answers. The problem has been solved, thanks.</description>
      <pubDate>Fri, 17 Aug 2007 19:38:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/problem-with-x-windows-login-to-a-vms-server/m-p/5063010#M24669</guid>
      <dc:creator>MarkOfAus</dc:creator>
      <dc:date>2007-08-17T19:38:33Z</dc:date>
    </item>
  </channel>
</rss>

