VMS732_PCSI V2.0 installation problem

[Ruud Dijt]

The DCLtables seams to be messed up during patch installation.

A set command/tables=sys$library:dcltables
and a secondtime installation of this patch seams to work
So the original kit is not correct.

The following product has been selected:
DEC AXPVMS VMS732_PCSI V2.0 Patch (maintenance update)

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.

DEC AXPVMS VMS732_PCSI V2.0: OpenVMS V7.3-2 PCSI V2.0

Files will not be renamed

* This product does not have any configuration options.

Execution phase starting ...

The following product will be installed to destination:
DEC AXPVMS VMS732_PCSI V2.0 DISK$ALPSYS732:[VMS$COMMON.]

Portion done: 0%...10%...20%...70%...90%...100%

The following product has been installed (and a recovery data set created):
DEC AXPVMS VMS732_PCSI V2.0 Patch (maintenance update)

DEC AXPVMS VMS732_PCSI V2.0: OpenVMS V7.3-2 PCSI V2.0

VMS732_PCSI-V0200 Release notes available


Release notes for the VMS732_PCSI-V0200 kit are available
at SYS$COMMON:[000000.SYSHLP]

%CLI-F-SYNTAX, error parsing 'DEFAULT_KIT'
-CLI-E-ENTNF, specified entity not found in command tables
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
0 000000007AFB0580 000000007AFB0580
0 000000007AFB0494 000000007AFB0494
0 000000007AFAF724 000000007AFAF724
0 FFFFFFFF800763F4 FFFFFFFF800763F4
0 FFFFFFFF800763F4 FFFFFFFF800763F4
PCSI$MAIN 0 0000000000051588 0000000000051588
PCSI$MAIN DCLQUALIFIER set_common_qualifiers
11550 0000000000000934 0000000000030934
PCSI$MAIN SPIU_COMMAND_VMS process_DCL
29963 000000000000C534 00000000000475E4
PCSI$MAIN SPIU_COMMAND_VMS main 32413 00000000000111E8 000000000004C298
PCSI$MAIN SPIU_COMMAND_VMS __main 0 000000000000009C 000000000003B14C
0 FFFFFFFF8026FED4 FFFFFFFF8026FED4

[Duncan Morris]

I also observed this behaviour during installation on our test systems. It would appear that the final phase does not do all that is required.

I will probably unpack the kit and check it out before it gets passed to the production team to deploy.

Looks like slack QA checking prior to release.

[Volker Halle]

Ruud,

this type of problem crops up from time to time, when images using new DCL qualifiers are shipped in an ECO kit and there is a missing DCL table update in the context of an installation (sub-)process.

A recent one was the /BLOCK_SIZE problem for COPY.

Log a call with HP.

Volker.

[Duncan Morris]

Yep, looks like a missing replace of DCLTABLES.EXE in the pcsi_postinstall.com.

The following snippet from the recent LMF update pcsi_postinstall.com shows what should happen....

$!
$! PCSI does not reinstall DCLTABLES after updating it (regression in
$! functionality fixed by next PCSI kit). Since this kit does not require a
$! reboot we need to install DCLTABLES here.
$!
$ INSTALL REPLACE SYS$LIBRARY:DCLTABLES.EXE/SHARE/OPEN/HEADER
$ SET COMMAND SYS$COMMON:[SYSUPD]LMF.CLD
$!

but this is totally missing in the PCSI V2 kit.

[Volker Halle]

Ruud,

this is more-or-less a 'cosmetic' problem, but you never know, what else should have been done during post-processing of the patch installation and did not happen due to the %CLI-F-SYNTAX error.

To make sure, everything is left in a consistent state, consider to just re-install the patch (after logout/login). This should work without an error (as the DCL table now has the new qualifier) and you'll be 100% sure, that your system has been correctly updated.

Volker.

[Ian Miller.]

I think doing
INSTALL REPLACE SYS$SHARE:DCLTABLES.EXE
then logging out/in should sort it out.

I think hp know about this but log a call to remind them.

[Ruud Dijt]

I had/have placed a call.

The thread was posted to keep everybody informed; i had taken already the necessary steps to solve the problem; As stated in the beginning of my thread.

[George_145]

When DCLTABLES is updated, the new DCLTABLES is not installed by PCSI, which should be done as PCSI part of PCSI's normal installation processing. This bug is actually fixed in the VMS732_PCSI-V0200 kit but to install that kit you need to use the old PCSI utility that has the bug - Catch 22.
To get around this, after installing the kit you can enter an INSTALL REPLACE DCLTABLES command after the installation completes. Users will still need to enter a SET COMMAND SYS$COMMON:[SYSUPD]PCSI.CLD comand or log out and back in to use the new PCSI qualifiers. After ececuting the INSTALL REPLACE DCLTABLES command, you do not need to re-install the kit.
This problem only affects the V7.3-2 PCSI kit. The correction is already in V8.2 and later. A new VMS732_PCSI-V0300 kit should be released today that works around the issue by installing DCLTABLES in a post-installation procedure.

[Ian Miller.]

new kit has been announced
http://www.openvms.org/stories.php?story=06/03/15/8371132