[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference evms::spia

Title:	Software Product Integration Architecture

Moderator:	STAR::HAMMOND

Created:	Fri Apr 28 1989
Last Modified:	Tue Jun 03 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	370
Total number of notes:	1977

368.0. "%PCSI-E-S_PRDNOTLOA, product not loaded into memory - Any idea why ?" by PEACHS::BECHTOLD () Tue Mar 04 1997 18:38

	Hello,

	I have a customer who has attempted to instal l Multimedia Service 
V2.0 off the DEC 96 OpenVMS Alpha Layered Product CD's and the SEP 96 CD's
as well with both kits failing on the following error. Thi sis on OpenVMS 
Alpha V6.2.

$prod install /sourc=cd:[mmov020.kit] mmov

The following product has been selected:
DEC AXPVMS MMOV V2.0

Do you want to continue? [YES] yes
%PCSI-E-S_PRDNOTLOA, product not loaded into memory
%PCSIUI-E-ABORT, fatal error encountered - operation terminated
$

He can successfully execute the following commands on the exact same
node.

$ PRODUCT SHOW PRODUCT/FULL
PRODUCT                        KIT TYPE   STATE      MAINTENANCE    REFERENCED
BY
-------                        --------   -----      -----------
-------------
DEC AXPVMS DQS V1.3-1          FULL       AVAILABLE
DEC AXPVMS DWMOTIF V1.2-3      FULL       AVAILABLE
DEC AXPVMS FORTRAN V6.3-711    FULL       AVAILABLE
DEC AXPVMS PERL V5.2-1         FULL       AVAILABLE
DEC AXPVMS TCL V7.5-2A         FULL       AVAILABLE
DEC AXPVMS VMS V6.2            OPER. SYS. AVAILABLE    DEC AXPVMS PERL V5.2-1
%PCSI-I-IOPPDB, additional information last updated 13-FEB-1997 in
DISK$AXPVMSSYS:[VMS$COMMON.][SYSUPD]VMSINSTAL.HISTORY;1

6 items found
$

And the following command.

$PRODUCT SHOW HISTORY
PRODUCT                        OPERATION       DATE/TIME
-------                        ---------       ---------
DEC AXPVMS BISON A2.3          REMOVE          23-JUL-1996 11:30:21
DEC AXPVMS EMOSAIC V2.10       REMOVE          23-JUL-1996 11:30:21
DEC AXPVMS FGREP V1.1          REMOVE          23-JUL-1996 11:30:21
DEC AXPVMS FLEX V2.5-2         REMOVE          23-JUL-1996 11:30:21
DEC AXPVMS GAWK V2.15-6        REMOVE          23-JUL-1996 11:30:21
        .
        .
        .
DEC AXPVMS VTX_WWW_GW T1.0     INSTALL         09-JUL-1996 11:41:44
DEC AXPVMS VMS V6.2            INSTALL         18-JAN-1996 13:44:21
DEC AXPVMS VMS V6.1-1H2        REMOVE          18-JAN-1996 13:44:21
DEC AXPVMS FORTRAN V6.3-711    INSTALL         11-AUG-1995 12:22:42
DEC AXPVMS DQS V1.3-1          INSTALL         12-JUL-1995 02:11:27
.
.
.
%PCSI-I-IOPPDB, additional information last updated 13-FEB-1997 in
DISK$AXPVMSSYS:[VMS$COMMON.][SYSUPD]VMSINSTAL.HISTORY;1

51 items found
$

I'm not sure why he's getting the error. I've made a reference copy of the
MMOV PCSI kit and reviewed the *.PCSI$DECSRIPTION file as follows.

DEC-AXPVMS-MMOV-V0200--1.PCSI$DESCRIPTION

product DEC AXPVMS MMOV V2.0 full ;
    software DEC AXPVMS VMS version minimum V6.2 ;
    execute start "@SYS$STARTUP:MMOV$STARTUP.COM" stop "@SYS$STARTUP:MMOV$SHUTD
    system parameter GBLPAGFIL minimum 4096 ;
    information RELEASE_NOTES phase after ;
    information PARAMETERS phase after ;
    if (<hardware device VIA0:>) ;
        information MUST_REBOOT phase after ;
        information NO_START phase after ;
    else if (<hardware device AUA0:>) ;
        information MUST_REBOOT1 phase after ;
        information NO_START1 phase after ;
    else ;
        information MIGHT_REBOOT phase after ;
        execute test @SYS$TEST:MMOV$IVP ;
    end if ;
    module [000000]MMOV$HELP.HLP type help module MULTIMEDIA ;
    file [SYSHLP]VO.HLP size 18 ;
    file [SYSHLP]AUDIOCONTROL.HLP size 7 ;
    file [SYSLIB]MMOV$DECSOUND.UID size 96 ;
.
.
.

I'm not sure what the issue is. Any help would be appreciated.

Regards,
Dave Bechtold
DTN 343-1216

T.R	Title	User	Date	Lines
368.1	Try newer PCSI images	EVMS::GLOSKOWSKI	`Wed Mar 05 1997 13:51`	7
	Dave, If the customer has access to newer PCSI images (ie. those that come with OpenVMS V7.1), ask them to install it and try again. If necessary, the newest available PCSI images can be obtained from Jim (STAR::Krycka). - Al
368.2	More information...	PEACHS::BECHTOLD	`Wed Mar 05 1997 19:00`	66
	Hello, The customer sent me more informatin today on this problem, it follows. Dave Bechtold ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ I've done a little more futzing and stumbled into something. > When PCSI is used to install or to register OpenVMS or any other > product, it creates the following four database files in SYS$SYSTEM: > > PCSI$FILE_SYSTEM.PCSI$DATABASE;1 > PCSI$PROCESSOR.PCSI$DATABASE;1 > PCSI$ROOT.PCSI$DATABASE;1 > DEC-AXPVMS-VMS-V0602.PCSI$DATABASE;1 > > The first three files are always created for any product that is > installed or registered. These three files are updated by future PCSI > operations. In addition to the files listed above, I have a number of versions of each of the following: PCSI$FILE_SYSTEM.SAVE$DATABASE PCSI$PROCESSOR.SAVE$DATABASE PCSI$ROOT.SAVE$DATABASE DEC-AXPVMS-VMS-V0602.SAVE$DATABASE ... (more for each of the other remaining products) Some interesting points to note are: 1) These .SAVE$DATABASE files exist over the time certain products were shown in the PRODUCT SHOW HISTORY display to have been installed then removed. Once removed, a product would no longer get new versions of this file. 2) None of these files pre-date 9-Jul-1996 and I don't recall ever deleting such files myself. I may PURGE such file but not delete them; however, these all go back to a version number of ;1. (I wouldn't have taken the time to renumber these things. :-) 3) I had a student working for me in July, 1996 and tinkering with the brand new Internet Product Suite. The first reference in my PCSI history to IPS being installed is the same date as the first version of each of these .SAVE$DATABASE files, though the time differs by about 13 minutes. Could these files be any indication of when things went wrong and how? Could these files be used in anyway to try to regain an operable PCSI utility? Thanks! --Bryan ========================================================================== Bryan R. Webb E-mail: webb@psc.edu VMS Systems Administrator Phone: (412) 268-5134 Pittsburgh Supercomputing Center Fax: (412) 268-5832 ========================================================================== Any help is appreciated... Regards, Dave Bechtold
368.3	Most likely a problem with the database files	STAR::KRYCKA	`Wed Mar 05 1997 20:46`	56
	I used the Sep-96 OpenVMS Alpha Software Product Library CDROM to successfully install MMOV V2.0 using V6.2 of the PCSI utility on my machine. Then I looked again at the PRODUCT SHOW PRODUCT and (partial) HISTORY displays in .0. It appeared that the customer had installed most or all of the products in the Internet Product Suite (IPS) V1.0, then attempted to remove all products. However, PERL and TCL are still listed as installed without the INTERNET_PRODUCT platform product being listed which is normally present if any of the optional products it contains is installed. It turns out that the PCSI utility shipped on the IPS V1.0 CDROM (which is used to install the IPS products) had a bug such that if you tried to remove all IPS products, PERL and TCL would be left on the system. This by itself should not be harmful (as far as PCSI is concerned), and I would expect that the user could perform a separate PRODUCT REMOVE of those two products to really get rid of them. [The PCSI utility on the IPS V1.2 CDROM fixes this removal problem, so that a removal of IPS removes everything.] I was about to suggest that the customer try to remove PERL and TCL, then try to install MMOV. However, after reading .2, there is the possibility that the PCSI database files are out of sync. PCSI does not create .SAVE$DATABASE files. I would assume that the person working for Bryan Webb last summer made a copy of the PCSI database files before experimenting with the IPS. If that is the case, and no other products were installed since then (excluding the IPS products which were removed), then restoring the saved copy of the PCSI database will likely solve the problem. I suggest doing the following: 1. PRODUCT REMOVE PERL,TCL Assuming that these products are not wanted. If this operation fails then there is something amiss with the database files. Regardless of the outcome, proceed to step 2. 2. Rename SYS$COMMON:[SYSEXE].PCSI$DATABASE;* to something else. 3. Rename SYS$COMMON:[SYSEXE].SAVE$DATABASE;1 to .;1. >>> Note that PCSI requires the its database files be version 1. <<< 4. Execute PRODUCT SHOW PRODUCT/FULL and PRODUCT SHOW HISTORY/FULL commands. This is just to verify that the database files are useable and reflect what you think is really installed. 5. PRODUCT INSTALL MMOV If MMOV still can't be installed, then the PCSI database will have to be deleted and recreated as described in note 359. One ohter thing - the .PCSI$DATABASE files are an interconnected set of files. You cannot just restore some of them, or delete one of them. So make sure that when you rename the *.PCSI$DATABASE files, you rename a set of files that were created by PCSI at the same time. - Jim Krycka
368.4	Thanks - Custoemr fixed!	PEACHS::BECHTOLD	`Thu Mar 06 1997 16:58`	186
	Hi Jim, Thanks for .3 it added in resolving the customers problem. Below are the customer comments with respect to this issue. <Customer message> > 1. PRODUCT REMOVE PERL,TCL > > Assuming that these products are not wanted. If this operation fails > then there is something amiss with the database files. Regardless of > the outcome, proceed to step 2. This turned out to be a major flop: GANGES [system]> product sho prod * PRODUCT ------- DEC AXPVMS DQS V1.3-1 DEC AXPVMS DWMOTIF V1.2-3 DEC AXPVMS FORTRAN V6.3-711 DEC AXPVMS PERL V5.2-1 DEC AXPVMS TCL V7.5-2A DEC AXPVMS VMS V6.2 %PCSI-I-IOPPDB, additional information last updated 5-MAR-1997 in DISK$AXPVMSSYS:[VMS$COMMON.][SYSUPD]VMSINSTAL.HISTORY;1 6 items found GANGES [system]> prod remove perl,tcl The following products have been selected: DEC AXPVMS PERL V5.2-1 DEC AXPVMS TCL V7.5-2A Do you want to continue? [YES] yes %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000140, PC=00180408, PS=0000001B %TRACE-F-TRACEBACK, symbolic stack dump follows Image Name Module Name Routine Name Line Number rel PC abs PC PCSI$SHR SPIU_ORDER_CONT spiu_collate_pr 4562 000021B8 00180408 PCSI$SHR SPIU_ORDER_CONT spiu_initiate_e 6556 000029FC 00180C4C PCSI$SHR SPIU_ORDER_TOTA spiu_form_total 5750 00003288 0018CA88 PCSI$SHR SPIU_API_OPERAT spiu_remove 6809 00004C28 00149388 PCSI$MAIN UICOMMON UIexecute_opera 10396 00001D54 0003DB74 PCSI$MAIN SPIU_COMMAND_VM process_command 12451 000055C8 000355C8 PCSI$MAIN SPIU_COMMAND_VM main 13808 00006638 00036638 PCSI$MAIN SPIU_COMMAND_VM __main 0 00000050 00030050 0 828BA170 828BA170 GANGES [system]> > 2. Rename SYS$COMMON:[SYSEXE].PCSI$DATABASE; to something else. > > 3. Rename SYS$COMMON:[SYSEXE].SAVE$DATABASE;1 to .;1. > > >>> Note that PCSI requires the its database files be version 1. <<< I did 2 but before doing 3 I retried something I had tried previously using the note with 3. I had previously tried a simple use of CONVERT to make a new clean copy of each of the PCSI$.PCSI$DATABASE files. This time, I made sure their version numbers were 1. (BTW, this isn't a nice restriction, folks. :-) Anyway, my idea failed, so I did 3 as described. > 4. Execute PRODUCT SHOW PRODUCT/FULL and PRODUCT SHOW HISTORY/FULL commands. > > This is just to verify that the database files are useable and reflect > what you think is really installed. This worked fine and nothing before the attempt install of the Internet Product Suite appears now. > 5. PRODUCT INSTALL MMOV This also went off without a hitch now. > One ohter thing - the .PCSI$DATABASE files are an interconnected set of > files. You cannot just restore some of them, or delete one of them. So > make sure that when you rename the .PCSI$DATABASE files, you rename a set > of files that were created by PCSI at the same time. I just want to note that while my product list and product history are much shorter, I still have .PCSI$DATABASE files for each of the IP Suite products. The outputs are as follows: GANGES [system]> prod show prod/full PRODUCT KIT TYPE STATE MAINTENANCE REFERENCED BY ------- -------- ----- ----------- ------------- DEC AXPVMS DQS V1.3-1 FULL AVAILABLE DEC AXPVMS DWMOTIF V1.2-3 FULL AVAILABLE DEC AXPVMS FORTRAN V6.3-711 FULL AVAILABLE DEC AXPVMS VMS V6.2 OPER. SYS. AVAILABLE %PCSI-I-IOPPDB, additional information last updated 5-MAR-1997 in DISK$AXPVMSSYS:[VMS$COMMON.][SYSUPD]VMSINSTAL.HISTORY;1 4 items found GANGES [system]> prod show history/full PRODUCT OPERATION DATE/TIME KIT TYPE ERRORS USER REMARK ------- --------- --------- -------- ------ ---- ------ DEC AXPVMS VMS V6.2 INSTALL 18-JAN-1996 13:44:21 OPER. SYS. 0 SYSTEM DEC AXPVMS VMS V6.1-1H2 REMOVE 18-JAN-1996 13:44:21 OPER. SYS. 0 SYSTEM DEC AXPVMS FORTRAN V6.3-711 INSTALL 11-AUG-1995 12:22:42 FULL SYSTEM DEC AXPVMS DQS V1.3-1 INSTALL 12-JUL-1995 02:11:27 FULL SYSTEM DEC AXPVMS DWMOTIF V1.2-3 INSTALL 10-JUL-1995 02:45:33 FULL SYSTEM DEC AXPVMS VMS V6.1-1H2 INSTALL 07-JUL-1995 10:44:16 OPER. SYS. 0 SYSTEM %PCSI-I-IOPPDB, additional information last updated 5-MAR-1997 in DISK$AXPVMSSYS:[VMS$COMMON.][SYSUPD]VMSINSTAL.HISTORY;1 6 items found GANGES [system]> GANGES [system]> dir .pcsi$database/col=1 Directory SYS$COMMON:[SYSEXE] DEC-AXPVMS-BISON-A0203.PCSI$DATABASE;1 DEC-AXPVMS-DQS-V0103-1.PCSI$DATABASE;1 DEC-AXPVMS-DWMOTIF-V0102-3.PCSI$DATABASE;1 DEC-AXPVMS-EMOSAIC-V0210.PCSI$DATABASE;1 DEC-AXPVMS-FGREP-V0101.PCSI$DATABASE;1 DEC-AXPVMS-FLEX-V0205-2.PCSI$DATABASE;1 DEC-AXPVMS-FORTRAN-V0603-711.PCSI$DATABASE;1 DEC-AXPVMS-GAWK-V0215-6.PCSI$DATABASE;1 DEC-AXPVMS-GREP-V0200.PCSI$DATABASE;1 DEC-AXPVMS-HLP2HTML-V0100.PCSI$DATABASE;1 DEC-AXPVMS-HTML2PS-V0001.PCSI$DATABASE;1 DEC-AXPVMS-INTERNET_PRODUCTS-V0100.PCSI$DATABASE;1 DEC-AXPVMS-MMOV-V0200.PCSI$DATABASE;1 DEC-AXPVMS-MPEG_PLAY-V0000.PCSI$DATABASE;1 DEC-AXPVMS-NS_NAV_EXPORT-V0200-1B6A.PCSI$DATABASE;1 DEC-AXPVMS-PERL-V0502-1.PCSI$DATABASE;1 DEC-AXPVMS-PURVEYOR-V0101-0B.PCSI$DATABASE;1 DEC-AXPVMS-SED-V0205.PCSI$DATABASE;1 DEC-AXPVMS-TCL-V0705-2A.PCSI$DATABASE;1 DEC-AXPVMS-TK-V0401-2A.PCSI$DATABASE;1 DEC-AXPVMS-UNZIP-V0401-0A.PCSI$DATABASE;1 DEC-AXPVMS-VMS-V0602.PCSI$DATABASE;1 DEC-AXPVMS-VTX_WWW_GW-T0100.PCSI$DATABASE;1 DEC-AXPVMS-WEBHLB-V0100.PCSI$DATABASE;1 DEC-AXPVMS-WEBMON-V0100.PCSI$DATABASE;1 DEC-AXPVMS-XV-V0310.PCSI$DATABASE;1 DEC-AXPVMS-YACC-V0100.PCSI$DATABASE;1 DEC-AXPVMS-ZIP-V0200.PCSI$DATABASE;1 PCSI$FILE_SYSTEM.PCSI$DATABASE;1 PCSI$PROCESSOR.PCSI$DATABASE;1 PCSI$ROOT.PCSI$DATABASE;1 Total of 31 files. GANGES [system]> They don't take up much space so I won't worry about them, but I thought it an interesting point to note. I appreciate all the help. (It may seem straight-forward when you work with these details alot, but when you don't it looks scary. :-) Thanks! <End of customer message> Again thanks for the help. Dave Bechtold DTN 343-1216
368.5	The database files you need are ...	STAR::KRYCKA	`Thu Mar 06 1997 17:44`	10
	It's good to hear that restoring the old PCSI database files allowed your customer to install MMOV. > I still have .PCSI$DATABASE files for each of the IP Suite products. These extra database files must be an artifact from your renaming process. They are not needed and are not used by PCSI because they are not referenced by PCSI$ROOT.PCSI$DATABASE. You need the three core files: PCSI$ROOT, PCSI$PROCESSOR, and PCSI$FILE_SYSTEM, plus one for each of the installed products: DQS, DWMOTIF, FORTRAN, MMOV, and VMS.