Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

tapesys V6.2.3, on alpha 8.2

 
Highlighted
Bjay
Advisor

tapesys V6.2.3, on alpha 8.2

installation was successful
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
4 REPLIES 4
EdgarZamora_1
Respected Contributor

Re: tapesys V6.2.3, on alpha 8.2

After installation usually the next step is configuration. Is this a new install? Have you "setup" tapesys? I'm by no means a tapesys expert but I played with it a little when I was working for another company. IIRC, on a new install your setup.par file will be empty. You probably need to "customize and configure" before you can start up. This is pretty much SOP.
Bjay
Advisor

Re: tapesys V6.2.3, on alpha 8.2

I did populated setup.par actually it is same from other system which is working fine I edit it to reflect for this node , indeed it is a new installation and never worked b4

Steven Schweda
Honored Contributor

Re: tapesys V6.2.3, on alpha 8.2

> [...] I edit it [...]

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?
Robert Atkinson
Respected Contributor

Re: tapesys V6.2.3, on alpha 8.2

It sounds like you have your 'PRI' or 'SEC' set to an unknown node.

Can you confirm node names and send in SETUP.PAR.

Rob.