OpenVMS installation

[geir_2]

Hi,

I have an OpenVMS workstation , and I want to create a clean OpenVMS installation. In my situation I have two options to do it:

1) Run vmsinstall and create/install a new system of it. Later I must install more packages like DECnet, UCX, TSM, Fortran, C, C++ etc. After installation I must install license. So far so good. But my problem is to find the software media (CD's). I have sent some e-mail to x colleagues, but sofar I got no answers. Does someof you know where I can get the software media from?? I assume it's lot work to do if I want to install OpenVMS from sratch.


2) The next options is to clean up the running system. Deinstall unnecessary software package.
It looks more simple to do it like this.
Which commands is necessary to list the installed software packages, and later deinstall uselesss software packages.


Nice If somebody could give me hints

Thanks

Geir

[Karl Rohwedder]

To check for installed software on a quite modern VMS version:

- PRODUCT SHOW PRODUCT and PRODUCT SHOW HISTORY

displays all software installed via PRODUCT,
this software can be deinstalled using PRODUCT REMOVE

- TYPE SYS$UPDATE:VMSINSTAL.HISTORY

displays software installed via the VMSINSTAL procedure, the deinstallation of such software is not straightforward, some software provides for a deinstallation procedure, e.g. Oracle/RDB, other software can only be deinstalled manually (some installation guides contain a list of installed files as a starter, but there are also Helpmodules, DCL verbs...)

- and then there is the BACKUP... type of software, which is difficult to track

I attached a little DCL script (2 files), which uses a control file to check for versions of a lot of software and can be adapted to your needs, perhaps it helps a little.

regards Kalle

[geir_2]

Hi,

Thanks for the answer. I'm running OpenVMS 6.2 (old version).

So I must use the old commands.


Geir

[Ian Miller.]

PRODUCT SHOW PRODUCT and PRODUCT SHOW HISTORY do work on VMS V6.2

[geir_2]

Thanks. If I run @sys$update:installed_prds.com, the output show a long list with products installed on the workstation.


Is it possible, to use simular command to deinstall some of these packages?

Geir

[Ian Miller.]

Products installed with PRODUCT INSTALL can be removed using PRODUCT REMOVE.
Unfourtally products installed with VMSINSTAL do not have a standard method of removal.

[Jeff Chisholm]

If you are in the Americas, HP Services has a reasonably priced ValuPack for replacement media, V5.n, V6.n, V7.n, V8.n whatever you've got. Send me an email and I'll reply with details. If you're in another geography I can contact your local HP Services people. /jeff

[geir_2]

Hi,
Thanks. I live in Europe. (Oslo). After all execellent feedback, I think I will install OpenVMS from scratch.

I also want to backup the old system with following commands:
$backup/image/log/veri dka0: mka500:ws99.bck/save

I hope the command is correct.

In the OpenVMS package I found 10 + 2CD with software. I assume the fist disk is bootable

>>> boot cdrom

Next, I must answer a lot of questions. I want to install DECnet, Fortran, C,C++ and POSIX.

At end license pak must be installed with the license command.

I hope everything seems to be OK? If somethings ins't correct let me know.

Thanks.

Geir

[Karl Rohwedder · Accepted solution]

Geir,

the backup commands looks good.

If you have the layered product Cd-set, there is no bootable Cd in it. You need the OpenVMS distribution, it contains a Cd labelled e.g. 'HP OpenVMS Alpha Version 8.2 Operating System'.

You can then boot it and install Vms together with the standard products (DECnet,TCPIP,Motif...).


When VMS is running, you can then installed software such as compilers... from the layered product Cd-set.

regards Kalle

[Barry Alford]

I think you normally install the License PAK before installing a layered product --check the product's Installation Guide first.

This allows the IVP (Installation Verification Procedure) to run after the installation.

[geir_2]

Kalle,

Thanks for the answer. It means:

1) I install OpenVMS with help from a bootable CD (OpenVMS binaries 6.2 ..)

2) When VMS is up and running, then I can use vmsinstall if I want to install layered products (DECnet, TCP/IP ,...)

Geir


PS:
Will the installation ask for DECnet and/or IP-address? Maybe I must include the address with use of ucx and ncp. Thanks.

[geir_2]

Hi,
Thanks. Is license PAK part of the bootable CD?

Geir

PS:
I noticed that POSIX is part of the bootable CD when I installed it, for some months ago.

[Jan van den Ende]

Geir,

on backing up your system:

$backup/image/log/veri dka0: mka500:ws99.bck/save

Assuming dka0: is your system disk, this is NOT the best way.

Even booted minimal. the system disk has several files OPENed for write.
Those are NOT guaranteed to be good in your backup!
If you HAVE (got) a bootable CD (you should anyway before you can continue), then it is best to BOOT from that CD. You will get a little menu, which also has the option DCL.
Choose that, mount dka0: and mka0:, and NOW do your backup. DKA0: is now just a data disk, and your backup will be wholly consistent.

Should you decide you want to backup a LIVE system disk, then MINIMISE any activity on the system (not too hard on a station) and modify your backup command:
$backup/image/log/veri dka0: mka500:ws99.bck/save /IGNORE=INTERLOCK
Without activity on the system, your open files are not being modified, and will end up OK in your backup. (But is IS officially unsupported!)
Without the /IGNORE, any open-for-write files will be ignored, and those include your authorisation files...

Success.

Proost.

Have one on me.

jpe

[Martin Vorlaender]

Geir,

the license should be already installed when you install the software kit, as the installation procedure normally contains an Installation Verification Procedure (IVP) which more often than not runs the product - which requires a license.

So, the normal course of events should be:
- Read the Release Notes/Installation Guide.
- Install the license.
- Install the stoftware.

cu,
Martin

[Jan van den Ende]

Geir,

on backing up your system:

$backup/image/log/veri dka0: mka500:ws99.bck/save

Assuming dka0: is your system disk, this is NOT the best way.

Even booted minimal, the system disk has several files OPENed for write.
Those are now guaranteed NOT to be in your backup!
If you HAVE (got) a bootable CD (you should anyway before you can continue), then it is best to BOOT from that CD. You will get a little menu, which also has the option DCL.
Choose that, mount dka0: and mka0:, and NOW do your backup. DKA0: is now just a data disk, and your backup will be wholly consistent.

Should you decide you want to backup a LIVE system disk, then MINIMISE any activity on the system (not too hard on a station) and modify your backup command:
$backup/image/log/veri dka0: mka500:ws99.bck/save /IGNORE=INTERLOCK
Without activity on the system, your open files are not being modified, and ignoring interlock will do 'the best it can', and they will end up OK in your backup. (But is IS officially unsupported!)
Without the /IGNORE, any open-for-write files will be not backupped, and those include your authorisation files...

Success.

Proost.

Have one on me.

jpe

[Barry Alford]

Hi Geir,

The Licence PAK is normally supplied on paper, giving details like:

Issuer: DEC
Authorization: XXX-IL-1995AUG24-NNNN
Product Name: FORTRAN
Producer: DEC
Units: 100
Version: 0.0
Release Date: (none)
PAK Termination Date: (none)
Availability: 0
Activity: 000000100
Options: RESERVE_UNITS
Hardware ID:


You can use LMF (License Management Facility) to enter these details -- see your documentation (or online:
http://www.hp.com/go/openvms/doc)

[geir_2]

Hi,
I'm backing up a workstation, and it's only one user logged into the system + some programs. As far as I know, the system is not working with open files.

Will it still be a problem if I missed the ingore=interlock?

Geir

PS:
I seems to be better to boot from a CD, and then use the backup command. So If you suggest to do that i will do it. Bit then I must interrupt the backup process.

[Rob Kersey]

Geir,

To back up our system disk we do the following:

1. Shutdown the Alpha and boot from the bootable O/S CD-ROM.

>>> BOOT DQA0 (Assuming DQA0 is the CD/DVD Rom)

2. Choose option 7 from the menu options. 'Execute DCL Commands & Procedures'.

3. Mount the disk to be backed up;

$ MOUNT/OVER=ID $1$DGA10: (Assuming this is your system disk)

4. Initialise the DLT tape.

$ INIT MKA600: SYSDSK

5. Backup the volume in question;

$ BACK/LOG/IMAGE $1$DGA10: MKA600:SYSDSK.BCK /SAV

6. When finished dismount the tape and disk;

$ DISMOUNT MKA600:
$ DISMOUNT $1$DGA10:

7. Issue a logout command to exit from the session. ($LOG)

8. When presented with the menu again select option 8 'Exit', to get back to the three chevron prompt.

9. Boot the alpha backup normally.

HTH.

[Martin Vorlaender]

Geir,

>>>
As far as I know, the system is not working with open files.
<<<

To see which files are open, do a

$ SHOW DEVICE SYS$SYSDEVICE: /FILES

I'm sure you'll get a looong list even on an idle system.

cu,
Martin

[Steven Schweda]

> The Licence PAK is normally supplied on paper, [...]

If you can't find the original paper PAKs,
you can do a "LICENSE ISSUE" to reproduce the
PAK data. See the HELP. If you make a copy
of the license data base file and specify the
copy (/DATABASE=filespec), you can avoid
cluttering the license data base history, and
obviate the "LICENSE ENABLE" command which
you would otherwise need to recover from the
"LICENSE ISSUE" command.

The default data base file is
"SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB".

[Steven Schweda]

Of course, you may be able simply to copy
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.

[geir_2]

Hi,

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?

[Steven Schweda]

You might look for anything named ".LDB",
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

[geir_2]

Hi,

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

[Karl Rohwedder]

The method to prevent from autobooting may depend on the type of hardware you have, e.g. Alphasystems have an HALT key. If you presse it after powerup, the system will not boot.

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