Installing DECRAM on OpenVMS 7.3-2

[B J DeNoyer]

I am trying to install DECRAM 3.2-3HP on an Alpha ES40 running OpenVMS 7.3-2. I have a valid DECRAM license loaded, and I have pre-allocated the SYSMAN parameter S2_SIZE. I have previously installed DECRAM from the same PCSI file without problems on multiple OpenVMS 7.3-1 systems. On the 7.3-2 system, I get the following sequence of messages from PRODUCT INSTALL ---
...
This product requires the license PAK DECRAM
%PCSI-I-PRCOUTPUT, output from subprocess follows ...
%DCL-E-OPENOUT, error opening SYS$SYSROOT:[SYSMGR.]DECRAM-LIC-CHECK.TXT; as output
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%PCSI-I-PRCERREXE, error executing: @PCSI$SOURCE:[SYSUPD]DECRAM_LIC_CHECK.COM
%PCSI-E-EXEPRCFAIL, product supplied EXECUTE PRECONFIGURE procedure failed
-RMS-E-DNF, directory not found
%PCSI-E-S_OPFAIL, operation failed
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition
$

[Steven Schweda]

> %DCL-E-OPENOUT, error opening
> SYS$SYSROOT:[SYSMGR.]DECRAM-LIC-CHECK.TXT; > as output
> -RMS-E-DNF, directory not found

I know nothing, but I can certainly believe
that "[SYSMGR.]" is not found, as it
looks syntactically defective.

The next question would be: Did you mess with
the messages to confuse the reader, or is
this actual output? If it's all real, it
would appear that there's a problem in the
installation procedure supplied with the kit.

If your SYS$LOGIN is not plain SYS$MANAGER,
then you might try setting it to the plain
value before trying the installation again.

[Hein van den Heuvel]

Agree with Steven... looks like a bad (default) directory setup.
Just try again from a 'normal' account

But if you insist, then go check for the directory reported to cause trouble...

- What is the default ($SHOW DEF)
- Does SYS$SYSROOT:[SYSMGR.] exist?
- Are you allowed to write to it?
- Can you just pre-create SYS$SYSROOT:[SYSMGR.] and try again?
- Does SYS$COMMON:[SYSMGR.] exist?

hth,
Hein.

[Thomas Ritter]

Is there a previous version installed, if so remove it. DECRAM does not create any special directories. Or you could have a bad logical. Prehaps use the system account and attempt the installation.

$ mc sysgen show s2_size
Parameter Name Current Default Min. Max. Unit Dynamic
-------------- ------- ------- ------- ------- ---- -------
S2_SIZE 6000 0 0 -1 MBytes


2 cents.

[Dean McGorrill]

I agree with Steven to, it looks like pcsi
is getting confused. use the system account,
hopefully the login.com doesn't have junk
to confuse pcsi. (hope this helps, btw whats
a decram license cost) Dean

[B J DeNoyer]

The listing I provided is letter-for-letter exact, except that I replaced the real name of my subdirectory under SYS$MANAGER with "" -- which is the name of the subdirectory that holds the .PCSI installation file -- because I can't reveal the true name. This is a clean system build, so there is no previous version of DECRAM installed. I am user SYSTEM. The S2_SIZE parameter is set to the correct size. I have done everything in this installation attempt the same way I have done it successfully on multiple VMS 7.3-1 systems.

[B J DeNoyer]

Dean -- I have no idea what the license costs. We get our licenses via government procurement, so I never see the actual costs on any of them.

[Andy Bustamante]

You might try using the actual device name and absolute path for the directory. I've installed DECram on a 7.3-2 system using my_disk:[dist732] as the source without issues.

Andy

[Dean McGorrill]

B J,
I understand your position with the
government and disclosure. I wonder if its
getting confused with where the directory is. ie in sys$sysroot or sys$common. written in full the difference for sysmgr say root 0 is..

sys$sysdevice:[sys0.sysmgr]

sys$common is

sys$sysdevice:[vms$common.sysmgr]

you might move the install area off the system disk. Dean

[B J DeNoyer]

I have fixed my problem. I had installed TCPIP 5.4 with ECO 6 on this system -- and that seems to have messed up a lot of stuff. I reinstalled TCPIP, but using ECO 5 this time, and things are working OK now. Amazing how things get so inter-twined, isn't it?

[B J DeNoyer]

Problem was resolved when I re-installed TCPIP and an older ECO.