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: 

SYSMAN protocols

 
SOLVED
Go to solution
Wim Van den Wyngaert
Honored Contributor

SYSMAN protocols

I did the following :

$ set ho alp23
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable
$ sysman
SYSMAN> set env/node=alp23
Remote Password:
%SYSMAN-I-ENV, current command environment:
Individual nodes: ALP23
At least one node is not in local cluster
Username SYSMGR_WVW will be used on nonlocal nodes

SYSMAN> do show time
%SYSMAN-I-OUTPUT, command execution on node ALP23
%SYSMAN-I-NODERR, error returned from node ALP23
-SYSTEM-F-UNREACHABLE, remote node is not currently reachable
SYSMAN> Exit
$ rl salpv1
[TNDRIVER: Proxy login for user "SYSMGR_WVW" in progress ...]

>set ho alp23
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable
>mc sysman
SYSMAN> set env/node=alp23
%SYSMAN-I-ENV, current command environment:
Individual nodes: ALP23
Username SYSMGR_WVW will be used on nonlocal nodes

SYSMAN> do show time
%SYSMAN-I-OUTPUT, command execution on node ALP23
24-DEC-2004 09:14:02
SYSMAN> Exit

Is sysman using the cluster protocol to reach other cluster nodes ?

Wim
Wim
8 REPLIES
Uwe Zessin
Honored Contributor
Solution

Re: SYSMAN protocols

Yes. By the way: have you noticed that you don't get asked for a password as long as you environment is limited to the cluster?
.
Volker Halle
Honored Contributor

Re: SYSMAN protocols

Wim,

SYSMAN uses SCS in a local cluster (communicates with CSP = CLUSTER_SERVER process). For a remote node, it uses DECnet.

Described in VAXcluster Principles book by Roy G. Davis, Chapter 8.5

Volker.
Wim Van den Wyngaert
Honored Contributor

Re: SYSMAN protocols

Uwe,

Yes I did. But I'm an infrequent sysman user. I have another tool that creates "normal" processes that have gone thru a login. But it needs decnet or IP which I don't have towards alp23 (thank you network team).

Wim
Wim
Uwe Zessin
Honored Contributor

Re: SYSMAN protocols

Ah, you said you have one big homogenous cluster, right?

I used to manage a number of small clusters scattered around Germany. Fortunately, all were reachable via DECnet and we made quite some efford to have the clusters look identical. SYSMAN (which appeared in VAX/VMS V5.0) certainly helped managing all the systems - a big thank you to VMS engineering!
.
Wim Van den Wyngaert
Honored Contributor

Re: SYSMAN protocols

Uwe,

Only a pitty that login.com is not executed in the process.

Wim
Wim
Robert Gezelter
Honored Contributor

Re: SYSMAN protocols

Wim,

Actually, on more than a few occasions I have been very happy that LOGIN.COM was not executed.

When dealing with problems at client sites, the SYSMAN connection has often been the only way into a remote machine when DECnet and IP did not (or had not) yet started. SYSMAN allowed me to get into the system and fix the problem.

If the LOGIN.COM had been executed, it might have been very difficult to actually login.

- Bob Gezelter, http://www.rlgsc.com
Wim Van den Wyngaert
Honored Contributor

Re: SYSMAN protocols

Rob,

That's why I use my own tool. I can type commands in the way I am used too. And the process stays alive and can receive multiple commands.

I use sysman in case of big problems only.

set env/login/cluster would be an improvement.

Wim
Wim
Jan van den Ende
Honored Contributor

Re: SYSMAN protocols

Wim,


Only a pitty that login.com is not executed in the process.


As per Bob's answer it should be clear that that would NOT ALWAYS be desirable.

And something else: it probably would not do you much good.
Each separate SYSMAN command stands on its own, and any symbol setting or logical name definitions executed in, eg, LOGIN.COM are GONE the moment you get back to the SYSMAN> prompt!

The way around that is to have your sequence of commands (say, DEFINE SYS$LOGIN ; @LOGIN.COM ; @work-to-do ) in one file, and define SYSMANINI to point to that file.

Not so easy to set up an environment and do some 'inter-active' work, though.

hope this helps some,

Proost.

Have one on me.

Seasonal greetings to all!

jpe

Don't rust yours pelled jacker to fine doll missed aches.