- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: sysgen parameter CHANNELCNT not getting change...
Operating System - OpenVMS
1753918
Members
7666
Online
108810
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
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
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
тАО10-31-2006 04:53 AM
тАО10-31-2006 04:53 AM
Re: sysgen parameter CHANNELCNT not getting changed
Srikanth,
not claiming that our way is the best there is, but here it is anyway:
Each week we run AUTOGEN SAVPARAMS GETDATA at peak time (for most load) on each cluster node (from a scheduled batch job)
Next evening, when the systems tend to be quieter, we run AUTOGEN GENPARAMS SETPARAMS FEEDBACK, generating AGEN$REPORTs in the process.
Next morning we review those reports, and if a trend approaches criticallity we schedule a reboot.
If you are aware of trends, you can prognose values (especially for non-dynamic params) and enter MIN_ or MAX_ values in MODPARAMS, such that reboot needs become rarer and rarer.
Do not expect, nor aim, to get there in one pass!
hth
Proost.
Have one on me.
jpe
not claiming that our way is the best there is, but here it is anyway:
Each week we run AUTOGEN SAVPARAMS GETDATA at peak time (for most load) on each cluster node (from a scheduled batch job)
Next evening, when the systems tend to be quieter, we run AUTOGEN GENPARAMS SETPARAMS FEEDBACK, generating AGEN$REPORTs in the process.
Next morning we review those reports, and if a trend approaches criticallity we schedule a reboot.
If you are aware of trends, you can prognose values (especially for non-dynamic params) and enter MIN_ or MAX_ values in MODPARAMS, such that reboot needs become rarer and rarer.
Do not expect, nor aim, to get there in one pass!
hth
Proost.
Have one on me.
jpe
Don't rust yours pelled jacker to fine doll missed aches.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-31-2006 09:03 AM
тАО10-31-2006 09:03 AM
Re: sysgen parameter CHANNELCNT not getting changed
Hi JPE
Many thanks as usual JPE for your response and this forum has been really good and quick in responding to queries.
Many thanks to everyone and will close the thread with this note.
Regards,
Srikanth
Many thanks as usual JPE for your response and this forum has been really good and quick in responding to queries.
Many thanks to everyone and will close the thread with this note.
Regards,
Srikanth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-15-2006 08:01 AM
тАО11-15-2006 08:01 AM
Re: sysgen parameter CHANNELCNT not getting changed
Srikanth,
(late response)...
Please be VERY CAREFUL using SYSGEN!
>> SYSGEN> USE ACTIVE
>> SYSGEN> SET CHANNELCNT 2048
>> SYSGEN> WRITE CURRENT
This sequence is very dangerous. You've taken your ACTIVE set and written it back to CURRENT. In many cases that may be benign, but there are a few situations where it could result in an unbootable system. At the very least, you don't know if you're committing some dynamic changes to other parameters since the last reboot to the permanent set.
Please make sure you know EXACTLY which set of parameters you're working with. Personally, I ALWAYS type an explicit USE command in SYSGEN to be certain. Most of the time it would be:
SYSGEN> USE ACTIVE
SYSGEN> ... change some dynamic parameters
SYSGEN> WRITE ACTIVE
OR
SYSGEN> USE CURRENT
SYSGEN> ... change some permanent parameters
SYSGEN> WRITE CURRENT
For permanent parameters, you're MUCH better off making your changes in MODPARAMS and using AUTOGEN to implement them. Changes should document what was done, when, why and by whom. You're also better off using a MIN, MAX or ADD, so that AUTOGEN can take other factors into consideration. Your CHANNELCNT change should look like this in MODPARAMS.DAT:
MIN_CHANNELCNT = 2048 ! Srikanth 27-Oct-2006, required by
(late response)...
Please be VERY CAREFUL using SYSGEN!
>> SYSGEN> USE ACTIVE
>> SYSGEN> SET CHANNELCNT 2048
>> SYSGEN> WRITE CURRENT
This sequence is very dangerous. You've taken your ACTIVE set and written it back to CURRENT. In many cases that may be benign, but there are a few situations where it could result in an unbootable system. At the very least, you don't know if you're committing some dynamic changes to other parameters since the last reboot to the permanent set.
Please make sure you know EXACTLY which set of parameters you're working with. Personally, I ALWAYS type an explicit USE command in SYSGEN to be certain. Most of the time it would be:
SYSGEN> USE ACTIVE
SYSGEN> ... change some dynamic parameters
SYSGEN> WRITE ACTIVE
OR
SYSGEN> USE CURRENT
SYSGEN> ... change some permanent parameters
SYSGEN> WRITE CURRENT
For permanent parameters, you're MUCH better off making your changes in MODPARAMS and using AUTOGEN to implement them. Changes should document what was done, when, why and by whom. You're also better off using a MIN, MAX or ADD, so that AUTOGEN can take other factors into consideration. Your CHANNELCNT change should look like this in MODPARAMS.DAT:
MIN_CHANNELCNT = 2048 ! Srikanth 27-Oct-2006, required by
A crucible of informative mistakes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-15-2006 09:50 AM
тАО11-15-2006 09:50 AM
Re: sysgen parameter CHANNELCNT not getting changed
Hi John,
Thanks for your precise answer. I will follow this when I am changing it for the next time.
Thanks,
Srikanth A
Thanks for your precise answer. I will follow this when I am changing it for the next time.
Thanks,
Srikanth A
- « 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