Operating System - OpenVMS
1753995 Members
7980 Online
108811 Solutions
New Discussion юеВ

Re: OpenVMS tape drive device Initialization

 
SOLVED
Go to solution
CO_5
Advisor

OpenVMS tape drive device Initialization

When a tape drive was pulled out accidentally, and when it was inserted back to the slot, the SHOW DEVICE could not detect anymore the device name. How to recover this device name ?

I checked there was IO Connect command under SYSMAN.

For example: the tape drive is MKA600:

Since there is a NOTE saying abt Caution when using IO Connect, I wnt to make sure it is safe to use this command below:
IO CONNECT MKA600:

May i also know the proper way to disconnect the drive ?

Thank you.

16 REPLIES 16
Karl Rohwedder
Honored Contributor

Re: OpenVMS tape drive device Initialization

I would try a SYSMAN IO AUTO /LOG to let SYSMAN rscan the buses.

Fro the help:
This command is for use on Alpha and I64 systems. It automatically
identifies and configures all hardware devices attached to a
system by connecting devices and loading their drivers.

On VAX systems, use the SYSGEN command AUTOCONFIGURE.

regards Kalle
Steven Schweda
Honored Contributor

Re: OpenVMS tape drive device Initialization

> [...] tape drive was pulled out [...]
> when it was inserted back to the slot [...]

Pulled out of what? In what is this slot?

Generally (assuming that you're on a non-VAX),
MCR SYSMAN IO AUTOCONFIGURE is pretty
harmless. You can add /SELECT = MKA600
if you wish to limit it to the one device.

MCR SYSMAN HELP IO
CO_5
Advisor

Re: OpenVMS tape drive device Initialization

hi,

Initially, i did the IO AUTOCONFIGURE ALL. The device name $mka600: is still not visible on the SHOW DEV.

Now, i performed the IO AUTOCONFIGURE/LOG
and followed by IO AUTOCONFIGURE/SELECT=$MKA600:

It still did not show any sign of it.

Not sure what happened ? The tape drive was unplugged from a primary machine and reconnected back to the machine.

Steven Schweda
Honored Contributor

Re: OpenVMS tape drive device Initialization

> [...] reconnected back [...]

Apparently not.

Was the SCSI ID changed?

It might help to know to what you're
connecting the tape drive, and how.
CO_5
Advisor

Re: OpenVMS tape drive device Initialization

There is a scsi cable connected to the machine and a power cable from the drive connected to the power line switch.

I am not sure how it was unplugged earlier by a personnel. But, it seems ok with the connection. There is no change in SCSI number.
Jan van den Ende
Honored Contributor

Re: OpenVMS tape drive device Initialization

CO,


The tape drive was unplugged from a primary machine and reconnected back to the machine.

"Primary machine"?
Is this perhaps a cluster config?
Are you issuing the tape commands from another node as the node which has the tape-unit?
If so, is TAPE_ALLOCLASS non-zero?

In general:
-what configuration?
-what version?

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
John Abbott_2
Esteemed Contributor

Re: OpenVMS tape drive device Initialization

Hi,

What's the drive, (cable) and host bus adaptor model nos ?

J.
Don't do what Donny Dont does
Steven Schweda
Honored Contributor

Re: OpenVMS tape drive device Initialization

It _still_ might help to know to what you're
connecting the tape drive, and how.

What else is on the SCSI bus?

SHOW DEVICE DKA
SHOW DEVICE MKA

Are any of those devices working?

Termination?

If you can shut the system down, SHOW DEVICE
at the SRM console might be interesting.
CO_5
Advisor

Re: OpenVMS tape drive device Initialization

Hi Guys,

thks for ur prompt replies.

The model of tape drive is SDLT 320.

It is connected to the primary node of a cluster(2 nodes) system.

i tried the IO autoconfigure/select=$mka600: from both nodes. It seems not much help either.

Btw, how do i know if TAPE_ALLOCLASS is non-zero?

Thks.