- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - OpenVMS
- >
- Crashing symbiont
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
- 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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-04-2009 03:36 PM
07-04-2009 03:36 PM
I'm trying to move a custom applicaton from an older to a newer system. The old system was 7.1-2 and it still runs. The "new" system is openvms 7.2-1. According to the applicaton developer this version should be ok. This was about the last version when they stopped development.
What happens is that I have a print queue with a custom symbion attached that is producing a crash dump and stopping the queue. This crash dump cannot be read by the analyze utility. The dump utility also does not show anything exiting about the dmp file. From what I understand, the queue prints to NL: and the symbiont it supposed to take the print item number and send it to the applicaton.
I have compared the running system with the new system and don't see the difference. Are there some other utilities that I could try to find out what goes wrong?
Thanks,
Markus
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-05-2009 03:12 AM
07-05-2009 03:12 AM
Solutionplease provide a little bit more information...
With which command did you try to analyze the process dump ? What is the exact error message ? Please provide the information as an attached .TXT file.
Try $ RUN/DEBUG symbiontname. If the DBG> prompt show up, enter EXIT. If not, post the error messages.
In general, describing what you want to do is o.k. when done in general words, but for failing commands and error messages, you should supply them EXACTLY character by character !
Volker.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-05-2009 02:29 PM
07-05-2009 02:29 PM
Re: Crashing symbiont
Many thanks for your reply. It's understood.
The only think I have done so far is to use
$ana/crash nw2smb.dmp
which results in
%SDA-E-NOTALPHADUMP, dump file does not contain an OpenVMS Alpha system dump
The other thing was the dump utility, which shows hex/text of the file, but I could not make out anything useful.
SYSTEM@NW2>anal/image/header nw2smb.exe
does not show me anything useful either.
SYSTEM@NW2>run /debug nw2smb.exe
OpenVMS Alpha Debug64 Version V7.2-01R
%DEBUG-I-INITIAL, Language: FORTRAN, Module: NW2SMB
DBG>
What can I do now?
I have attached a text file describing the problem and showing the info I have.
Maybe I'm missing some library or logical which causes the symbiont to fail. It is still running on the old machine, but I cannot find the difference to the current setup.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-05-2009 04:31 PM
07-05-2009 04:31 PM
Re: Crashing symbiont
Is the file NW2SMB.TLB in sys$library: ?
You have an access violation, which means you are trying to access an area of memory you are not allowed to. Can be caused by many things, but root cause is often something else entirely, which (down to bad programming not checking for an error!)subsequently results in an attempt to access memory location zero.
Have fun,
PJ
Peejay
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If it can't be done with a VT220, who needs it?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-05-2009 11:23 PM
07-05-2009 11:23 PM
Re: Crashing symbiont
The only think I have done so far is to use
$ana/crash nw2smb.dmp
which results in
%SDA-E-NOTALPHADUMP, dump file does not contain an OpenVMS Alpha system dump
<<<
Try ANALYZE/PROCESS_DUMP. For that version of VMS SDA could not read/understand process dumps.
>>>
SYSTEM@NW2>run /debug nw2smb.exe
OpenVMS Alpha Debug64 Version V7.2-01R
%DEBUG-I-INITIAL, Language: FORTRAN, Module: NW2SMB
DBG>
<<<
Which means, you can activate the image and there are no missing shareables or version mismatches when activating the image.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-06-2009 12:45 AM
07-06-2009 12:45 AM
Re: Crashing symbiont
It is a complex system. Everything else seems to work fine, except the symbionts. Could it be the difference between ovms 712 and 721? Perhaps something like a "trace" utility that could be used to track the applicaton while its running might show the point where it fails. I tried $run/debug NW2SMBSRV.exe and then typed "SET TRACE/BRANCH/CALL". I was guessing something might show up when the error occurs, but it does not show anyhting. I guess I don't know how to use it or attach to the symbiont.
thanks,
Markus
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-06-2009 08:20 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
07-07-2009 02:23 AM
07-07-2009 02:23 AM
Re: Crashing symbiont
Thanks,
Markus
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP