- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- DOSD peculiarity
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО09-25-2008 10:59 PM
тАО09-25-2008 10:59 PM
Experimenting with DOSD on OpenVMS Alpha V8.3, I noticed something weird. Maybe someone can shed some light.
I changed the DUMPSTYLE system parameter to 13, specified DUMPFILE_DEVICE to be $1$DKD600 in MODPARAMS.DAT, created $1$DKD600:[SYS0.SYSEXE]SYSDUMP.DMP using SYSGEN, ran AUTOGEN, shutdown the node, specified DUMP_DEV to be DKD600 in the SRM, and booted the node.
After the boot, I checked the open files on SYS$SYSDEVICE and on $1$DKD600. To my surprise the file [SYS0.SYSEXE]SYSDUMP.DMP was listed as open on SYS$SYSDEVICE but not on $1$DKD600 (apart from INDEXF.SYS no files were open on DKD600). However, if I force a crash, the dump is written to $1$DKD600:[SYS0.SYSEXE]SYSDUMP.DMP.
Any idea why VMS lists the old dump file to be open on SYS$SYSDEVICE, and keeps quiet about the dumpfile on DKD600?
Thanks for any insight in this.
Kris (aka Qkcl)
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2008 11:07 PM
тАО09-25-2008 11:07 PM
Re: DOSD peculiarity
DKD600,
This is needed in case the system crashes before DKD600 is mounted; it may also be the reason that the dumpfile on the system disk is open at all times. Or it may indeed indicate a minor bug.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2008 12:58 AM
тАО09-26-2008 12:58 AM
Re: DOSD peculiarity
"For best results, include the MOUNT command in SYS$MANAGER:SYCONFIG.COM". May be mounted too late ?
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2008 12:59 AM
тАО09-26-2008 12:59 AM
Re: DOSD peculiarity
It would be a good idea to crash the system to see where the crash goes.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2008 01:04 AM
тАО09-26-2008 01:04 AM
Re: DOSD peculiarity
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2008 01:18 AM
тАО09-26-2008 01:18 AM
Re: DOSD peculiarity
did a forced crash (OPCCRASH) to test whether my DOSD file was
working, at the suggestion of one poster. Bingo! It works, despite the
fact that the file does not show as open when I did SHOW DEVICE/FILE.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2008 02:10 AM
тАО09-26-2008 02:10 AM
Re: DOSD peculiarity
> DKD600,
>
> This is needed in case the system crashes before DKD600 is mounted
I don't care. I really want the dump file off the system disk.
Re: Wim
> DKD500 may not be ODS-5 and not be part of a shadow set.
According to the System Manager's manual, the ODS-5 restriction is lifted.
> May be mounted too late ?
The mount happens in SYLOGICALS; and according to said manual:
"Although not a requirement, HP recommends that you mount the dump device during system startup. If the dump device is mounted, it can be accessed by CLUE and AUTOGEN and for the analysis of crash dumps. For best results, include the MOUNT command in SYS$MANAGER:SYCONFIG.COM."
So it isn't necessary to even mount the disk (but I will put the MOUNT in SYCONFIG and try again).
> It would be a good idea to crash the system to see where the crash goes.
As I said in my original post, I've crashed the system and the dump goes to DKD600. No problem there.
> did a forced crash (OPCCRASH) to test whether my DOSD file was
working, at the suggestion of one poster. Bingo! It works, despite the
fact that the file does not show as open when I did SHOW DEVICE/FILE.
That's part of my question. Why doesn't it show as an open file, and the dump file in SYS$SYSTEM does (although not used anymore, I guess).
Regards,
Kris (aka Qkcl)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2008 02:29 AM
тАО09-26-2008 02:29 AM
Re: DOSD peculiarity
may be this is a bug and they are keeping the wrong file open ? But then the protection is gone too ...
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2008 02:34 AM
тАО09-26-2008 02:34 AM
Re: DOSD peculiarity
fwiw
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2008 03:20 AM
тАО09-26-2008 03:20 AM
Re: DOSD peculiarity
Wim