On Friday, 01/18/2008 at 10:49 EST, "Said, Nick" <[EMAIL PROTECTED]>
wrote:
> I had the same problem at my shop a few months ago - new z/VM 5.3
> implementation backing up with FDR on z/OS. The problem is a missing
> dummy VTOC on cylinder 0 that FDR depends on - S213 abend if it doesn't
> find it. You must format cylinder 0 using CPFMTXA. Just make sure you
> run an ALLOCATE after the format to redefine all your CP areas.
The VTOC is located on cyl 0. The record number is a 5-byte number
starting at +0x0B in the label. In the example I posted, the VTOC is on
record 5:
RECORD 3 (a VOL1 label)
KEY 4 0000 E5D6D3F1 *VOL1 *
DATA 80 0000 E5D6D3F1 E3C5E2E3 C5D9F000 00000005 *VOL1TESTER0.....*
0010 00000000 00404040 40404040 40404040 *..... *
0020 40404040 40404040 40000000 0000C3D7 * .....CP*
0030 E5D6D340 40404040 40404040 40404040 *VOL *
0040 40404040 40404040 40404040 40404040 * *
RECORD 5 - This looks like a good type 4 DSCB
KEY 44 0000 04040404 04040404 04040404 04040404
0010 04040404 04040404 04040404 04040404
0020 04040404 04040404 04040404
DATA 96 0000 F4000000 00050000 00000000 00000001
DSCB type = 0xF4 = 4
max CCHHR of DSCB entry = 000000005
# VTOC extents = 0x01 = 1
0010 00000005 000FE5A2 00000030 0000322D
SMS status = 0x00 = Non-system managed volume
# alt cyls = 0x00 = 0
# cyls = 0x0005 = 5
# trks/cyl = 0x000F = 15
Trk length = 0xE5A2 = 58786
Flags = 0x30 = 0011 0000
...1 ... = # alt cyls is valid
..1. ... = ????? Not defined
DSCBs per track = 0x32 = 50
PDS dir blocks per track = 0x2D = 45
0020 00000000 00000000 00000000 00000000
0030 00000000 00000000 00000000 00000000
0040 00000000 00000000 00000000 00000000
0050 00000000 00000000 00000000 00000000
RECORD 6 - This looks like a type 5 DSCB
KEY 44 0000 05050505 00010000 00000000 00000000
key = 0x05050505
relative addr of 1st avail trk = 0x0001
# UNused cyls = 0x0000 = 0
# add'l unused trks = 0x00 = 0
0010 00000000 00000000 00000000 00000000
0020 00000000 00000000 00000000
DATA 96 0000 F5000000 00000000 00000000 00000000
DSCB type = 0xF5 = 5
0010 00000000 00000000 00000000 00000000
0020 00000000 00000000 00000000 00000000
0030 00000000 00000000 00000000 00000000
0040 00000000 00000000 00000000 00000000
0050 00000000 00000000 00000000 00000000
Repeating the DITTO VTOC listing:
Unit 0111 VOLSER TESTER 3390 with 5 cyls, 15 trks/cyl, 58786 bytes/trk
--- Data Set Name --- sorted by NAME ----- Ext Begin-end Reltrk,
1...5...10...15...20...25...30...35...40.... seq Cyl-hd Cyl-hd numtrks
*** VTOC EXTENT *** 0 0 0 0 0 0,1
*** FREE EXTENT *** 0 0 1 4 14 1,74
*** This volume is currently 1 percent full with 74 tracks available
I agree that that the DSCB-4 says the VTOC consists of only one track
starting on track 0 of cyl 0, head 0. I have no idea how it decided from
the DSCB-5 shown above that the rest of the volume was available. I even
changed the 0x0001 to 0x0000 in the DSCB-5 and it says the same thing.
I wonder what the DSCB-5 looks like on an MVS volume that is completely
full? Maybe DITTO is wrong?
Alan Altmark
z/VM Development
IBM Endicott
