- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: %dcl-e-open
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
тАО10-07-2008 02:31 AM
тАО10-07-2008 02:31 AM
Re: %dcl-e-open
As Jess kindly pointed out UCX doesn't seem to like logical names so, as per his note, you need a two step process: -
>>>>>>>>>>>>>>>>>>>
To get some more details about the error, do
$ SHOW DEVICE/FULL BG_DIGI:
If, as would seem likely, the device physical name starts with BG then it is an IP socket. Depending on what TCP/IP stack you are using and what VMS version you are runnning (hint: tell us these things), you can get socket details with the command:
$ UCX SHOW DEVICE /FULL BGn
<<<<<<<<<<<<<<<<<<<<
Is it posible to see the DCL OPEN command that is triggering this error and a few lines above taht?
Cheers Richard Maher
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2008 02:41 AM
тАО10-07-2008 02:41 AM
Re: %dcl-e-open
i don├В┬┤t understand to mach this system but if you can help me thanks.
i send you a report what i do.
cheers Nuno
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2008 02:59 AM
тАО10-07-2008 02:59 AM
Re: %dcl-e-open
Volume Status: subject to mount verification, allocation inhibited because of
error on bitmap, write-back caching enabled.
There is an error in the bitmap and the allocation of space is inhibited, i.e. no new files, hence the WLK error.
You may try a
$ ANAL/Disk/Repair DKB0:
but you should make a backup before.
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2008 03:11 AM
тАО10-07-2008 03:11 AM
Re: %dcl-e-open
i do the command and i put the report.
cheers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2008 04:51 AM
тАО10-07-2008 04:51 AM
Re: %dcl-e-open
The disk is going bad.
Switch over to a new disk.
This may involve restoring a backup.
This may involve loss of data.
If you are lucky all you have to do is find a spare drive (push in a fresh brick) for example DKB100. Now $backup/image dbk0: dkb100:. Dismount DKB0, Mount DKB100, redefine logicals name like bg_digi to point to to new drive. Hint: $SHOW LOG */OUT=logicals.tmp ... $SEARCH logicals.tmp DKB
Over time you may want to put th enew drive in the old slot, or not.
Good luck!
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2008 05:16 AM
тАО10-07-2008 05:16 AM
Re: %dcl-e-open
%SEARCH-W-OPENIN, error opening SYS$COMMON:[SYSMGR]LOGICALS.TMP; as input
-RMS-E-FNF, file not found
%SEARCH-E-NOFILE, no file found
$ sho dev d
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DNFS0: Online 0
DNFS1: Mounted 0 litsg1:/ 0 1 0
DNFS2: Mounted 0 litsg2:/ 0 1 0
DNFS3: Mounted 0 litsg:/disk2 0 1 0
LITAX1$DKA0: Mounted 0 AXPVMSSYS 583060 425 1
LITAX1$DKA400: Online wrtlck 0
LITAX1$DKB0: Mounted 9 DISK2 5630778 2 1
LITAX1$DKB400: Mounted 0 DISK3 3510765 1 1
LITAX1$DKB500: Mounted 0 DISK4 4284234 1 1
LITAX1$DVA0: Online 0
$ backup/image dkb0: dkb400:
%BACKUP-F-MOUNTFOR, DKB400:[SYSMGR]*.*;* must be mounted /FOREIGN
$ show log */out=logicals.tmp
this weekend we had light lack and never more I connect with the server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2008 05:20 AM
тАО10-07-2008 05:20 AM
Re: %dcl-e-open
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2008 07:48 AM
тАО10-07-2008 07:48 AM
Re: %dcl-e-open
best regards
Nuno
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2008 07:50 AM
тАО10-07-2008 07:50 AM
Re: %dcl-e-open
"take your fingers from that keyboard and slowly step away from the computer"
Please go careful, and try to get some more experienced help.
The commands I suggested were rough directions, not verbatim.
Judging by the output posted you are out of your 'comfort zone' with this set up and risk creating further damage.
Please escalate the problem, internally or externally (vendor, hp, consultant, whatever.).
Good luck!
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-07-2008 07:52 AM
тАО10-07-2008 07:52 AM
Re: %dcl-e-open
It sure looked scary there for a moment!
Good to hear it worked out, and thanks for letting us know.
Cheers,
Hein.