From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::%GIZMO.SRI.COM:RELAY-INFO-VAX" 24-APR-1989 20:20
To:	MRGATE::"ARISIA::EVERHART"
Subj:	Re: Problem with message pointers.

Received: From KL.SRI.COM by CRVAX.SRI.COM with TCP; Mon, 24 APR 89 16:42:11 PDT
Received: from LBL.Gov by KL.SRI.COM with TCP; Mon, 24 Apr 89 16:35:06 PDT
Received: from warner.hepnet by LBL.Gov with VMSmail ;
	Sat, 22 Apr 89 10:11:58 PDT
Date:    Sat, 22 Apr 89 10:11:58 PDT
From: nagy%warner.hepnet@LBL.Gov (Frank J. Nagy/VAX Guru&Wizard)
Message-Id: <890422101158.2340a818@LBL.Gov>
Subject: Re: Problem with message pointers.
To: Info-VAX@kl.sri.com
X-St-Vmsmail-To: INFO_VAX

I'm not sure what's wrong with what you are doing, but here is how I build
and use a message section (translating from MMS build files):

Compile all message sources for the section file:

	$ MESSAGE /NOSYMBOLS /OBJECT=xxxx.OBJ   xxxx.MSG
	
Link all these object files into a message section file:

	$ LINK /SHAREABLE=message-section  xxxx.OBJ,...,SYS$INPUTS:/OPTIONS
	GSMATCH=ALWAYS,1,0

The GSMATCH always allows matches so the version of the message section
file currentonly on the system will be used.

We then stick the message section file (called EPICUREMSG.EXE) in a
directory on the system pointed to by a system-wide logical name.  We
use RDCS$LIB, but you could just a well put it into SYS$MESSAGE: (make
sure you use SYS$COMMON:[SYSMSG] on a cluster).

Next the message source files are compiled again to product new object
files which will be linked into the user programs.  These new object
files define the symbols for the individual messages (as global symbols)
and include a pointer to the message section file.  Note that the previous
run of MESSAGE specified /NOSYMBOLS since these are unnecessary in making
the section file.  Now we use /NOTEXT since the message text is in the
section file AND /FILE so the section file is referenced.

    $ MESSAGE /NOTEXT /FILE=RDCS$LIB:EPICUREMSG.EXE  /OBJECT=xxxx  xxxx.MSG
    or
    $ MESSAGE /NOTEXT /FILE=SYS$MESSAGE:yours.EXE  /OBJECT=xxxx  xxxx.MSG

These resulting .OBJ files are then put in an object library referenced
in the user's LINKs.

All I can say is the above sequence of steps works for us.


= Dr. Frank J. Nagy   "VAX Guru & Wizard"
= Fermilab Research Division/Electrical and Electronics Dept/Controls Group
= HEPNET: WARNER::NAGY (43198::NAGY) or FNAL::NAGY (43009::NAGY)
= BitNet: NAGY@FNAL
= USnail: Fermilab POB 500 MS/220 Batavia, IL 60510