Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!UAFSYSB.UARK.EDU!DMARTIN
From: DMARTIN@UAFSYSB.UARK.EDU ("Daniel P. Martin")
Newsgroups: comp.lang.asm370
Subject: Re: Deep down in CP...
Message-ID: <9002061534.AA06034@lilac.berkeley.edu>
Date: 6 Feb 90 15:19:05 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List <ASM370%UCF1VM.bitnet@lilac.berkeley.edu>
Distribution: inet
Organization: The Internet
Lines: 20

>2.  doing I/O to ALL DASD

Zapping control blocks is probably an unnecessarily dangerous approach
(not that it isn't fun to do from time to time... :-) ).  If you're on
a reasonably current VM R5 system, or on VM 6 at any working level, take
a look at diagnose code x'E4', which allows you to perform various
minidisk extent management operations including definition of full-volume
minidisk overlays for anything that's ATTACHed to system.  As I don't
have access to an XA system or documentation, I can't say if this is
supported under XA as well as /370 VM.

Nuking the VDEVBLOK will work too, but with the DIAG interface available,
it's an "overkill" solution -- sort of like swatting flies with Buicks.

Regards,

-dan.

Daniel P. Martin -- Systems Programmer III
University of Arkansas Main Campus - Fayetteville