DCPS install fails

[Willem Grooters]

OpenVMS 8.2, AXP

Tried to install DCPS 2.5 but I get just this:

$ set def dqa0:[dcpsaxp025.kit]
$ prod install dcps

The following product has been selected:
HP AXPVMS DCPS V2.5 Layered Product

Do you want to continue? [YES]

Configuration phase starting ...

You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.

HP AXPVMS DCPS V2.5: HP DECprint Supervisor for OpenVMS

© Copyright 2005 Hewlett-Packard Development Company, L.P.

Examining system environment ...
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\NODES\

%DCPS-F-USERABORT, operation terminated by user request
%PCSI-E-S_OPFAIL, operation failed
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition
$

The installation guide doesn't tell anything on NODES...

Willem

[Karl Rohwedder]

Willem,

is this a cluster? DCPS tries to detect all nodes booting from the current systemdisk and creates a DCL symbol NODES="~node1~node2...~".

It uses SYSMAN for this, perhaps you have problems running SYSMAN, try it interactivly:
$ MCR SYSMAN
SET ENV /CLUSTER
DO SHO LOG SYS$SYSDEVICE

regards Kalle

[Volker Halle]

Willem,

if you want to debug this yourself, try using the /TRACE qualifier to get more information.

Next step is PROD EXTRACT PDF DCPS

Look at *DCPS*.PCSI$DESCRIPTION for the .COM files in the kit. You can extract them with PRODUCT EXTRACT FILE DCPS/SELECT=filename

and have a look at where the symbol NODES is used.

Volker.

[Karl Rohwedder]

re. Volker:

a routine named dcps$pcsi_configure is called with a EXECUTE PRECONFIGURE statement from the description file.

Willem, to check for yourself just copy the kit to reference format using:
$ PROD COPY DCPS/FORM=REFE/DEST=[.XXX]

regards Kalle

[Wim Van den Wyngaert]

Or check accounting to find out if the sysman processes failed.

Wim

[Willem Grooters]

Karl:
It's designed to be a cluster, but at the moment it's just one box.

â â â â â â â â â â â â â â â â â â â â â â â â â ¬â â â â â â â â â â
â SYSTEMS â MEMBERS â
â â â â â â â â â â ¬â â â â â â â â â â â â â â â ¼â â â â â â â â â â ¤
â NODE â SOFTWARE â STATUS â
â â â â â â â â â â ¼â â â â â â â â â â â â â â â ¼â â â â â â â â â â ¤
â DIANA â VMS V8.2 â MEMBER â
â â â â â â â â â â ´â â â â â â â â â â â â â â â ´â â â â â â â â â â


$ mcr sysman
SYSMAN> set env/cluster
%SYSMAN-I-ENV, current command environment:
Clusterwide on local cluster
Username SYSTEM will be used on nonlocal nodes

SYSMAN> do sho log sys$sysdevice
%SYSMAN-I-OUTPUT, command execution on node DIANA
"SYS$SYSDEVICE" = "$116$DKA100:" (LNM$SYSTEM_TABLE)
SYSMAN>

Volker:
Copied all (PCSI and TXT files) off CD to a directory - on the system disk.

Believe it or not: trying to install from there with /TRACE went perfect...(and the only things done were copy and /TRACE option.

Willem

[Karl Rohwedder]

If it is not a cluster, the symbol NODES is directly defined, here is a code snippet:

$ if f$getsyi ("cluster_member")
$ then cluster = "Y"
$ gosub examine_cluster_nodes
$ else cluster = "N"
$ number_of_nodes = 1
$ nodes = "~" + f$edit (f$getsyi ("scsnode"), "trim") + "~"

(beware of line wraps)

regards Kalle

[Paul Anderson_7]

What is the result of

$ WRITE SYS$OUTPUT F$GETSYI ("CLUSTER_MEMBER")

on your system? (I'm guessing it's TRUE.)

In that case, the installation procedure runs SYSMAN to determine the system disk on each node, as previously mentioned. SYS$ERROR goes to the null device for that command, so it would be interesting to issue the SYSMAN commands manually to see what happens.

And you said after you copied the kit from CD to disk the installation worked? Did you just copy the PCSI file or did you do a PRODUCT COPY ?

Paul

Paul Anderson
OpenVMS Engineering
Hewlett-Packard Company

[Willem Grooters]

Insdtalltion directly from the CD gave this error. After having copied the PCSI file - and specifying /TRACE - the installation succeeded. Don't ask why. It just did.