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

Conference turris::decc_bugs

Title:	DEC C Problem Reporting Forum
Notice:	Report DEC C++ problems in TURRIS::C_PLUS_PLUS
Moderator:	CXXC::REPETETCHEON

Created:	Fri Nov 13 1992
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1299
Total number of notes:	6249

1293.0. "PLI-I-IOERROR during Install C 5.3" by UTRTSC::DORLAND (The Wizard of Odz2) Wed May 14 1997 11:27

    
    	Hello,
    
    	A customer tries to INSTALL CC053 on VAX VMS 6.1.
    	This fails. After analysing the problem it turns out
    	that the installation fails when generating .H files
    	with the following command (from GEN_STARLET.COM) :
    
    	 SDL/VAX/NOPARSE/LANG=CC=VMI$KWD:/C_DEV VMI$KWD:bccdefs.sdi
    
    	and
    
    	 SDL/VAX/NOPARSE/LANG=CC=VMI$KWD:/C_DEV VMI$KWD:sql_literals.sdi
    
    	The other .SDI files are parsed oke.
        The error is :
    
    %PLI-F-ERROR, PL/I ERROR condition.
    -PLI-I-IOERROR, I/O error on file 'SOURCE_FILE'.
    -PLI-I-FILENAME, File name: 'VOL:[MGR.COR.KWD]BCCDEFS.SDI;4'.
    -RMS-W-RTB, 23 byte record too large for user's buffer
    %TRACE-F-TRACEBACK, symbolic stack dump follows
    module name     routine name                     line       rel PC   
    abs PC
    
                                                               00099A4D 
    00099A4D
                                                               0009E875 
    0009E875
    OLDINTREE       OLDINTREE                         632      00000089 
    000864F9
    SDLMAIN         SDLMAIN                          2221      00000CBB 
    0008200F
    BVX09
    
    
    	I have extracted these files from STARTLETSD.TLB with the LIBEXT
    	utility, but the files look allright. I modified them by deleting
    	all the comments, but is doesn't help.
    
    	There is a small history to this. CC 5.3 was installed, next
    	CC 5.5 was installed, but this resulted in some problems
    	which could not be solved immediately. So the customer tries
    	to go back to 5.3...
    
    	I tried using a PLIRTL from VMS 6.2, but it didn't help.
    	So whats next?
    
    	Any help will be appreciated.
    
    	Regards, Ton
    	Any ideas? T

T.R	Title	User	Personal Name	Date	Lines
1293.1	I'll take a look at it.	DECC::ERICW		`Wed May 14 1997 17:12`	0
1293.2	Can't reproduce	DECC::ERICW		`Fri May 16 1997 14:21`	18
	I haven't been able to reproduce the problem, and unfortunately the error message itself is a bit bizzare in this context. A couple of questions come to mind: 1. Have you recently upgraded or otherwise tinkered with the PLI runtime library? It appears from the error message that SDL, a tool we use during the installation, requires the PLI RTL. 2. Have you tinkered with BCCDEFS.SDI or SQL_LITERALS.SDI at all? I assume you would have first confirmed that those files hadn't been modified before contacting us, but I am just checking. 3. If either of those questions doesn't lead you down a solution path, can you provide a complete installation log including any special options you chose? That would be helpful reproducing the problem. Eric
1293.3	Find Out What Stuck These Into STARLETSD	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Mon May 19 1997 10:47`	15
	The SDL and SDL/NOPARSE tools use PL/I. The modules BCCDEFS and SQL_LITERALS do not appear to be OpenVMS-provided components -- the latter module would tend to point at a locally-installed database package of some sort. I'm going on my recollection of the internal processing performed here by the DEC C installation kit, but I believe these are the tools used to "unpack" the definitions from the OpenVMS-provided STARLETSD into the various C include files. (Eric?) Determine where (and why) these modules were inserted into the STARLETSD library, and -- make a BACKUP copy of the STARLETSD library first -- remove these modules from the library, and then retry the DEC C V5.3 installation.
1293.4	The assumptions in .3 are correct.	DECC::ERICW		`Mon May 19 1997 15:32`	0
1293.5	BCCDEFS? SQL_LITERALS? Not On V7.1 Master Pack...	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Mon May 19 1997 16:50`	7
	: The modules BCCDEFS and SQL_LITERALS do not appear to be OpenVMS-provided : components -- the latter module would tend to point at a locally-installed : database package of some sort. I checked the listing of all modules present in OpenVMS VAX V7.1 release (yes, I know you're not yet running that OpenVMS release), and did not locate any references to either of the above-named two source modules.
1293.6	Problem solved.	UTRTSC::DORLAND	The Wizard of Odz2	`Thu May 22 1997 02:28`	7
	After close examination it turned out that these 2 modules were added on request of RDB software developers. After temporarily removing these modules the installation of C 5.3 went fine. Thankks for the replies, Ton