- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Problem with x windows login to a vms server
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2007 09:44 PM
тАО08-14-2007 09:44 PM
Some people use X windows (Exceed, Reflections, and my old favourite, Xcursion).
They connect within the same vlan to a server, There is no NAT or firewall between the users and the server.
The command used to connect is:
@sys$manager:decw$startsm
Here is a log from eXcursion:
14/08/2007 10:40:18 AM X Server Information eXcursion V7.2.177 (Intel) logging enabled.
14/08/2007 10:40:18 AM Network Information WSAStartup(1): "WinSock 2.0", "Running"
14/08/2007 10:40:18 AM Network Information WSAStartup(1): "WinSock 2.0", "Running"
15/08/2007 6:46:31 PM X Application Startup Information rexec: connection succeeded
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
1
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.
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?
Any help would be greatly appreciated.
Thanks,
Mark
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2007 10:10 PM
тАО08-14-2007 10:10 PM
SolutionWhether there is an explicit (or implied) licence for you do do that, I couldn't say.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-14-2007 11:12 PM
тАО08-14-2007 11:12 PM
Re: Problem with x windows login to a vms server
" 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."
Ok, I don't have access to the other one, so I will get them to copy it to the server in question. Thanks!
"
Whether there is an explicit (or implied) licence for you do do that, I couldn't say.
"
Hmm, me neither.
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.
Thanks,
Mark.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-16-2007 07:28 AM
тАО08-16-2007 07:28 AM
Re: Problem with x windows login to a vms server
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.
Make this the "command file for X-Windows to execute"
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-16-2007 06:26 PM
тАО08-16-2007 06:26 PM
Re: Problem with x windows login to a vms server
Some extra information from the eXcursion (Pathworks 32)installation guide.
Handling Expired OpenVMS Passwords
eXcursion displays a DECterm that lets users supply a new password if their
old password has expired, thus allowing them to start X applications from
OpenVMS accounts This facility is not enabled by default, and a short
procedure is required to enable it.
To enable checking for expired passwords:
1. On the OpenVMS system, copy the file PCXPWD.EXE to
SYS$COMMON:[SYSEXE]PCX$CHKPWDEXP.EXE.
The file PCXPWD.EXE is located in the \HOST\VMS_A(for
Alpha) or \HOST\VMS_V(for VAX) subdirectory of your
eXcursion directory.
2. Set the file protection to allow world RE access.
3. Install the new version of PCX_SERV.COM (located in the
\HOST\VMS_A or \HOST\VMS_V subdirectory of the eXcursion kit
tree).
4. Rename the PCX_SERV.COM file to PCX$SERVER.COM.
During a remote start, PCX$SERVER.COM searches for the executable
file (PCX$CHKPWDEXP.EXE) required to check for expired
passwords. If found, the executable file runs.
If the user's OpenVMS password is expired, an error message is
displayed, and a DECterm is started to allow the user to log in and
change his or her password.
If the password is not expired, and you have selected the appropriate
logging settings in the Control Panel, the following message appears in
your SYS$LOGIN:NETSERVER.LOG file:
PCX$SERVER_MSG: check for expired password enabled.
This message indicates that the facility for checking passwords is
functioning correctly.
_____________________ Note______________________
You will receive no error message in the log file if
PCX$SERVER.COM searches for the executable file
PCX$CHKPWDEXP.EXE and cannot locate it.
________________________________________________
/Regards
Leif J
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-17-2007 12:38 PM
тАО08-17-2007 12:38 PM