- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Info on FILCNTNONZ bugcheck?
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
тАО04-17-2005 07:29 AM
тАО04-17-2005 07:29 AM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-17-2005 02:47 PM
тАО04-17-2005 02:47 PM
Re: Info on FILCNTNONZ bugcheck?
Google gives a hit on an ECO: VMS721H1_SYS-V0600
CrashDump Summary
-----------------
Bugcheck Type: FILCNTNONZ, Open file count nonzero
after process rundown
Current Image:
Failing PC: FFFFFFFF.D269A360
PROCESS_MANAGEMENT+3C360
Failing PS: 18000000.00000000
Module: PROCESS_MANAGEMENT (Link Date/Time:
18-OCT-2000 07:01:30.44)
Offset: 0003C360
Images Affected:[SYS$LDR]IO_ROUTINES.EXE
[SYS$LDR]IO_ROUTINES_MON.EXE
Case CFS.103399 ?
hth,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-17-2005 06:51 PM
тАО04-17-2005 06:51 PM
Re: Info on FILCNTNONZ bugcheck?
there are a couple of possible reasons for this crash. It can either happen during image (in IMAGE_MANAGEMENT.EXE) or process (in PROCESS_MANAGEMENT.EXE) rundown.
You'll find the $DASSGN system service failure status in R0 and the channel control block address in R5 or R3:
$ ANAL/CRASH sys$system:sysdump.dmp
SDA> EVA/COND R0
SDA> READ SYSDEF
SDA> FORMAT/TYPE=ccb @R5 - or @R3
SDA> SHOW DEV/ADDR=@@R5 - or @@R3 - should show disk
There are a couple of patches, which refer to a solution for this kind of problem. The most promising ones would be those referencing CFS.103399 (as referred to by Hein). For V7.2-2 it's VMS722_SYS-V0200, there does not seem to be a patch for this problem for V7.1-2.
If you could provide the CLUE files from CLUE$COLLECT:CLUE$node_ddmmyy_hhmm.LIS (at least the CLUE CRASH output from SDA> CLUE CRASH) as an attachment to your next reply, I can further confirm this.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-18-2005 01:42 PM
тАО04-18-2005 01:42 PM
Re: Info on FILCNTNONZ bugcheck?
I appreciate any tips for troubleshooting or analysis of this problem. Let me know if you desire further info. Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-18-2005 06:37 PM
тАО04-18-2005 06:37 PM
Solutionthis IS the problem referred to by Hein (CFS.103399).
Unfortunatley, there never have been patches released for the NOW UNSUPPROTED versions V7.1-2 or V7.2-1 to fix this longstanding problem. Those versions were already UNSUPPORTED when the solution had been coded.
Use the SDA commands from my previous post to confirm that R3 is indeed pointing to the CCB and SDA> SHOW DEV/ADDR=@@R3 will show you the device.
If you have a software service contract with HP, you can try to contact them and ask for the solution (a new SYS patch or at least new exec images for V7.1-2 and V7.2-1), but you'll certainly be charged for this (if HP accepts this call at all) ...
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-19-2005 06:52 AM
тАО04-19-2005 06:52 AM
Re: Info on FILCNTNONZ bugcheck?
I've enjoyed "ask the wizard" and this forum is really helpful. I'll close this thread as resolution is contingent upon when the upgrade happens. Thanks all!
Tony