install> /share=ADDRESS - Any downside?

[Richard J Maher]

Hi Hartmut,

Sorry for being vague. SYS$UPDATE:VMSINSTAL run IVP after having run SYS$STARTUP:T3$STARTUP which itself tries to install the image /SHARE=ADDRESS. The installation was run from the SYSTEM account with all privs enabled. Doing it "outside" of VMSINSTAL does not exhibit the same error.

Can you please show me the INSTALL HELP ADD /SHARE from a version of Alpha/VMS 7.2-2 or lower?

Maybe it's me?

Cheers Richard Maher

[Richard J Maher]

Hi Hartmut,

I found this link that certainly says the ADDRESS_DATA option was well and truly arrived as of Alpha/VMS 7.2

http://mail2.fwd.com/cgiplus-bin/conan?key=V72_Features~Programming_Features&explode=yes&title=VMS%20Help&referer=

A curious buglet on my 7.2-2 system is that a INSTALL> LIST without a specific filename shows up everything installed as "SharAddr": -
SYSMSG;1 Open Hdr SharAddr Lnkbl
T3$MSG;1 Open Hdr SharAddr Lnkbl
TCPIP$MSG;1 Open Hdr SharAddr Lnkbl

Yet: -
$install lis/full sys$message:t3$msg

DISK$ALPHASYS:.EXE
T3$MSG;1 Open Hdr Shared Lnkbl
Entry access count = 0
Current / Maximum shared = 1 / 0
Global section count = 1

Makes it hard to locate which ones are installed share=address.

Anyway, If anyone can shed any light on why the attached startup file would give the previously discussed NOPRIV error when run from SYS$UPDATE:VMSINSTAL : -

$ VMI$CALLBACK PROVIDE_FILE TIER3_ T3$STARTUP.COM VMI$ROOT:[SYS$STARTUP]
$ VMI$CALLBACK SET STARTUP T3$STARTUP.COM

Yet work without error when run directly then please let me know!

BTW, all's fine of IA64 8.3-1H1.

In the meantime I'm off to code a hardware/OS specific work-around for my other hardware/OS specific work-around :-(

Cheers Richard Maher

PS. looks like DECWindows is the only real user on my 7.2-2 system?