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

Conference clt::cobol

Title:	VAX/DEC COBOL
Notice:	Kit,doc,performance talk info-->DIR/KEY=KIT or DOC or PERF_TALK
Moderator:	PACKED::BRAFFITT

Created:	Mon Feb 03 1986
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3250
Total number of notes:	13077

3205.0. "ACCVIO in DEC$COBRTL" by MLNCSC::DELLAPERGOLA () Wed Feb 26 1997 09:14


	Hi


	a customer is porting a program running on AXP OpenVms 1.5 to
	AXP OpenVMS 6.2. 

	He has installed DEC COBOL 2.3 and now at execution time
	he obtains an ACCVIO.

	Command for compile and link are 
	$ COBOL/ANSI/NOOP
	$ LINK

	Access violation, reason mask=00, virtual address=202020F1,
	PC=011A7ED8, PS=0000001B

	Symbolic stack dump follows
	Image name  Module name  Routine name Line Number  rel PC  abs PC
	DEC$COBRTL				        0 0002FED8 011A7ED8
	MENUQ       PINV_PRT	 PINV_PRT	     4034 0000A4F8 00AFDCE8
	MENUQ	    PINVPRTD     PINVPRTD	     2198 00006B18 00DFFB78
	MENUQ	    PINVD	 PINVD		     4411 00015A8C 00AE2B9C
	MENUQ       MENU	 MENU		     1543 000018A0 008618A0
	MENUQ						0 00F17C40 00F27C40
	MENUQ						0 83612170 83612170

	Access violation, reason mask=00, virtual address=202020EF,
        PC=011865F0, PS=0000001B

	....................................................
	....................................................

	Running the Debug the program accvio at a WRITE statement causing
	
	< break on unhandled exception at SHARE$DEC$COBRTL+196312 >

	Has anyone suggestion on how isolate the problem?

	Trying with DEC Cobol 2.4 gives same results.

	Thanks and best regards 

	Anna Della Pergola

T.R	Title	User	Personal Name	Date	Lines
3205.1		WENDYL::BLATT		`Wed Feb 26 1997 09:41`	11
	make sure you have the correct Cobol Rtl installed. Compile with /check=all to be sure nothing is out of range. If none of these resolve your problem, we will need more information to track down any possible compiler/rtl problems. Also, .0 shows using /NOOP. You could try /OPT.
3205.2	Check parameters to RTL routine.	CPEEDY::FLEURY		`Thu Feb 27 1997 12:36`	7
	Re: .0 The virtual address of the ACCVIO looks suspect. Please be sure that the parameters to the RTL routine are passed correctly. The 202020 portion is equivalent to ascii spaces. Dan
3205.3		MLNCSC::DELLAPERGOLA		`Fri Feb 28 1997 08:01`	22
	Hi the accvio message is caused by a WRITE (Cobol Statement) DBG> 4031: ADD 1 TO WS-PAGE-COUNTER 4032: MOVE WS-PAGE-COUNTER TO TITLE2-PAGE-COUNTER 4033: MOVE PRINT-TITLE1 TO PRINT-LINE 4034: WRITE PRINT-LINE AFTER ADVANCING PAGE stepped to PINV-PRT\%line 4034 4034: WRITE PRINT-LINE AFTER ADVANCING PAGE break on unhandled exception at SHARE$DEC$COBRTL+196312 So there is not a direct call from Cobol program to RTL routine Thanks and best regards Anna Della Pergola
3205.4		QUARRY::neth	Craig Neth	`Fri Feb 28 1997 09:52`	5
	While this certainly could be an RTL bug, that seems relatively unlikely. What seems much more likely to me is that the application is writing off the end of an array and into memory that the RTL uses. The suggestions in .1 are right on. Have you tried using /CHECK yet?
3205.5	Try V2.4	PACKED::BRAFFITT		`Sun Mar 02 1997 22:49`	12
	> He has installed DEC COBOL 2.3 and now at execution time > he obtains an ACCVIO. At least one case of a runtime ACCVIO was fixed with V2.4. Make sure to install both the V2.4 compiler and RTL. V2.4 is shipping from the SSB. See CLT::DEC_COBOL_IFT note 2 for a pointer to the SSB kit for internal use. If you still have problems after you have installed both the V2.4 compiler and the V2.4 RTL, try the other suggestion (to compile /CHECK).