I would try that.
We use DFDSS to dump too.  I recall that there were some vols that had a
problem.   I think it was 3390-9's that had been ddr's of 3's at one
point in their life.  Hard to remember though.


Marcy Cortes 
 
"This message may contain confidential and/or privileged information. If
you are not the addressee or authorized to receive this for the
addressee, you must not use, copy, disclose, or take any action based on
this message or any information herein. If you have received this
message in error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your cooperation."


-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Dennis Schaffer
Sent: Thursday, January 17, 2008 8:22 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: [IBMVM] S213 Abend Backing Up 530RES Using z/OS FDR

I just attempted to use DFDSS to dump 530RES using the syntax suggested
b= y Larry and I got another S213 abend for SYS1.VTOC.  I think the
problem is=
 
with the volume and not the dumping software.

What do you think of my original suggestion (CPFMTXA FORMAT cyl 0,
followed by SALIPL to reload the IPL text) for correcting the problem?

Thanks,
Dennis


On Thu, 17 Jan 2008 09:59:43 -0500, Macioce, Larry
<[EMAIL PROTECTED]> wrote:

>We use dfdss from z/OS to backup all our z/VM packs and you must have a

special parm in the job to do that. The parms (sysin) looks like this:



 



DUMP TRACKS(0,0,3338,14) INDDNAME(DASD) OUTDDNAME(TAPE) ADMIN - 



CPVOLUME CANCELERROR      



The admin and cpvolume are a must.             =
                         =




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



 



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 shouldn't have anything to do with your FDR

problem.  The fact that CP can IPL fine means all is OK.  You should

tell FDR -I don't know how- that it should take some physical based

backup, or has it a "VM-format" parameter? 



2008/1/17, Dennis Schaffer <[EMAIL PROTECTED]>:



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

t

he

FTP server method.  The installation, while slow, has completed

successfu 

lly

and I'm able to IPL the newly-installed system.  Thanks, IBM, for

allowin

g

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

th

e

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

n

ot

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)

agains

t

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

runn

ing

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.

Do

es

this sound reasonable?  Can you think of any other reason I'd be

experiencing this error?



Thanks in advance for your assistance.



Dennis Schaffer









-- 

Kris Buelens,

IBM Belgium, VM customer support 









-----------------------------------------

********************************************************************

The information transmitted is intended solely for the individual or
entity to which it is addressed and may contain confidential and/or

privileged material. Any review, retransmission, dissemination or other
use of or taking action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. If you have
received this email in error please contact the sender and delete the

material from any computer.

********************************************************************

Reply via email to