- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- defining Netserver$Timeout for single non-privileg...
Operating System - OpenVMS
1755763
Members
2614
Online
108838
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
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
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
05-27-2003 01:45 PM
05-27-2003 01:45 PM
Solution
I don't think the logical name netserver$timeout needs to be defined /SYSTEM to be effective.
For years, I have had the following in my LOGIN.COM for network processes:
$ DEFINE NETSERVER$TIMEOUT "7 00:00:00"
This has the desired effect; my network processes last 7 days.
I have just confirmed this behaviour on VMS 7.3 with DECnet-plus. My memory tells me it has worked the same way for a long time.
The NETSERVER.EXE code in DECnet phase IV just does a simple SYS$TRNLOG of NETSERVER$TIMEOUT with no special processing. It should find a /PROCESS logical name. I don't have easy access to a Phase IV node to confirm this.
For years, I have had the following in my LOGIN.COM for network processes:
$ DEFINE NETSERVER$TIMEOUT "7 00:00:00"
This has the desired effect; my network processes last 7 days.
I have just confirmed this behaviour on VMS 7.3 with DECnet-plus. My memory tells me it has worked the same way for a long time.
The NETSERVER.EXE code in DECnet phase IV just does a simple SYS$TRNLOG of NETSERVER$TIMEOUT with no special processing. It should find a /PROCESS logical name. I don't have easy access to a Phase IV node to confirm this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2003 04:58 AM
05-28-2003 04:58 AM
Re: defining Netserver$Timeout for single non-privileged User
jrd is correct. I work with Zeni the original poster and I just tested it on one of our systems running Phase IV and it worked. We had looked at the Netserver.com file and it appeared to only be looking for an EXEC mode logical in the job and system logical tables for the translation. For our problem, actually, we are going the opposite way that jrd was doing. Instead of a long timeout, we need to set it to 0 for a specific user, forcing them through the login sequence every time they connect. That is what I tested and it worked.
- « Previous
-
- 1
- 2
- Next »
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP