HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Alpha V8.2-based Infoserver?

 
Larry Bohan
Advisor

Alpha V8.2-based Infoserver?

Anyone have this working on 8.2?

I don't recall reading anything inre in the
release notes; I expect it's unsupported,
or was pulled from 8.2 release.

perhaps the exe/help are placeholders
(this looks to be the case).

but if not, I'd figure there would be
a driver to load and/or server process to
start. (or perhaps a beta/test kit)

any ideas?

A1110> mount/for/system/noass LDA61:
%MOUNT-I-MOUNTED, 82SA mounted on _$1$LDA61: (A1)
A1110> MCR ESS$INFOSERVER
InfoServer> CREATE SERVICE BOOT82SA LDA61:
InfoServer> SHOW SERVICE
%INFOSRVR-I-FOUND, 0 services found.
InfoServer> exit
6 REPLIES
John Gillings
Honored Contributor

Re: Alpha V8.2-based Infoserver?

Larry,

Latent support. It may end up in V8.3 - watch for New Features or Release notes.
A crucible of informative mistakes
Peter Weaver_1
Frequent Advisor

Re: Alpha V8.2-based Infoserver?

You can find the documentation for this in chapter 4 of the 8.2-1 IA64 release notes (http://h71000.www7.hp.com/doc/82FINAL/6676/ba322-90033.pdf). I have played with the 8.2 version on both Alpha and IA64 but I never tried serving a container mounted /FOREIGN. The docs say /FOREIGN will work though. Do you have both SYSPRV and OPER?

Peter Weaver
http://www.weaverconsulting.ca/
CHARON-VAX, CHARON-AXP
Larry Bohan
Advisor

Re: Alpha V8.2-based Infoserver?

Thanks for the doc pointer;

All privs (tried both /foreign, and not)
Same result. Guess it'll wait il Alpha 8.3..

I take it, you've seen/have this working on I64/8.2-1? just curious.

Robert Gezelter
Honored Contributor

Re: Alpha V8.2-based Infoserver?

Larry,

Try the OpenVMS 8.3 Software Developer Kit. See http://h71000.www7.hp.com/news/sdk_8_3_announce.html

- Bob Gezelter, http://www.rlgsc.com
Peter Weaver_1
Frequent Advisor

Re: Alpha V8.2-based Infoserver?

I have seen it work on 8.2 Alpha and IA64. Did you remember to @SYS$STARTUP:ESS$LAD_STARTUP.COM? The book said to edit SYS$STARTUP:ESS$LAD_STARTUP.DAT first, but I think I just left it alone and used the defaults.

If that does not help then post the results of

InfoServer> show server
Larry Bohan
Advisor

Re: Alpha V8.2-based Infoserver?

I got a bit further with this;
P. Weaver's remarks helped me notice that
I fat-fingered the ess$_startup's.

I can create a service for a LDAn: device
(mounted /nowrite, or /foreign) from the Alpha 8.2 using ess$infoserver.

from other 7.3-2/8.2 Alpha nodes, I can bind to it (via ladcp), and mount it (DADn:)

I tried various combinations of boot-flags
(notably bit 10, lad/last bootstrap),
w/ an LDAn: built from AXPVMS$PCSI_INSTALL_MIN.COM, as well as a
an LDAn: image of a 7.3-2 binary/install CDROM.

Both wind up looking for a disk server,
"%VMScluster-I-REINIT_WAIT, ...Waiting for access to the system disk server"
(regardless that I dithered the LDAn:'s alphavmssys.par with vaxcluster=0, etc)

What I was hoping for, was to use this as a way to boot into a standalone/minimum environment, off a remote CDROM (or LDAn), without acting/joining as a cluster satellite.

eg, perhaps to booting into a ISL environment first, the "Network Initial System Load Function", from which one might choose a
disk service.

[..Some of my confusion may stem from the fact, that I've never seen even one InfoServer, and as such, might be mistaken
about what functionality to expect ..]

f.ex, I'm wondering if there are some ess$isl*.* pieces I need to be looking at,
or addtl loaders on the mop client setup (decnet/osi)


>>>boot -prot mop -flags e,401 ewa0
(boot ewa0.0.0.9.0 -flags e,401)

Trying MOP boot.
..........

Network load complete.
392 Packets, Max pkt size 1492, Retries 0
Loaded by: aa-00-04-00-48-04
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 8dc00(580608)
initializing HWRPB at 2000
initializing page table at 3ff20000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
%VMScluster-I-SYSDISK, Satellite system disk is
%VMScluster-I-SYSROOT, Satellite system root is [SYSE.]
%EWA-I-BOOTDRIVER, Console setting is FastFD (Full Duplex)
%EWA-I-BOOTDRIVER, Found onboard DE500
%EWA-I-BOOTDRIVER, Selected 100baseTX FDX (DE500-BA, onboard DE500)
%VMScluster-I-BUSONLINE, LAN adapter is now running 00-10-64-30-62-F5
cluster-W-PROTOCOL_TIMEOUT, NISCA protocol timeout
%VMScluster-I-REINIT_WAIT, Waiting for access to the system disk server
%VMScluster-I-BUSONLINE, LAN adapter is now running 00-10-64-30-62-F5
cluster-W-PROTOCOL_TIMEOUT, NISCA protocol timeout

As opposed, to something I expected would
look something like, what's seen here:

http://h18002.www1.hp.com/alphaserver/docs/userguide/WebHelp/infoserver_boot.htm