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

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

338.0. "Access violation - CCM option" by ISIDRO::LOURDES (Lourdes Rebollar, EIS Spain) Thu Mar 26 1992 16:33

Hello,

We are having some problems when we compile the CM text library from the CCM
option of the System Customization Management Menu.

We have VMS V5.4-2 with ALL-IN-1 V2.4.

When I try the CCM option, I get the following dump:

.......
.......
TXL> BLP MRE$BUILD_GRS_INDEX
TXL> BLP MRE$BUILD_NOGRS_FILE

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=008D3600, PC
=00173604, PSL=03C00001

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                008D3600
        Name   = 0000000C                00000000
                 00000000                008D3600
                 008D3600                00000000
                 00173604                00000000
                 03C00001                2FFC0000
                                         7FE6CA5C
                                         7FE6CA20
                                         001329E3
                                         00000330

        Register dump

        R0 = 00000000  R1 = 7FE6AC74  R2 = 00000000  R3 = 7FE6AEA4
        R4 = 00000000  R5 = 00000000  R6 = 00000025  R7 = 7FE6ACFC
        R8 = 008D35DA  R9 = 008D3600  R10= 7FE6AEA4  R11= 7FE6BE35
        AP = 7FE6AC38  FP = 7FE6ABF8  SP = 7FE6AC74  PC = 00173604
        PSL= 03C00001

but if I compile it with:
ALLIN1/NOINI
OA$TXL_COMPILE CMTXL

the compilation is fine.

Any help ? If you need more information. please let me know.

Looking forward to your answer
Thanks in advance and best regards,

Lourdes.

    
T.RTitleUserPersonal
Name
DateLines
338.1Check files in the directorySHALOT::NICODEMWho told you I'm paranoid???Fri Mar 27 1992 18:064
	Have you checked for a bad file?  (E.g., a non-template file -- such as
a journal file left over from the editor -- in a BLP directory)

	F
338.2checkedISIDRO::LOURDESLourdes Rebollar, EIS SpainMon Mar 30 1992 11:488
    Yes, I have checked that.
    
   $ dir oa$blp:/exclu=*.blp
     %DIRECT-W-NOFILES, no files found
    
    Thanks,
    
    Lourdes
338.3maybe non asciiSHALOT::GEERDESMon Mar 30 1992 21:094
Check the MRE$BUILD_NOGRS_FILE.BLP is it actually ASCII? Or check the file
after this one.	

	Ben
338.4are ASCIIISIDRO::LOURDESLourdes Rebollar, EIS SpainTue Mar 31 1992 09:5323
    Ben,
    
    I have checked these files. They are ASCII. they only have one line
    each one, they are:
    
    MRE$BUILD_NOGRS_FILE.BLP:
    
    <mre$e_message.message["%MRE-E-NGR"]>
    
    MRE$BUILD_NOPRS_FILE.BLP:
    
    <mre$e_message.message["%MRE-E-NPR"]>
    
    They mustn't be the problem, because they existed before and never they
    had had problems.
    
    Any idea more?
    
    Thaks and regards,
    
    Lourdes
    
                                                              
338.5More help requiredBEAGLE::WOODAre you sure this is the way?Wed Apr 08 1992 12:4657
    I have some further information on this call.  Anybody have some ideas
    as to what Quotas might be low given the following; 

Checking everything in OA$SITE_BLP_xxx is a BLP file       
there's no corruption in the file where the compilation      
some other test shows the following results:              
    
A)	If entering ALL-IN-1 using ALLIN1/NOCUSTOM, option CCM        
	the same behaviour. This implies the original script         
	is being used.                                 
    
B)	Entering ALL-IN-1 using ALLIN1/NOINIT and doing DO CM_CDS     
	the same result.                                             
    
C)	When entering ALL-IN-1 using ALLIN1/NOINIT and doing          
	CMTXL, no error is generated.                     
    
D)	Same as c) doing <DO OA$TXL_COMPILE CMTXL from any            
	screen.                                                 
    
E)	If you invoke the following script instead of the             
	CM_CDS.SCP, the compilation goes OK (as you can         
	this script contains the same instructions as the           
	CM_CDS.SCP, but the .IF, GOTO and .LABEL ones:          

! OUR_CM_CDS.SCP                                                 
!+                                                               
GET #CM_TXL = "CDS"                                              
OA$FAO OA$_SCM_TXL_COM,"#CM_TEMP",#CM_TXL                        
YESNO_PROMPT #CM_TEMP\OA$FLD_STAY                                
.IF OA$PROMPT_DISPOSE NE 2 THEN .EXIT                            
CLEAR\OA$TXL_COMPILE CMTXL\OA$TXL_REMOVE CMTXL\OA$MSG_PURGE      
GET OA$DCL = "SET PROTECTION = W:RE OA$LIB:CMTXL.TXL"            
OA$TXL_INSTALL CMTXL                                             
PURGE_FILE OA$LIB:CMTXL.TXL,2                                    
OA$FAO OA$_SCM_TXL_COP,"OA$DISPLAY",#CM_TXL                      
.EXIT                                                            
    
F)	If you move the BLP's from OA$SITE_BLP_SHARE to               
	OA$SITE_BLP_LLV and the ones from _LLV to _SHARE, no error       
	is obtained.                                                     
    
G)	If you move every BLP to OA$SITE_SHARE or to                  
	OA$SITE_ENGLISH, no error.                                       
    
H)	If you generate in OA$SITE_BLP_ENGLISH a BLP similar in       
	name to those in OA$SITE_BLP_SHARE (all of them in the form      
	MRE$*.BLP), an access violation occurs, but in a different       
	file than previous tests.                                        
    
As we are thinking in something similar to insufficient          
memory to do the compilation, we've tested increasing the        
process quotas of the ALLIN1 account (WSDEFAULT, WSQUOTA,        
BYTLM, ENQLM, PGFQUOTA, DIOLM, BIOLM) but no result.             
    
    Cheers,
    Andy
338.6txl problem revisitedARNIES::SMITHP1Raiders of the Lost ConferenceThu Oct 29 1992 15:248
	Bit too late for you Andy, but just in case anyone else comes
	across this problem (like I just did!)....

	You will need to execute the OA$TXL_CLOSE function before the
	OA$TXL_REMOVE and OA$TXL_COMPILE functions.

		p1