<?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 and SYSTEM-F-NOSUCHOBJ in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/sysman-and-system-f-nosuchobj/m-p/3416634#M65484</link>
    <description>Monitor the existance of the SMI process. One day you might need it ...&lt;BR /&gt;&lt;BR /&gt;Wim</description>
    <pubDate>Sun, 07 Nov 2004 15:38:22 GMT</pubDate>
    <dc:creator>Wim Van den Wyngaert</dc:creator>
    <dc:date>2004-11-07T15:38:22Z</dc:date>
    <item>
      <title>SYSMAN and SYSTEM-F-NOSUCHOBJ</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-and-system-f-nosuchobj/m-p/3416632#M65482</link>
      <description>What does it mean when I set my environment in SYSMAN for several nodes in my VMS environment and ultimately receive the "-SYSTEM-F-NOSUCHOBJ, network object is unknown at remote node"?  What object is unknown?</description>
      <pubDate>Sun, 07 Nov 2004 00:26:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-and-system-f-nosuchobj/m-p/3416632#M65482</guid>
      <dc:creator>Mario Abruzzi</dc:creator>
      <dc:date>2004-11-07T00:26:40Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMAN and SYSTEM-F-NOSUCHOBJ</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-and-system-f-nosuchobj/m-p/3416633#M65483</link>
      <description>Mario,&lt;BR /&gt;&lt;BR /&gt;  SYSMAN uses the SMISERVER on the remote node. The SMISERVER process creates a DECnet object, also called SMISERVER. If the object is not present or disabled, SYSMAN will report NOSUCHOBJ.&lt;BR /&gt;&lt;BR /&gt;  On the target node, make sure SMISERVER is started:&lt;BR /&gt;&lt;BR /&gt;$ @SYS$SYSTEM:STARTUP SMISERVER</description>
      <pubDate>Sun, 07 Nov 2004 01:28:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-and-system-f-nosuchobj/m-p/3416633#M65483</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2004-11-07T01:28:13Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMAN and SYSTEM-F-NOSUCHOBJ</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-and-system-f-nosuchobj/m-p/3416634#M65484</link>
      <description>Monitor the existance of the SMI process. One day you might need it ...&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Sun, 07 Nov 2004 15:38:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-and-system-f-nosuchobj/m-p/3416634#M65484</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2004-11-07T15:38:22Z</dc:date>
    </item>
    <item>
      <title>Re: SYSMAN and SYSTEM-F-NOSUCHOBJ</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/sysman-and-system-f-nosuchobj/m-p/3416635#M65485</link>
      <description>note SMISERVER is started by default on cluster nodes but not started by default on standalode nodes. I think its very handy and should be started on all nodes.</description>
      <pubDate>Sun, 07 Nov 2004 17:56:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/sysman-and-system-f-nosuchobj/m-p/3416635#M65485</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2004-11-07T17:56:40Z</dc:date>
    </item>
  </channel>
</rss>

