HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Display X windows
Operating System - OpenVMS
1827871
Members
1226
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
06-15-2007 01:52 AM
06-15-2007 01:52 AM
Hello all,
We have OpenVMS 7.3-2 (not the NEW Desktop Environment). Now if we generally login to the session we are able to run applications (X windows based...applications).
We currently have the main server housing the system disk and 3 other stations. There are also few accounts. Users often require to login to account 1 and then when they are in the account
often do a (in the terminal window)
$set host 0
username: ACcount2
pwd:XXXXXX
However, when the user now tries to access any of the applications that would basically open up in a new window (example running text editor applications etc. ) we get an error.
I believe the reason for this is because we need to setup the terminal
using
$display
command with some qualifiers but it is not clear what should they be.
Any help in this matter would be great.
Thanks in advance.
We have OpenVMS 7.3-2 (not the NEW Desktop Environment). Now if we generally login to the session we are able to run applications (X windows based...applications).
We currently have the main server housing the system disk and 3 other stations. There are also few accounts. Users often require to login to account 1 and then when they are in the account
often do a (in the terminal window)
$set host 0
username: ACcount2
pwd:XXXXXX
However, when the user now tries to access any of the applications that would basically open up in a new window (example running text editor applications etc. ) we get an error.
I believe the reason for this is because we need to setup the terminal
using
$display
command with some qualifiers but it is not clear what should they be.
Any help in this matter would be great.
Thanks in advance.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2007 02:07 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2007 02:32 AM
06-15-2007 02:32 AM
Re: Display X windows
Nipun,
In the workstation X-Session may require to set â Session Manager->Option->Securityâ then put "*" in Node, "*" in Username and TCPIP or DECNET what ever you are using.
In the server issue $SHOW DISPLAY, if the node name differs from the one the user has logged in from then set the display with e.g
SET DISP/NODE=nodename /TRANS=TCPIP
Now try your command.
Regards,
Shankar
********************************************
In the workstation X-Session may require to set â Session Manager->Option->Securityâ then put "*" in Node, "*" in Username and TCPIP or DECNET what ever you are using.
In the server issue $SHOW DISPLAY, if the node name differs from the one the user has logged in from then set the display with e.g
SET DISP/NODE=nodename /TRANS=TCPIP
Now try your command.
Regards,
Shankar
********************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-15-2007 03:03 AM
06-15-2007 03:03 AM
Re: Display X windows
>>> $set host 0
username: ACcount2
pwd:XXXXXX<<<
This DECnet remote login construction is typically an indication of some form of accounting or auditing, or of some form of a site-specific access control issue.
If used for process accounting or auditing, there are (or were) tools around which implement charge-code accounting. Freeware tools such as HGLOGIN and GLOGIN can be solutions here, and commercial packages are (or were) available.
If this was used for access controls, there are mechanisms using access control lists and identifiers which can entirely eliminate the need for the DECnet network session. And that can maintain standard OpenVMS auditing and accountability.
Using ACLs and identifiers will allow the users to log in once, and it will not derail your X Windows DECW$DISPLAY setting, nor will it mask the symbols, logical names or other parts of the original login process context.
Stephen Hoffman
HoffmanLabs LLC
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP