- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Sysdump.dmp
Operating System - OpenVMS
1753902
Members
10046
Online
108810
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
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
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
05-10-2004 06:46 AM
05-10-2004 06:46 AM
Re: Sysdump.dmp
Uwe:
I think that this _IS_ the whole error message: the rest of the info about what is not allowed to be seen is not displayed BECAUSE it is not allowed to be seen!
UareTerminated:
You are accessing your 'remote' system with the default network access.
If you have set up proxy access, then you are using the defined proxy user (usually the same user as on the accessing system), but if not, then at the remote node you are the default network user (and obviously that is NOT blocked at your site!).
If you DO want the info to be supplied by the remote node, then use
$
OTOH, I understand this IS a cluster?
Then the info is available locally, and you can simply
$ dir sys$sysdevice:[sys*.sysexe]sysdump.dmp
If you heva multiple system disks (which I don't suspect) then replace 'sys$sysdevice' with the name(s) of the system disk(s) as seen from your local system.
Alternatively,
$ MCR SYSMAN
set environment/cluster
do dir sys$sysdevice:[sys*.sysexe]sysdump.dmp
But then, for every system booting off the same disk, you get the info over again.
If none of this helps, you make me very curious of your configuration!
Success,
Jan
I think that this _IS_ the whole error message: the rest of the info about what is not allowed to be seen is not displayed BECAUSE it is not allowed to be seen!
UareTerminated:
You are accessing your 'remote' system with the default network access.
If you have set up proxy access, then you are using the defined proxy user (usually the same user as on the accessing system), but if not, then at the remote node you are the default network user (and obviously that is NOT blocked at your site!).
If you DO want the info to be supplied by the remote node, then use
$
OTOH, I understand this IS a cluster?
Then the info is available locally, and you can simply
$ dir sys$sysdevice:[sys*.sysexe]sysdump.dmp
If you heva multiple system disks (which I don't suspect) then replace 'sys$sysdevice' with the name(s) of the system disk(s) as seen from your local system.
Alternatively,
$ MCR SYSMAN
set environment/cluster
do dir sys$sysdevice:[sys*.sysexe]sysdump.dmp
But then, for every system booting off the same disk, you get the info over again.
If none of this helps, you make me very curious of your configuration!
Success,
Jan
Don't rust yours pelled jacker to fine doll missed aches.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-10-2004 04:46 PM
05-10-2004 04:46 PM
Re: Sysdump.dmp
Well, i don't think that OpenVMS is all that difficult to manage compared to some other OS. Its relatively very easy to manage VMS systems :-). I know that some times it tends to get difficult finding help if you are looking for anything. But thats why we are all here, to help out each other.
I have couple of suggestions for you. I hope they help you in managing your systems better and also finding resources that are needed to do so
1. Make it a habit to look for any info
at the DSNLink (at the ITS tool). If you
don't have DSNLink on your systems, you
can always look for "How to ...." at
http://askq.compaq.com. I find this very
usefull.
2. Since you mention that you have a 7 node
cluster, i would suggest that you put up
a seperate disk as a dump device. It will
certainly help you in some cases.
3. Many of our friends have already
mentioned on how to set up the dumps.
Let us know if you have any specific questions and we would be glad to clarify
regards
Mobeen
I have couple of suggestions for you. I hope they help you in managing your systems better and also finding resources that are needed to do so
1. Make it a habit to look for any info
at the DSNLink (at the ITS tool). If you
don't have DSNLink on your systems, you
can always look for "How to ...." at
http://askq.compaq.com. I find this very
usefull.
2. Since you mention that you have a 7 node
cluster, i would suggest that you put up
a seperate disk as a dump device. It will
certainly help you in some cases.
3. Many of our friends have already
mentioned on how to set up the dumps.
Let us know if you have any specific questions and we would be glad to clarify
regards
Mobeen
- « Previous
-
- 1
- 2
- Next »
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP