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

Conference dssdev::decforms

Title:	DECforms
Notice:	This is not an official software support channel. Kit info: 4.L
Moderator:	DSSDEV::FORMS

Created:	Thu Mar 23 1989
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4004
Total number of notes:	16520

3997.0. "Errors when linking forms objects with/map" by CSC32::D_BUTLER () Thu May 08 1997 13:19

I received a call recently claiming that when linking objects in the 
following environment the given errors occur. I realize that they are out
of date version wise but the development people at this site would
really like to get a map file.

ALPHA 2100 4/200
OPENVMS 6.1
DECFORMS 1.4D
FORTRAN 6.2

	if a /map switch is added to the link command the following occurs:

	%LINK-E-WRITERR
	%RMS-F-RAB
	%TRACE-E-TRACEBACK

This only occurs with a combination of /map and Decforms objects being linked.

DB

T.R Title User Personal
Name Date Lines

3997.1 and a possible answer is... CSC32::C_BENNETT Mon May 12 1997 15:00 47

T.R	Title	User	Personal Name	Date	Lines
3997.1	and a possible answer is...	CSC32::C_BENNETT		`Mon May 12 1997 15:00`	47
	Hello Dave, Attached please find an article which describes a pretty similar issue... I would reccomend 2.1B release of DECforms if /MAP is really really needed... Copyright (c) Digital Equipment Corporation 1995. All rights reserved. PRODUCT: DECforms Versions 1.4C, 1.4D OP/SYS: OpenVMS VAX Version 6.1 OpenVMS Alpha Version 6.1 SOURCE: Digital Equipment Corporation PROBLEM: While linking a DECforms based application with the /MAP qualifier, you receive the following error: %LINK-E-WRITEERR, error writing (filename) %TRACE-E-TRACEBACK, symbolic stack dump follows -RMS-F-RAB, invalid RAB or RAB not accessible %LINK-W-FAOFAIL, FAO system service failure WORKAROUND: Use one of the following to work around this problem: 1. Use the /NOMAP qualifier 2. Ugrade to DECforms version 2.1A MUP or greater ANALYSIS: If DECforms based objects are getting linked into the executable, one possible cause is that DECforms Version 1.4 for Alpha; specifically, the Extract Object utility has created .OBJ files with incomplete header lengths. This would cause the linker to abort when LINK /MAP was used. Use of the /NOMAP or upgrading to DECforms version 2.1A MUP or greater will fix this problem in that the FORMS EXTRACT OBJECT module will calculate and record the correct header lengths.

    Hello Dave,
    
    Attached please find an article which describes a pretty similar
    issue...   I would reccomend 2.1B release of DECforms if /MAP is
    really really needed...
    
    
Copyright (c) Digital Equipment Corporation 1995. All rights reserved.

PRODUCT:    DECforms Versions 1.4C, 1.4D

OP/SYS:     OpenVMS VAX Version 6.1
            OpenVMS Alpha Version 6.1

SOURCE:     Digital Equipment Corporation


PROBLEM:

While linking a DECforms based application with the /MAP qualifier,
you receive the following error:

%LINK-E-WRITEERR, error writing (filename)
%TRACE-E-TRACEBACK, symbolic stack dump follows
-RMS-F-RAB, invalid RAB or RAB not accessible
%LINK-W-FAOFAIL, FAO system service failure


WORKAROUND:

Use one of the following to work around this problem:

     1.  Use the /NOMAP qualifier

     2.  Ugrade to DECforms version 2.1A MUP or greater


ANALYSIS:

If DECforms based objects are getting linked into the executable, one
possible cause is that DECforms Version 1.4 for Alpha; specifically, the
Extract Object utility has created .OBJ files with incomplete header
lengths.  This would cause the linker to abort when LINK /MAP was used.

Use of the /NOMAP or upgrading to DECforms version 2.1A MUP or greater
will fix this problem in that the FORMS EXTRACT OBJECT module will
calculate and record the correct header lengths.