Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Subject: dir accessing error

Original Message
Name: ajmal
Date: April 20, 2003 at 22:02:28 Pacific
Subject: dir accessing error
OS: vms
CPU/Ram: 3400
Comment:
Basically when i booted vax from console
the systen will halt at this line..

%TMSCPLOAD-I-LOADINGTMSCP,LOADING THE TMSCP TAPE SERVER
so what i did,i use following commands at
SYSBOOT prompt.
SYSBOOT> SET TMSCP_LOAD 0
SET VAXCLUSTER 0
continue
now the system will not halt at any point.
and i got $ prompt.
when i use this command
show device d:
the system show only one physical device
$2$DIA1
but the data is store in following logical devices.
D$6:[sabir]
D$9:[sabir]
and the system will not show both devices.

now plz tell what command i should use to
access the logical devices

waiting for ur reply..
thaks
ajmal


Report Offensive Message For Removal

Response Number 1
Name: ME
Date: April 21, 2003 at 18:41:36 Pacific
Subject: dir accessing error
Reply: (edit)
First I must say that I do not have experience with a VMS cluster.

But what I understand that happens is that :
- you have a VAX/VMS cluster
- one node hangs when you boot it
- therefore you boot it as a standalone machine. But the result of this is, that some disks are not mounted or even visible.
My conclusion is that the two user disks are physically connected to the remaining part of the cluster. There is no way you can see them on the standalone machine, unless you physically connect them (this doesn't sound like a good idea). What you should do, is try to find out why the machine hangs in the normal boot.

- what happens when you boot with :
SYSBOOT> SET TMSCP_LOAD 0
SYSBOOT> SET VAXCLUSTER 1 (or 2, depending on what it used to be)
This will not load the software that makes the tapeunit available in the cluster, but would add the machine to the cluster.

- what happens when you boot minimal with :
SYSBOOT> set startup_p1 "MIN"

I would also advice to bring your question to another forum. With only one question and answer a day, it may take a loooong time before your VAX is up again. I would advice either the newsgroup comp.os.vms :
http://groups.google.com/groups?hl=en&group=comp.os.vms
or the forum at openvms.org :
http://www.openvms.org/phorum/list.php?f=1


Report Offensive Follow Up For Removal



Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: dir accessing error 

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software



Version Tracker Pro
Keep your software current and secure, effortlessly

Click Here for a Free Scan

Driver Agent
Automatically find the latest drivers for your computer.
Click Here for a Free Scan



The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC