home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pmafire!news.dell.com!swrinde!elroy.jpl.nasa.gov!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms
- Subject: Re: Re: equivalent to SET BOOT
- Message-ID: <1992Sep4.171004.29582@cco.caltech.edu>
- Date: 4 Sep 92 17:10:04 GMT
- References: <1992Sep3.103256.3@seb.se>
- Sender: news@cco.caltech.edu
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- Organization: HST Wide Field/Planetary Camera
- Lines: 30
- Nntp-Posting-Host: sol1.gps.caltech.edu
-
- In article <1992Sep3.103256.3@seb.se>, s01964@seb.se writes:
- >>|
- >>| Does anyone know if it is possible to issue an equivalent to the
- >>|>>>SET BOOT <nickname> [>boot-parameters>], without bringing down the system.
- >>| We are running VMS5.5 on a 4010, 6320, and a 6610. Thanks.
- >
- >>There would have to be a different routine for each type of VAX as each has
- >>a different console. As far as I know no such program exists although perhaps
- >>one or two hack have been brewed up for a particular machine or two.
- >
- >
- >I've done a small program that change the boot device for VAXstation 3100
- >and VAXstation 4000. Please contact me with E-mail if you want to have the
- >source.
-
- I've seen lots of people talking about programs to do this, but why not just:
- 1) Halt the system;
- 2) Issue the SET BOOT commands;
- 3) Issue a CONTINUE command.
- Sure, the system is halted for a few seconds, but you don't bring it down, and
- once you issue the CONTINUE command, things proceed from where they were when
- the system was halted.
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-