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 problem... ;->
-Chip-
On 2/1/08 04:12 Dennis_Schaffer said:
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 the community. However, my backup job was redirected
to a different z/OS system from the one where the varies occurred.
So, there was no problem with the z/VM sysres volume which was built by the
installation process.
Probable user error.
Thanks to all of you for your input.
Dennis
On Thu, 17 Jan 2008 00:28:09 -0600, Dennis Schaffer
<[EMAIL PROTECTED]> wrote:
Hi,
I'm installing z/VM (v5.3) in a previously z/OS-only shop. Because there is
no existing VM, I'm doing a first-level installation and I'm also using the
FTP server method. The installation, while slow, has completed successfully
and I'm able to IPL the newly-installed system. Thanks, IBM, for allowing
me to bypass all those tapes.
I don't yet have access to any tape drives under VM so I'm depending on z/OS
to backup my newly-installed volumes, 530RES, 530PAG and 530SPL.
However, I experience S213-04 abends (can't find SYS1.VTOC on the volume)
attempting to backup these volumes using Innovation's FDR under z/OS. z/VM
was shutdown and I varied the volumes offline/online to z/OS following the
first failure, hoping that might correct the problem. I've used the same
product/technique many times before in a past life and I know the process
works.
I suspect the installation process (whether its something inherent to v5.3
or something unique to the FTP server install process, I'm not sure) is not
initializing these volumes with the "dummy VTOC" required by z/OS. I did
not override the default volume format option of the installation.
I suspect I need to run ICKDSF CPVOLUME FORMAT (or CPFMTXA FORMAT) against
cyl 0 on each of these volumes (first documenting and resbuilding the
allocation maps) and then run SALIPL to rewrite the Loader IPL text on
530RES. Be aware that I'll more than likely be doing this against a running
system without a backup (I'll probably try to DDR MAINT 123/124/125 to
another volume, for a small amount of insurance).
I think that's what I need to do but I want to run it past the community
because I don't want to go through that multi-day installation again. Does
this sound reasonable? Can you think of any other reason I'd be
experiencing this error?
Thanks in advance for your assistance.
Dennis Schaffer
========================================================================
