[Info-vax] VAX VMS going forward

[hb]

On 8/1/20 12:30 AM, Stephen Hoffman wrote:
> Not of having the code in P2 space to start with, without requiring the 
> system manager (directly or indirectly) post-processing the linker 
> output using the INSTALL tool to relocate parts into P2 space?
> 
> Wasn't I grumbling about the arcane 64-bit app development environment, 
> and folks here are now happily (and unwittingly) providing confirmations 
> of how chaotic this whole mess is?

It was said that all code has to fit in P0. That is not the case. 
Especially the often used VMS supplied shareable images have no code in 
P0. Do you care where their code is, as long as it is not in your way?

I didn't and do not want to argue about the ease of use of developing 
64-bit applications. But nothing stops you from making /SEGMENT=CODE=P2 
the linker default via a DCL symbol, a command procedure, an mm(s|k) 
makefile or a CLD file - without any help from a system manager.

And no, INSTALL does not relocate into P2 space.