- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: tapesys V6.2.3, on alpha 8.2
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
тАО12-24-2008 03:49 AM
тАО12-24-2008 03:49 AM
tapesys V6.2.3, on alpha 8.2
1. @tapesys_sytem:startup ok
2. sho system /proc=tap*
$ sho system /pro=tap*
OpenVMS V8.2 on node JASPER 24-DEC-2008 12:06:16.97 Uptime 0 02:04:09
Pid Process Name State Pri I/O CPU Page flts Pages
204000A5 TAPESTART COM 0 905 0 00:00:06.01 2424 130
$ sho system /pro=tap*
OpenVMS V8.2 on node JASPER 24-DEC-2008 12:06:58.04 Uptime 0 02:04:50
Pid Process Name State Pri I/O CPU Page flts Pages
204000A5 TAPESTART COM 0 2486 0 00:00:18.06 5636 88
204000A6 TAPMGRDB LEF 10 737 0 00:00:04.91 2746 334
204000A7 TAPMGRRQ LEF 8 773 0 00:00:05.62 3413 105
but during the startup process I get the final message as
%%%%%%%%%%% OPCOM 24-DEC-2008 12:07:14.63 %%%%%%%%%%%
Message from user TAPESYS on JASPER
TAPMGRDB, %TAPMGR-F-ALROPNERR, failed to open alias reel file !AD
$
%%%%%%%%%%% OPCOM 24-DEC-2008 12:07:15.13 %%%%%%%%%%%
Message from user TAPESYS on JASPER
TAPMGRDB, -RMS-F-DUP, duplicate key detected (DUP not set)
$
%%%%%%%%%%% OPCOM 24-DEC-2008 12:07:17.58 %%%%%%%%%%%
Message from user TAPESYS on JASPER
TAPMGRDB, TAPMGRDB has stopped - %TAPMGR-F-ALROPNERR, failed to open alias reel
file !AD
- restart TAPESYS
Thank you
Bjay
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-24-2008 05:26 AM
тАО12-24-2008 05:26 AM
Re: tapesys V6.2.3, on alpha 8.2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-24-2008 09:33 PM
тАО12-24-2008 09:33 PM
Re: tapesys V6.2.3, on alpha 8.2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-25-2008 10:02 AM
тАО12-25-2008 10:02 AM
Re: tapesys V6.2.3, on alpha 8.2
Edit how? -RMS-F-DUP sounds like an indexed
file, and if you edited it with a normal text
editor, you probably damaged it. You might
compare DIRE /FULL output from a working
system and your new system for the file you
edited.
I know nothing about TAPESYS, but if it uses
indexed files, it might include some tools to
use to create and change them.
Is it time to read the documentation yet?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-05-2009 03:51 AM
тАО01-05-2009 03:51 AM
Re: tapesys V6.2.3, on alpha 8.2
Can you confirm node names and send in SETUP.PAR.
Rob.