On Friday, 02/01/2008 at 02:03 EST, Chip Davis [EMAIL PROTECTED] wrote:
Oh man, I *HATE* it when that happens... :-)
Dennis, I commend your courage and candor. We've all been there, and
sometimes
managed to slink away unnoticed with an only slightly flattened
forehead.
Just think of all
I thought I'd provide an update and closure to this S213 abend issue.
The solution was actually pretty embarrassing. The solution was to vary
the
device offline/online to the correct z/OS system.
I had recognized the need to vary the device offline/online before I even
solicited input from
Oh man, I *HATE* it when that happens... :-)
Dennis, I commend your courage and candor. We've all been there, and sometimes
managed to slink away unnoticed with an only slightly flattened forehead.
Just think of all the valuable insight we all gained about VM VTOC records from
your
I sent Dale a TYPE of two cyl 0 head 0 (one of z/VM 5.3 and one of an
ICKDSF CPVOL-ed Tdisk)
2008/1/18, Dale R. Smith [EMAIL PROTECTED]:
The VTOC should start right after the volume label. The first record in
the VTOC should be the FMT4 (Format-4) DSCB record. The second record in
the VTOC
Thanks Kris! I was wrong about the location of the Format-4 DSCB, it
doesn't always follow immediately after the volume label record. The
volume label record is always the third record on cylinder 0 track 0. Th
e
volume label record has a pointer to the first record in the VTOC, (which
is
On Monday, 01/21/2008 at 10:02 EST, Dale R. Smith
[EMAIL PROTECTED] wrote:
The x'05050505' in the KEY area indicates that this is a Format-5 DSCB.
Immediately following the key identifier, the x'0001' is the first free
track available, (relative to the beginning of the volume). The x''
IIRC, ICKDSF CPVOLUME FORMAT is supposed to set the FMT5 DSCB in
the VTOC for a volume to indicate that there is no free space on the
volume. The FMT4 DSCB should contain the size of the volume. I'm not
sure what DITTO is looking at, but z/OS should be using the FMT5 DSCB.
What does a
Dale,
I hope I don't lose your interest; it will be sometime next week before I
can get that information because (1 I can't IPL it due to bad HMC-SE
connectivity which occurred last night; the processor is in another city
and
(2 it will be next week before we get network connectivity for the
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 VTOC should start right after the volume label. The first record in
the VTOC should be the FMT4 (Format-4) DSCB record. The second record in
the VTOC should be the FMT5 (Format-5) DSCB record. Here is a pointer to
the layout of the Format-4 DSCB: http://publibz.boulder.ibm.com/cgi-
-
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens
Sent: Thursday, January 17, 2008 11:35 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: S213 Abend Backing Up 530RES Using z/OS FDR
Same here (for a VM resident)
DITTO/ESA for VM DVT - Display VTOC
DDR TYPE of cyl 0, track0 is still a lot of data. One should know which
fields to display.
2008/1/18, Dale R. Smith [EMAIL PROTECTED]:
IIRC, ICKDSF CPVOLUME FORMAT is supposed to set the FMT5 DSCB in
the VTOC for a volume to indicate that there is no free space on the
volume. The FMT4 DSCB
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
Before trying to fix (if required) the packs of your new VM system,
use ICKDSK CPVOL FORMAT on a spare pack and see if FDR likes that
better. Because, I'd think that when the z/VM 5.3 disks were created
at IBM, the same ICKDSF was being used. I also suppose that the
process to create the INSTDVD
Dennis,
This appears to be a problem with FDR. I have used it to backup various
VM DASD for over 20 years.
I suggest you contact Innovation.
Jim
This message w/attachments (message) may be privileged, confidential or
proprietary, and
VM doesn't use VTOCs to describe disk contents; the CP directory tells which
cylinders are allocated as minidisks, and the CP allocation map tells CP
which cylinders to use for PAGE, SPOOL, etc.
I'll send you a document with some extra information about this subject.
The FTP based installation
I use FDR to backup my current z/VM 510 system. However, you need to
make sure you are using FDR and not FDRABR.
Here is part of the JCL I use to backup the z/VM system.
//VMDUMP EXEC PGM=FDR,REGION=0M,
//PARM='DUMP TYPE=FDR'
//SYSPRINT DD SYSOUT=*
.
Don't know it this helps
Mace
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Kris Buelens
Sent: Thursday, January 17, 2008 9:42 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: S213 Abend Backing Up 530RES Using z/OS FDR
PROTECTED] On
Behalf Of Kris Buelens
Sent: Thursday, January 17, 2008 9:42 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: S213 Abend Backing Up 530RES Using z/OS FDR
VM doesn't use VTOCs to describe disk contents; the CP directory tells
which cylinders are allocated as minidisks
PROTECTED] On
Behalf Of Kris Buelens
Sent: Thursday, January 17, 2008 9:42 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: S213 Abend Backing Up 530RES Using z/OS FDR
VM doesn't use VTOCs to describe disk contents; the CP directory tells
which cylinders are allocated as minidisks, and the CP
Of Kris Buelens
Sent: Thursday, January 17, 2008 9:42 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: S213 Abend Backing Up 530RES Using z/OS FDR
VM doesn't use VTOCs to describe disk contents; the CP directory tells
which cylinders are allocated as minidisks, and the CP allocation map
tells
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On
Behalf Of Kris Buelens
Sent: Thursday, January 17, 2008 9:42 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: S213 Abend Backing Up 530RES Using z/OS FDR
VM doesn't use VTOCs to describe
Dennis--If I remember correctly, you'll also have to be able to do a
DIRECTXA to reload the directory. I think there is a pointer on cyl 0
that points to the current system directory even tho the DRCT allocated
area is somewhere else. I may be wrong, but just in case
Jim
Dennis
Yes indeed:
There are two hex values for DRCT (maybe not exact): X'40' inactive DRCT
cylinder; X'C0' active DRCT cylinder. ICKDSF ALLOCATE writes X'40' for
DRCT, and CP won't find an active DRCT anymore.
2008/1/17, Jim Bohnsack [EMAIL PROTECTED]:
Dennis--If I remember correctly, you'll also
On Thursday, 01/17/2008 at 09:42 EST, Kris Buelens
[EMAIL PROTECTED] wrote:
VM doesn't use VTOCs to describe disk contents; the CP directory tells
which
cylinders are allocated as minidisks, and the CP allocation map tells CP
which
cylinders to use for PAGE, SPOOL, etc.
After a CPFMTXA
Same here (for a VM resident)
DITTO/ESA for VM DVT - Display VTOC Line 1 of 2
Unit 0130 VFRRES 3390 with 3339 cyls, 15 trks/cyl, 58786 bytes/trk
--- Data Set Name ---Ext Begin-endReltrk,
1...5...10...15...20...25...30. seq Cyl-hd Cyl-hd
26 matches
Mail list logo
