HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: SYSMAN and SYSTEM-F-NOSUCHOBJ
Operating System - OpenVMS
1830231
Members
1826
Online
109999
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2004 04:26 PM
11-06-2004 04:26 PM
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?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-06-2004 05:28 PM
11-06-2004 05:28 PM
Solution
Mario,
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.
On the target node, make sure SMISERVER is started:
$ @SYS$SYSTEM:STARTUP SMISERVER
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.
On the target node, make sure SMISERVER is started:
$ @SYS$SYSTEM:STARTUP SMISERVER
A crucible of informative mistakes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2004 07:38 AM
11-07-2004 07:38 AM
Re: SYSMAN and SYSTEM-F-NOSUCHOBJ
Monitor the existance of the SMI process. One day you might need it ...
Wim
Wim
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2004 09:56 AM
11-07-2004 09:56 AM
Re: SYSMAN and SYSTEM-F-NOSUCHOBJ
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.
____________________
Purely Personal Opinion
Purely Personal Opinion
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP