- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Conversational Boot
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
тАО11-16-2006 05:37 AM
тАО11-16-2006 05:37 AM
ctrl P to stop failed boot
>>>SET BOOT_OSFLAGS 0,1
>>>boot
sysboot> set startup_p1 "min"
sysboot> continue
Now I was into the server.I modified my systartup_vms.com and shutdown. To boot back to normal I typed
sysboot> set startup_p1 ""
sysboot> continue
Is there more to it than this? One thing I noticed a few days after going through this procedure is that I was running on only 1 processor instead of two. Would a processor failing to run be caused by the steps I took above (or possibly missing steps?) Any help would be greatly appreciated.
Thank you,
Lisa Collins
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 06:07 AM
тАО11-16-2006 06:07 AM
SolutionThe CPU might have failed or the CPU could have been "disabled" at the console. SYSGEN parameters can also be set to disable starting specific CPUs. Something like SMPCPUS or MULTICPROSSING could "turn off" secondary CPUs.
What does the output from a $show cpu/full show you?
Bill
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 06:08 AM
тАО11-16-2006 06:08 AM
Re: Conversational Boot
You should also inspect the system error log for any "CPU" events.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 09:25 AM
тАО11-16-2006 09:25 AM
Re: Conversational Boot
The above mentioned things could be the issue. One other thing to check - LIC LIST /full. Look to make sure one of your additional CPU usage licenses (would be part of OPENVMS-ALPHA) didn't get disabled somehow. I think most CPUs run with 100 units - but honestly don't know if thats just my systems or all.
Does the DS20 run webes or decevent? If those were running it should show up there. I don't know exact commands to extract the details. I usually use the web interface with webes to pull my reports now but I do know there is a command line method.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 11:06 AM
тАО11-16-2006 11:06 AM
Re: Conversational Boot
Disabling a processor, unlikely.
A failed processor: possible.
If you can go through a power cycle without too much inconvenience, shut the machine down and see if the self tests show a failed processor.
I would also check the running parameters to make sure that you are somehow not running MIN or some other restricted situation. Use SYSGEN or SYSMAN to check the active, running parameters.
- Bob Gezelter, http://www.rlgsc.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-16-2006 07:07 PM
тАО11-16-2006 07:07 PM
Re: Conversational Boot
So, you can also do a /noautostart.
May be your startup is doing something specific with that (for your DS20).
Show cpu shows the setting.
And on 7.3 it's not even in the help text.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2006 04:00 AM
тАО12-04-2006 04:00 AM
Re: Conversational Boot
I rebooted the system and the system did not reboot properly. It went into sysboot. Long story short I got back to the >>> prompt and typed SET BOOT_OSFLAGS 0,0 (since it was still set to SET BOOT_OSFLAGS 0,1) and on reboot, both CPU's were working.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-04-2006 05:14 AM
тАО12-04-2006 05:14 AM