- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: OpenVMS installation
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
тАО01-30-2006 09:40 PM
тАО01-30-2006 09:40 PM
Re: OpenVMS installation
the old license data base file from the old
system disk to the new system disk. This
tends to work better if you don't change the
SCSSYSTEMID and SCSNODE parameters, as some
of the PAKs may have the NO_SHARE option, and
thus are sensitive to the node name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-30-2006 09:44 PM
тАО01-30-2006 09:44 PM
Re: OpenVMS installation
A good idea, but is it possible to copy all files (related to license) from the old system disk to the new system.
$ backup mka500:files dka0:
Regards geir
PS:
Do you have the filenames?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-30-2006 09:55 PM
тАО01-30-2006 09:55 PM
Re: OpenVMS installation
but that one file in SYS$SYSTEM is often the
only one.
DIRE DKA0:[000000...].LDB
The UAF and its friends are also good files
to consider for save and restore. The VMS
FAQ has a list. Look for SYSUAF for more
ideas.
http://h71000.www7.hp.com/faq/openvms_faq.html
http://h71000.www7.hp.com/faq/vmsfaq_stmlf.txt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2006 07:01 PM
тАО01-31-2006 07:01 PM
Re: OpenVMS installation
The workstation boot automatically from dka0. I want to break the boot sequence. I have tried break key, Ctrl-C/Y etc.
How is it possible to break the boot sequence??
One more question: If I want to install Fortran-90,C,C++ which is a part of CD #2 (Layered products). Is it neccssary to mount CD#2, and then use vmsinstall. I tried it but, each time I got an error message that says unknown products. Any comments?
Thanks geir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2006 07:22 PM
тАО01-31-2006 07:22 PM
Re: OpenVMS installation
To set the default, set the console variable AUTO_ACTION to HALT.
To install LP with VMSINSTAL you have to specify the product name, which is derived from the kits filename minus the filetype, e.g.
the C-Compiler kits are CC071.A anc CC071.B, the kit name is CC071, so a
$@SYS$UPDATEVMSINSTAL CC071 [location]
should work (you may omit the 071 to install any version found on [location])
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2006 07:42 PM
тАО01-31-2006 07:42 PM
Re: OpenVMS installation
Thanks. Is break key the same as F5. I have tried i seveal times, without success (after power off/on, and reset button).
Should I press other key at the same time, or ...?
Geir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2006 07:57 PM
тАО01-31-2006 07:57 PM
Re: OpenVMS installation
In depending of hardware implementation it is possible to find a hardware button to display console prompt (in VAX 3000 family implementations, it is a little button near thinwire).
Are you check CTRL/P if you have Alpha family hardware?
Saludos.
Daniel.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2006 08:32 PM
тАО01-31-2006 08:32 PM
Re: OpenVMS installation
Recent systems allow for CONTROL/P if
the console variable CONTROL_P is set to ON.
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2006 12:22 AM
тАО02-01-2006 12:22 AM
Re: OpenVMS installation
Thanks for the answer. This time I got problem if I want to enable and register new license.
I can't logg in to the system, because of trouble with the license. So I thougt that I should boot from a CD.
But this time I got following error:
$mc lmf
%cli-F-syntax,error parsing 'register'
-cli-e-entnf,specifies entity not found in command table.
I'm sure that I registered license for Fortran, C, C++ and DECnet. I have also installed MOTIF (but the license is not installed yet). Now I want to register and activate the license.
I have tried both lmf and a com-file to register the license.
Maybe I must start all over again?? I hope is not necessary
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-01-2006 12:29 AM
тАО02-01-2006 12:29 AM
Re: OpenVMS installation
>>>
$mc lmf
%cli-F-syntax,error parsing 'register'
-cli-e-entnf,specifies entity not found in command table.
<<<
"mc lmf" is not the way to call the License Management Facility, $ LICENSE REGISTER is, or @SYS$UPDATE:VMSLICENSE.COM
cu,
Martin