OpenVMS 8.3 DECwindows setup

[WADE S]

I had an Integrity BL860c server blade sent to me running OpenVMS 8.3. I'm not a OpenVMS user, and I was hoping someone could tell me how to configure the DECwindows system, or point me to the correct documentaion for it. I have verified that all packages needed to run it were installed, but haven't been able to get the windows system working.

Thanks,

[Richard Whalen]

I know that it's not much help, but "it should be set up automatically".

What does
$ show logical decw*
display?

[WADE S]

The BL860c has no graphics device, so I think it needs to be setup to display on a remote device.
Here's the output.

$ show logical decw*

(LNM$PROCESS_TABLE)

(LNM$JOB_82DA3800)

(LNM$GROUP_000001)

(LNM$SYSTEM_TABLE)

"DECW$LOGINOUT" = "CDE$SYSTEM_DEFAULTS:[BIN]DECW$LOGINOUT"
"DECW$SECURITY" = "SYS$SHARE:DECW$SECURITY_VMS.EXE"
"DECW$SESSIONCOM" = "sys$manager:decw$startsm.com"
"DECW$SESSIONINIT" = "run sys$system:decw$wsinit"
"DECW$SESSIONMAIN" = "run sys$system:decw$session"

(LNM$SYSCLUSTER_TABLE)

(DECW$LOGICAL_NAMES)

"DECW$BITMAPS" = "SYS$SYSROOT:[DECW$INCLUDE.BITMAPS]"
"DECW$BOOK" = "SYS$SYSROOT:[DECW$BOOK]"
"DECW$CBI" = "SYS$SYSROOT:[SYSCBI.DECW$CBI]"
"DECW$CONSOLE_SELECTION" = "NONE"
"DECW$EXAMPLES" = "SYS$SYSROOT:[SYSHLP.EXAMPLES.DECW]"
"DECW$INCLUDE" = "SYS$SYSROOT:[DECW$INCLUDE]"
= "SYS$SYSROOT:[DECW$INCLUDE.EXTENSIONS]"
= "SYS$SYSROOT:[DECW$INCLUDE.ICE]"
= "SYS$SYSROOT:[DECW$INCLUDE.SM]"
"DECW$KEYMAP" = "DECW$SYSCOMMON:[SYS$KEYMAP.DECW.USER]"
= "DECW$SYSCOMMON:[SYS$KEYMAP.DECW.SYSTEM]"
"DECW$SNAPSHOT_SECURITY" = "TRUE"
"DECW$SYSCOMMON" = "SYS$SYSROOT"
"DECW$SYSTEM_DEFAULTS" = "SYS$SYSROOT:[DECW$DEFAULTS.USER]"
= "SYS$SYSROOT:[DECW$DEFAULTS.SYSTEM]"
= "SYS$LIBRARY:"
"DECW$USER_DEFAULTS" = "SYS$LOGIN:"
"DECW$USE_XM_VENDOR_SHELL" = "NOTES$MAIN"
"DECW$UTILS" = "SYS$SYSROOT:[SYSHLP.EXAMPLES.DECW.UTILS]"
"DECW$XLIBERRDB" = "SYS$MESSAGE:DECW$XLIBERRDB.DAT"
$

[Richard Whalen]

Those logicals show that the setup ran.

Yes, it needs to display on a remote device, so it depends upon how the user's session is set up.

Does the connection happen over Telnet, DECnet, SSH, LAT, or what?

[John Gillings]

Wade,
The "HP OpenVMS Version 8.3 Upgrade and Installation Manual" is highly detailed. See: http://h71000.www7.hp.com/doc/83final/ba322_90045/index.html

I recommend you read through it once. Then repeat with a highlighter to mark your path and go through the check lists (there are numerous options), then work your way through it with the system.

That should get you through to a working system.

[WADE S]

The user session is either by telnet or the remote serial console.

[Hoff]

Here's an intro to using ssh with a Mac OS X client, and that shows one approach and its set-up:

http://64.223.189.234/node/134

There's a section on DECwindows troubleshooting in the OpenVMS FAQ that's available here:

http://64.223.189.234/node/1

I'd suggest either the text for PDF version here. (HTML is nice to look at, but very difficult to search.)

In particular, you need have SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM configured to load the TCPIP transport. (This should be mentioned in both places.) This assumes you have TCP/IP Services or some other IP stack configured.

Once you have this startup set up (and have restarted DECwindows), you'll use the implicit DECW$DISPLAY set up for you by the ssh command shown, or that you have manually registered with the SET DISPLAY/TRANSPORT=TCPIP/NODE command.

Stephen Hoffman
HoffmanLabs LLC

[Volker Halle]

Hi,

welcome to the OpenVMS ITRC forum.

If your OpenVMS system does not have a graphics device, you need a X-server running on some other node and need to direct your X-display to that other node.

If you've logged in via TELNET or the remote console, you can set your display with:

$ SET DISP/CREATE/NODE=/trans=TCPIP

For testing, first run $ MC DECW$CLOCK or $ RUN DECW$EXAMPLES:ICO. ICO provides more detailled error messages, if the connection fails.

Volker.

[WADE S]

I appreciate the help you guys are giving me.
Please bare with me, but this is the 1st time I've ever seen an OpenVMS system, which is why I'm trying to get the Windows display.
I realize you may not have the time, but can someone provide me the commands syntax to modify the setup.com file to load the TCPIP transport.
Then I think I may be somewhere with what Halle just provided. One can hope anyway.

[Volker Halle]

Wade,

if your VMS system is the X-client, you don't need to have the TCPIP transport loaded in DECW$PRIVATE_SERVER_SETUP.COM (I did test that yesterday).

If you have a working X-server, consider to try the SET DISPL/CREATE/NODE=/TRANS=TCPIP and RUN DECW$EXAMPLES:ICO.

If it works - fine, otherwise tell us the error message. Try a TCPIP PING first to make sure, that you have a valid route for TCPIP traffic.

Volker.

[WADE S]

The Network doesn't appear to be setup.

ping: socket: network is down
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable
$

[Volker Halle · Accepted solution]

Wade,

if TCPIP has been configured, you can start it with:

$ @SYS$STARTUP:TCPIP$STARTUP

If it has not been configured, you need to configure it with:

$ @SYS$MANAGER:TCPIP$CONFIG

Volker.

[WADE S]

NOW THAT'S WHAT I NEEDED. UTILITIES.
I'm still working on getting the correct host name to get the service running.
Is there a way to display what utilities like that are available on the system.

[Hoff]

And if you do need load the TCPIP transport via the SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM file, read here:

http://64.223.189.234/node/134

and then read the comments in the server setup file, or (in the very unlikely event somebody's purged the comments) in the DECW$PRIVATE_SERVER_SETUP.TEMPLATE file that's located in the same directory.

There was a request outstanding to add TCPIP to the transport list automatically; to simply eliminate the need to manually configure the TCPIP transport underneath DECwindows, and to look for and to start it unless such was disabled.

And (as you may yet encounter weirdnesses), do remember the DECwindows troubleshooting section that's available in the OpenVMS FAQ, with the most recent version of the FAQ being located here:

http://64.223.189.234/node/1

[WADE S]

I'm trying to set this up to use DHCP. I still have something wrong. The 2 messages I'm concerned with are:

%TCPIP-S-STARTDONE, TCPIP$PWIP_DRIVER startup completed
%%%%%%%%%%% OPCOM 11-DEC-2007 19:28:24.70 %%%%%%%%%%%
Message from user SYSTEM on VMS
PWIPdriver, PWIPacp interface init failure, aborting PWIP ACP startup...

&

%%% TCPIP IVP: error - Local Host Not Found %%%
%SYSTEM-F-NOLOGNAM, no logical name match

[Volker Halle]

Hi,

don't make this too complicated. Use a fixed IP address, not DHCP.

Volker.

[WADE S]

Volker,
If I had my choice, I wouldn't run in a DHCP environment, but I don't have that luxury. My DHCP server shouldn't be the problem.
I notice when I run the utility and try to configure the interfaces, it doesn't give me any options to configure manually or using DHCP.

HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu

Hostname Details: Configured=Not Configured, Active=Not Configured

Configuration options:

[E] - Exit menu

Enter configuration option:

[Volker Halle]

If TCPIP$CONFIG.COM shows no LAN interfaces, then there are probably none.

Does $ SHOW DEVICE E show any ? Or MC LANCP SHOW DEV ?

Volker.

[WADE S]

No. These should be embedded on a BL860c bladeserver as far as I know, but I show none.

$ SHOW DEVICE E
%SYSTEM-W-NOSUCHDEV, no such device available
$ MC LANCP SHOW DEV
%LANCP-W-NODEVFND, No devices found
$

[WADE S]

Here's what I just a show device outputs.

$ show devices

Device Device
Name Status
VMS$DKA100: Mounted

Device Device
Name Status
OPA0: Online
FTA0: Offline
TTA0: Online
MOU0: Online
ASN0: Online
TNA0: Online

Device Device
Name Status
PKA0: Online
SRA0: Online
MPA0: Online
CMA0: Online
SEA0: Online
OHA0: Online
OHB0: Online
UCM0: Online
USB0: Online
HID0: Online
WSA0: Offline
PPP0: Online
PWIP0: Online
$

[Volker Halle]

There are NO LAN devices configured !

Whoever sent you this BL860c system did not bother to check, whether the LAN hardware is supported by the current version of OpenVMS I64 !

I suggest that you contact your hardware supplier and make sure, that you get a correctly configured system including the correct LAN interfaces and OpenVMS I64 version.

If you're running V8.3 and not V8.3-1H1, you may need an additional LAN patch kit to support the LAN interfaces built into this machine !

Volker.

[WADE S]

This BL860 came directly from HP engineering after they had it configured in manufacturing.
It's running version 8.3

[Volker Halle]

Please forward my regards to OpenVMS engineering, but you've obviously received a system, which does not work or you're missing instructions on how to get it to work.

Full Blade BL860c support is in V8.3-1H1, there were a couple of patches for V8.3 released in JUN-2007 for initial BL860c support. Do you have those patches installed ($ PRODUCT SHOW HISTORY) ?

Volker.

[WADE S]

If you're talking about Kit Name: HP-I64VMS-VMS83I_LAN-V0700--4.PCSI$COMPRESSED which i just went out & found, and am Now trying to get on the machine and install, it doesn't look like it.


$ PRODUCT SHOW HISTORY
------------------------------------ -----------
PRODUCT KIT TYPE
------------------------------------ -----------
HP I64VMS AVAIL_MAN_BASE V8.3 Full LP
HP I64VMS CDSA V2.2-272 Full LP
HP I64VMS DWMOTIF V1.6 Full LP
HP I64VMS DWMOTIF_SUPPORT V8.3 Full LP
HP I64VMS KERBEROS V3.0-106 Full LP
HP I64VMS OPENVMS V8.3 Platform
HP I64VMS SSL V1.3-284 Full LP
HP I64VMS TCPIP V5.6-9 Full LP
HP I64VMS TDC_RT V2.2-107 Full LP
HP I64VMS VMS V8.3 Oper System
HP I64VMS WBEMCIM V2.0-A051013F Full LP
------------------------------------ -----------

[Volker Halle]

Someone sent you this machine WITHOUT the necessary patches installed. It won't work on a BL860c - as you've seen.

You need to install a couple of patches on that machine first, BEFORE it is able to recognize the LAN adapters. You will have a hard time getting those patches to this machine WITHOUT a working LAN interface !!!

It may be easier to try to get a V8.3-1H1 DVD and re-install OpenVMS.

The list of patches you need can be found here:

http://h71000.www7.hp.com/openvms/cclass_support.html

Volker.