Richard,
Here's what I used to use, from a svm that ran this (and other things)
every 15 minutes. The range of "normal" DASD device addresses are
specified, and it proceeds to vary all others offline.
/* DASDOFF EXEC
Vary all DASD that VM is not using offline to avoid conflicts with
z/OS activities.
*/
VM_DASD_addrs = '1000-10FF 1100-11FF 1910-1917'
'PIPE(name DASDOFF endchar ?)|',
'CP Q DASD ALL |',
'SPLIT , |',
'STRIP |',
'PICK W3 /== /OFFLINE/ |',
'PICK W3 /== /SUBCHOFF/ |',
'L: NOT LOOKUP 6.4 6.4 |',
'CONS |',
'SPECS /VARY OFF/ 1 6.4 NW |',
'CP |',
'CONS',
'?',
'CP Q' VM_DASD_addrs '|',
'SPLIT , |',
'STRIP |',
'L:'
Best regards,
Mark
"Schuh, Richard"
<[EMAIL PROTECTED]>
Sent by: The IBM To
z/VM Operating IBMVM@LISTSERV.UARK.EDU
System cc
<[EMAIL PROTECTED]
ARK.EDU> Subject
Offline Devices
12/24/2007 12:26
PM
Please respond to
The IBM z/VM
Operating System
<[EMAIL PROTECTED]
ARK.EDU>
Recently, we have had some problems with a ficon card. The path was varied
off from all devices and the chpid varied offline. The chpid was then taken
offline at the HSM and the part replaced. When the chpid was brought back
online at the HSM, the ensuing device reconfiguration interrupt apparently
caused all 4096 devices to be brought online. Unfortunately, only 365 of
the devices were online when the hardware activity started. The remaining
devices are in the Devices_offline list in the SYSTEM CONFIG file and are
not supposed to be online to VM. In this particular case, only the one path
out of four was affected by the hardware problem.
I cannot put the devices in an ignore list because it is sometimes
necessary to make one of them available to VM. From the description, it
does not appear that making them not_sensed would help. In fact, it would
probably make the occasional need to make a device available more
complicated. Is there any way to have the devices stay offline in a
situation like this?
Regards,
Richard Schuh
