- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- VMS & HSG80 powerup/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
тАО05-08-2006 05:42 AM
тАО05-08-2006 05:42 AM
Is there a way to make the ES40 pause during startup to allow the HSG80s time to complete their startup?
Thanks in advance!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2006 06:31 AM
тАО05-08-2006 06:31 AM
Solutionthere is no easy solution to your problem.
It may be possible to modify the power-up script to include e.g. some TEST commands to delay execution of the script enough, so that the HSG80s finish their power-up initialization first.
See chapter 2.23 in the ES40 User Interface Guide:
http://h18002.www1.hp.com/alphaserver/download/es40fg_revb.pdf
Be careful when modifying the power-up script.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2006 08:57 AM
тАО05-08-2006 08:57 AM
Re: VMS & HSG80 powerup/boot
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2006 09:52 AM
тАО05-08-2006 09:52 AM
Re: VMS & HSG80 powerup/boot
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2006 10:47 AM
тАО05-08-2006 10:47 AM
Re: VMS & HSG80 powerup/boot
I don't think that I'll want to mess with STARTUP.COM!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2006 11:16 AM
тАО05-08-2006 11:16 AM
Re: VMS & HSG80 powerup/boot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2006 01:50 PM
тАО05-08-2006 01:50 PM
Re: VMS & HSG80 powerup/boot
I've attached a simple procedure which attempts to mount a disk. It will wait a maximum of 30 seconds for the device to appear. Obviously this can be modified to suit. Should be self explanatory.
My preference is to abstract the "storage objects" from the physical devices. You need a kind of data base which can associate "nick names" for storage objects to devices and logical names. During startup, you then ask a procedure to make sure the storage is available, perhaps with an importance flag (ie: "REQUIRED - means wait forever until it's available, or "OPTIONAL" - means wait some timeout period, then give up and return a failure status). The procedure will check if the device exists and is mounted. If not, it will do whatever is needed.
Implemented correctly, this allows you to specify multiple logical objects that may map to the same physcial device, and you're free to move them around as required. You don't need to code an explicit sequence of mounts during the startup, it will be derived automatically. Your startup looks something like this:
$ @GETDISK APPLICATION_1 DISK$APP1 REQUIRED
$ @APP1_STARTUP
$ @GETDISK APPLICATION_2 DISK$APP2 REQUIRED
$ @APP2_STARTUP
$ @GETDISK APPLICATION_3 DISK$APP3 OPTIONAL
$ IF $STATUS.EQS.DISK_OK THEN @APP3_STARTUP
(or you can write the GETDISK call at the start of the APP_STARTUP.COM proceddure)
All the gory details of mounts, shadow sets, policies and other stuff are hidden in GETDISK.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2006 01:51 PM
тАО05-08-2006 01:51 PM
Re: VMS & HSG80 powerup/boot
I've attached a simple procedure which attempts to mount a disk. It will wait a maximum of 30 seconds for the device to appear. Obviously this can be modified to suit. Should be self explanatory.
My preference is to abstract the "storage objects" from the physical devices. You need a kind of data base which can associate "nick names" for storage objects to devices and logical names. During startup, you then ask a procedure to make sure the storage is available, perhaps with an importance flag (ie: "REQUIRED - means wait forever until it's available, or "OPTIONAL" - means wait some timeout period, then give up and return a failure status). The procedure will check if the device exists and is mounted. If not, it will do whatever is needed.
Implemented correctly, this allows you to specify multiple logical objects that may map to the same physcial device, and you're free to move them around as required. You don't need to code an explicit sequence of mounts during the startup, it will be derived automatically. Your startup looks something like this:
$ @GETDISK APPLICATION_1 DISK$APP1 REQUIRED
$ @APP1_STARTUP
$ @GETDISK APPLICATION_2 DISK$APP2 REQUIRED
$ @APP2_STARTUP
$ @GETDISK APPLICATION_3 DISK$APP3 OPTIONAL
$ IF $STATUS.EQS.DISK_OK THEN @APP3_STARTUP
(or you can write the GETDISK call at the start of the APP_STARTUP.COM proceddure)
All the gory details of mounts, shadow sets, policies and other stuff are hidden in GETDISK.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2006 01:56 PM
тАО05-08-2006 01:56 PM
Re: VMS & HSG80 powerup/boot
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2006 05:51 PM
тАО05-08-2006 05:51 PM
Re: VMS & HSG80 powerup/boot
we are talking about HSG80 (e.g. DGA) disks here, which will NOT be configured by CONFIGURE, but need to be configured by explicitly running SYSMAN IO AUTOCONFIGURE.
The 'logical' place to wait for the disks to appear (in a loop starting with $ MCR SYSMAN IO AUTO), would be either in SYLOGICALS.COM or SYCONFIG.COM.
SYSTARTUP_VMS.COM would be too 'late', if you have common files on the HSG disks (e.g. queue manager db).
Also take into considertion, that you might want to skip the autoconfiguration, if booting with STARTUP_P1 = "MIN".
Volker.