🚀 go-pugleaf

In article <1993Jan5.105637.25287@tc.cornell.edu> you write:
|>Having just begun porting an application to VMS on the Alpha, I have
|>a question concerning the format of the SYMBOL_VECTOR command in
|>a linker options file. Of course, I don't have the new linker manual.
|>I realize that one now replaces macro-coded transfer vectors by
|>linker options of the form:
|>
|>	SYMBOL_VECTOR=(routine1=PROCEDURE,routine2=PROCEDURE,...)
|>
|>etc. What other values are accepted in place of PROCEDURE? For
|>example, I have a VAX/VMS shareable image that defines a couple of hundred
|>universal message symbols (ie created in a .MSG file and linked in
|>with the shareable image). In the linker options file, I have:
|>
|>	UNIVERSAL=PROG__MSG1
|>	UNIVERSAL=PROG__MSG2, etc.
|>
|>What is the appropriate form of SYMBOL_VECTOR command to replace this?
|>Thanks, one and all.
|>
|>Steve

Steve,
	The SYMBOL_VECTOR linker option has multiple incarnations.. where
in general it is described as:

SYMBOL_VECTOR=([[alias_name/]symbol-name=]symbol-vector-entry-type)

symbol-vector-entry-type may be any of:

DATA		  - symbol vector for data cell
PRIVATE_PROCEDURE - creates enty for a routine that is not propageted to the 
		    GST of the shareable image
PRIVATE_DATA 	  - same as above except is for data
PROCEDURE 	  - vector entry for a routine entry
PSECT		  - create entry for a program section
SPARE		  - reserve space for a future entry

Notice that DEC also allowed for aliasing of symbol names.. I believe for the
replacement of what you have you want..

SYMBOL_VECTOR=(PROG__MSG1=DATA)
SYMBOL_VECTOR=(PROG__MSG2=DATA)

-Larry.