1831809 Members
2713 Online
110030 Solutions
New Discussion

7.3-2 <> 7.3-2 ????

 
Willem Grooters
Honored Contributor

7.3-2 <> 7.3-2 ????

A collegue encountered a weird problem when trying to apply patches to OpenVMS 7.3-2 on PersonalAlpha (latest (128Mb) edition: it seems VMS 7.3-2 is not to be 7.3-2: See attachement.


Willem Grooters
OpenVMS Developer & System Manager
5 REPLIES 5
Karl Rohwedder
Honored Contributor

Re: 7.3-2 <> 7.3-2 ????

What does a PROD SH PROD *VMS/FU tell you?

regards Kalle
Robert Gezelter
Honored Contributor

Re: 7.3-2 <> 7.3-2 ????

Willem,

I concur. Is there any possibility that the product database is out of sync with the system?

- Bob Gezelter, http://www.rlgsc.com
Willem Grooters
Honored Contributor

Re: 7.3-2 <> 7.3-2 ????

Sure.....
%PCSI-E-OPENIN, Error opening SYS$SYSDEVICE:[VMS$COMMON.][SYSEXE]PCSI$ROOT.PCSI$DATABASE as input.
-RMS-E-FNF, file not found

...

Duh.
The instance is set up for testing new setup and so the original 9Gb system disk was backed up. PersonalAlpha can handle 4Gb at max - so the disk was squeezed to that size and in that process, all files considered "not needed" were deleted - including *.PCSI$DATABASE files.

They were needed after all. It was after ALL *.PCSI* files (except for the kits) needed to be restored before installation could succeed.

Willem Grooters
OpenVMS Developer & System Manager
Willem Grooters
Honored Contributor

Re: 7.3-2 <> 7.3-2 ????

Lesson learned: Leave *.PCSI* in SYS$SYSTEm alone. These are needed by PRODUCT to check dependencies...
Willem Grooters
OpenVMS Developer & System Manager
Hein van den Heuvel
Honored Contributor

Re: 7.3-2 <> 7.3-2 ????


Wim,

Next time when someone creates a reply which leads you to solve the problem, then assign 10, or at least 8 points. The price is right!

That way we get to see the silly bunny and we know the problem was solve.

Here, Kalle's answer was the perfect question and should get 10 points. It made you think, and that was the solution!

Groetjes,
Hein.