<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SYSMAN protocols in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450068#M66186</link>
    <description>Wim,&lt;BR /&gt;&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;Only a pitty that login.com is not executed in the process.&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;As per Bob's answer it should be clear that that would NOT ALWAYS be desirable.&lt;BR /&gt;&lt;BR /&gt;And something else: it probably would not do you much good.&lt;BR /&gt;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&amp;gt; prompt!&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Not so easy to set up an environment and do some 'inter-active' work, though.&lt;BR /&gt;&lt;BR /&gt;hope this helps some,&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;Seasonal greetings to all!&lt;BR /&gt;&lt;BR /&gt;jpe&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 24 Dec 2004 07:59:35 GMT</pubDate>
    <dc:creator>Jan van den Ende</dc:creator>
    <dc:date>2004-12-24T07:59:35Z</dc:date>
    <item>
      <title>SYSMAN protocols</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450060#M66178</link>
      <description>I did the following :&lt;BR /&gt;&lt;BR /&gt;$ set ho alp23&lt;BR /&gt;%SYSTEM-F-UNREACHABLE, remote node is not currently reachable&lt;BR /&gt;$ sysman&lt;BR /&gt;SYSMAN&amp;gt; set env/node=alp23&lt;BR /&gt;Remote Password:&lt;BR /&gt;%SYSMAN-I-ENV, current command environment:&lt;BR /&gt;        Individual nodes: ALP23&lt;BR /&gt;        At least one node is not in local cluster&lt;BR /&gt;        Username SYSMGR_WVW   will be used on nonlocal nodes&lt;BR /&gt;&lt;BR /&gt;SYSMAN&amp;gt; do show time&lt;BR /&gt;%SYSMAN-I-OUTPUT, command execution on node ALP23&lt;BR /&gt;%SYSMAN-I-NODERR, error returned from node ALP23&lt;BR /&gt;-SYSTEM-F-UNREACHABLE, remote node is not currently reachable&lt;BR /&gt;SYSMAN&amp;gt;  Exit&lt;BR /&gt;$ rl salpv1&lt;BR /&gt;[TNDRIVER: Proxy login for user "SYSMGR_WVW" in progress ...]&lt;BR /&gt;&lt;BR /&gt;&amp;gt;set ho alp23&lt;BR /&gt;%SYSTEM-F-UNREACHABLE, remote node is not currently reachable&lt;BR /&gt;&amp;gt;mc sysman&lt;BR /&gt;SYSMAN&amp;gt; set env/node=alp23&lt;BR /&gt;%SYSMAN-I-ENV, current command environment:&lt;BR /&gt;        Individual nodes: ALP23&lt;BR /&gt;        Username SYSMGR_WVW   will be used on nonlocal nodes&lt;BR /&gt;&lt;BR /&gt;SYSMAN&amp;gt; do show time&lt;BR /&gt;%SYSMAN-I-OUTPUT, command execution on node ALP23&lt;BR /&gt;  24-DEC-2004 09:14:02&lt;BR /&gt;SYSMAN&amp;gt;  Exit&lt;BR /&gt;&lt;BR /&gt;Is sysman using the cluster protocol to reach other cluster nodes ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Fri, 24 Dec 2004 03:16:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450060#M66178</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-12-24T03:16:42Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMAN protocols</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450061#M66179</link>
      <description>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?</description>
      <pubDate>Fri, 24 Dec 2004 03:46:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450061#M66179</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-12-24T03:46:18Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMAN protocols</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450062#M66180</link>
      <description>Wim,&lt;BR /&gt;&lt;BR /&gt;SYSMAN uses SCS in a local cluster (communicates with CSP = CLUSTER_SERVER process). For a remote node, it uses DECnet.&lt;BR /&gt;&lt;BR /&gt;Described in VAXcluster Principles book by Roy G. Davis, Chapter 8.5&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Fri, 24 Dec 2004 03:47:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450062#M66180</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2004-12-24T03:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMAN protocols</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450063#M66181</link>
      <description>Uwe,&lt;BR /&gt;&lt;BR /&gt;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).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Fri, 24 Dec 2004 03:49:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450063#M66181</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-12-24T03:49:22Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMAN protocols</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450064#M66182</link>
      <description>Ah, you said you have one big homogenous cluster, right?&lt;BR /&gt;&lt;BR /&gt;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!</description>
      <pubDate>Fri, 24 Dec 2004 03:56:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450064#M66182</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2004-12-24T03:56:20Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMAN protocols</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450065#M66183</link>
      <description>Uwe,&lt;BR /&gt;&lt;BR /&gt;Only a pitty that login.com is not executed in the process.&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Fri, 24 Dec 2004 03:58:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450065#M66183</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-12-24T03:58:23Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMAN protocols</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450066#M66184</link>
      <description>Wim,&lt;BR /&gt;&lt;BR /&gt;Actually, on more than a few occasions I have been very happy that LOGIN.COM was not executed.&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;If the LOGIN.COM had been executed, it might have been very difficult to actually login.&lt;BR /&gt;&lt;BR /&gt;- Bob Gezelter, &lt;A href="http://www.rlgsc.com" target="_blank"&gt;http://www.rlgsc.com&lt;/A&gt;</description>
      <pubDate>Fri, 24 Dec 2004 07:39:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450066#M66184</guid>
      <dc:creator>Robert Gezelter</dc:creator>
      <dc:date>2004-12-24T07:39:03Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMAN protocols</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450067#M66185</link>
      <description>Rob,&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;I use sysman in case of big problems only.&lt;BR /&gt;&lt;BR /&gt;set env/login/cluster would be an improvement. &lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Fri, 24 Dec 2004 07:42:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450067#M66185</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-12-24T07:42:22Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMAN protocols</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450068#M66186</link>
      <description>Wim,&lt;BR /&gt;&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;Only a pitty that login.com is not executed in the process.&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;As per Bob's answer it should be clear that that would NOT ALWAYS be desirable.&lt;BR /&gt;&lt;BR /&gt;And something else: it probably would not do you much good.&lt;BR /&gt;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&amp;gt; prompt!&lt;BR /&gt;&lt;BR /&gt;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.&lt;BR /&gt;&lt;BR /&gt;Not so easy to set up an environment and do some 'inter-active' work, though.&lt;BR /&gt;&lt;BR /&gt;hope this helps some,&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;Seasonal greetings to all!&lt;BR /&gt;&lt;BR /&gt;jpe&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 24 Dec 2004 07:59:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-protocols/m-p/3450068#M66186</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2004-12-24T07:59:35Z</dc:date>
    </item>
  </channel>
</rss>

