My QDSK EXEC contains logic to get quite some information from the CMS header records when a disk cannot be accessed as it is empty or has only FM0 files (the information you can get includes things like when was the disk formatted, last accessed in R/W). It uses RxDASD or DDR PRINT to read header records from the minidisk (so no need for modern pipes, ad no DDR to copy the whole -maybe large- minidisk).
Ask and you it'll be sent (as I did to Ian). -- Kris Buelens, IBM Belgium, VM customer support 2007/9/18, David Kreuter <[EMAIL PROTECTED]>: > > DDRing from r/o source disk to r/w tdisk will show all stats and all > files > > ________________________________ > > From: The IBM z/VM Operating System on behalf of Stracka, James (GTI) > Sent: Tue 9/18/2007 3:56 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: [IBMVM] ACCESS empty RR disk fails > > > > The disk can have files but if they are all MODE 0, you do not get to > ACCESS it either. > > -----Original Message----- > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On > Behalf Of David Kreuter > Sent: Tuesday, September 18, 2007 3:50 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: ACCESS empty RR disk fails > > > Ian: You can roll your own/fend for yourself. Start by using DDR. Say > your mdisk is at vaddr 1B0. DDR INPUT 1B0 DASD TYPE 0 0 3 > > cyl 0 head 0 record 3 has the label information. You can decode the > info there and get the numbers you need. > > Or if its a small sized disk, and you have sufficient tdisk, define a > tdisk of the same size, ddr the r/o over to the r/w tdisk and et voila > you can access and then see your stats. This would even work by creating > a 1 cylinder tdisk (and then just copy cyl 0), but ... it's weird and > somewhat dangerous .... > > David > > ________________________________ > > From: The IBM z/VM Operating System on behalf of Ian S. Worthington > Sent: Tue 9/18/2007 12:20 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: [IBMVM] ACCESS empty RR disk fails > > > > I've come across this a few times but never understood *why* accessing > an empty disk I've linked RR should fail (rc=28, iirc). Any good reason > for that? > > And any way to *prevent* it from failing? (I'm not after the files I'm > after the disk stats I can only get when the disk is accessed.) > > ian > ... >
