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

Conference turris::fortran

Title:Digital Fortran
Notice:Read notes 1.* for important information
Moderator:QUARK::LIONEL
Created:Thu Jun 01 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1333
Total number of notes:6734

1158.0. "ERRSET and Alpha 7.0 and Fortran 7.0" by EVTAI1::LEREUIL () Tue Feb 04 1997 04:34

    
    	Hi , my customer migrating from VAX to AXP with Fortran 7.0
    	and they are using the ERRSET routine on the VAX FORTRAN
    	this routine is not supported on ALPHA , I have seen the note
    	1764 on DEC_FORTRAN_ALPHA about this routine , but the qualifier
    	/CHECK=NOFORMAT for disable FORVARMIS has not effect , if you have
    	one or more ideas
    
    	Thanks indeed
    
    	Gerard-louis Lereuil
    	french CSC
T.RTitleUserPersonal
Name
DateLines
1158.1QUARK::LIONELFree advice is worth every centTue Feb 04 1997 09:354
What are they using ERRSET for?  What errors are they trying to modify the
behavior of and how?

				Steve
1158.2example, pleaseTLE::WHITLOCKStan WhitlockTue Feb 04 1997 15:389
1.  Please answer the questions in .1

2.  Please send us an example of what the user is trying to do with
    /CHECK=NOFORMAT but can't.  Please show the output on a VAX and the
    program that generated it {which shows what you want} and the program
    and output on Alpha.  Please include the compile line so we can see
    what comannd line options you're using in each case.

Thanks			/Stan
1158.3root fileEVTAI1::LEREUILThu Feb 06 1997 01:397
    
    	Hi , you can retrieve a file example to
    	RIVOLI::IDGCSLRAPPMPOUVPE01.SFO ou Rivoli address is 47.115
    
    	Thanks indeed
    
    	gerard-louis lereuil
1158.4QUARK::LIONELFree advice is worth every centThu Feb 06 1997 11:2331
The program calls ERRSET with error number 63, output conversion error, asking
that those errors not be displayed.  This has nothing to do with
/CHECK=FORMAT, which affects error 61, format-variable mismatch.  By default,
output conversion errors continue, so the problem here is how to suppress
the error message.

One could use IOSTAT=, but another way would be to use LIB$ESTABLISH to
establish the following condition handler in the main program:


	INTEGER*4 FUNCTION OUTCONERR_HANDLER (SIGARGS,MECHARGS)
	INTEGER SIGARGS(*),MECHARGS(*)
	INCLUDE '($FORDEF)'
	INCLUDE '($SSDEF)'
	OUTCONERR_HANDLER = SS$_RESIGNAL
	IF (SIGARGS(2) .EQ. FOR$_OUTCONERR) OUTCONERR_HANDLER=SS$_CONTINUE
	RETURN
	END


In the main program, you'd put:


	EXTERNAL OUTCONERR_HANDLER

	...

	CALL LIB$ESTABLISH(OUTCONERR_HANDLER)


				Steve
1158.5thanksEVTAI1::LEREUILFri Feb 07 1997 01:253
    
    	Hi , thanks indeed Steve
    	Gerard-louis