CHECKIN LIBV in 3494 robot - optimising
1997-04-25 14:21:12
Subject: |
CHECKIN LIBV in 3494 robot - optimising |
From: |
"BELL, CRAIG" <rcbell AT VNET.IBM DOT COM> |
Date: |
Fri, 25 Apr 1997 11:21:12 PDT |
Oh, and one more thing about dsmlabel, since that came up in this thread:
You can use more than one drive with dsmlabel- you don't have to start up
several dsmlabel processes each with their own drive, ie.
dsmlabel -library=/dev/lmcp0 -drive=/dev/rmt1 -drive=/dev/rmt2 -keep -search
BUT- do NOT use a drive that is currently defined to the adsm server! You
MUST delete any drive from the server & lower the mountlimit of that drive's
devclass before using it with dsmlabel (or you could halt the server). There
has been actual data loss by not following this instruction, from a
combination of contention between the server and dsmlabel for the drive, and
a bug in the dsmlabel code (which has since been fixed- see APAR IC17064).
Craig Bell
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- CHECKIN LIBV in 3494 robot - optimising, Sheelagh Treweek
- Re: CHECKIN LIBV in 3494 robot - optimising, Pittson, Timothy ,HiServ/NA
- Re: Re[2]: CHECKIN LIBV in 3494 robot - optimising, Thomas A. La Porte
- Re: CHECKIN LIBV in 3494 robot - optimising, Dwight E. Cook
- Re[2]: CHECKIN LIBV in 3494 robot - optimising, ALLEN BARTH
- CHECKIN LIBV in 3494 robot - optimising, BELL, CRAIG
- CHECKIN LIBV in 3494 robot - optimising,
BELL, CRAIG <=
|
|
|