HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: TCPIP parameter changes
Operating System - OpenVMS
1827687
Members
3575
Online
109967
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
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-19-2009 10:07 AM
05-19-2009 10:07 AM
TCPIP parameter changes
hi all friends...
In tcpip,We have planned to do chage the tcp_keepcnt,tcp-keepidle,tcp_interval,tcp_init attributes values for system performance.
we have changed these values by following the command:
sysconfig -r sybsystem atributes=value
and we have checked theses values and it was effected immediately ,butwe have changed these values in volatile database and how to change these values in permanent database..
I think it will be changed through sysconfigdb utility,but how can i cange these...otherwise shall i edit and update the sysconfigtab.dat file....
pls help me support at the earliest....
Thank you
K.Karthik.
In tcpip,We have planned to do chage the tcp_keepcnt,tcp-keepidle,tcp_interval,tcp_init attributes values for system performance.
we have changed these values by following the command:
sysconfig -r sybsystem atributes=value
and we have checked theses values and it was effected immediately ,butwe have changed these values in volatile database and how to change these values in permanent database..
I think it will be changed through sysconfigdb utility,but how can i cange these...otherwise shall i edit and update the sysconfigtab.dat file....
pls help me support at the earliest....
Thank you
K.Karthik.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-19-2009 02:40 PM
05-19-2009 02:40 PM
Re: TCPIP parameter changes
Karthik,
Remember there are 3 levels here. "Volatile" (lasts only for this incarnation), "Permanent" (survives reboots, but not necessarily patches, upgrades or other maintenance), then there's "Forever" - where the change will always be applied and is well documented.
Rather than editing sysconfigdb, I'd recommend you add your sysconfig commands somewhere in your startup procedures. That way the changes are forever, and can be documented, explaining why the change was made.
TCPIP$STARTUP will call SYS$STARTUP:TCPIP$SYSTARTUP.COM, if it exists, at the end of the startup sequence.
Remember there are 3 levels here. "Volatile" (lasts only for this incarnation), "Permanent" (survives reboots, but not necessarily patches, upgrades or other maintenance), then there's "Forever" - where the change will always be applied and is well documented.
Rather than editing sysconfigdb, I'd recommend you add your sysconfig commands somewhere in your startup procedures. That way the changes are forever, and can be documented, explaining why the change was made.
TCPIP$STARTUP will call SYS$STARTUP:TCPIP$SYSTARTUP.COM, if it exists, at the end of the startup sequence.
A crucible of informative mistakes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-22-2009 10:29 PM
05-22-2009 10:29 PM
Re: TCPIP parameter changes
Dear John,
Thanks for your support.
We have planned to do change theses values in permanent databsae via add command in tcpip startup procedure.
Actually these values changes recommended by HP,for last week one type of application users are not able to login in the system.The problem rectified after shutdown(cluster shutdown:3front end servers,one back end server) the systems and rebooted.
we have also used RTR application for communicating process..
Thank you
K.K
Thanks for your support.
We have planned to do change theses values in permanent databsae via add command in tcpip startup procedure.
Actually these values changes recommended by HP,for last week one type of application users are not able to login in the system.The problem rectified after shutdown(cluster shutdown:3front end servers,one back end server) the systems and rebooted.
we have also used RTR application for communicating process..
Thank you
K.K
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