COPYTOCOPY utility and DSNU1402I msg

James Hannis

COPYTOCOPY utility and DSNU1402I msg
I'm not suggesting that all error conditions on a COPYTOCOPY result in rc=04
instead of rc=08. I was agreeing that in the specific case noted below that
the return code should be set to 04 -

"a DSNU1402i msg on the COPYTOCOPY utility (COPYTOCOPY attempted to make an
image copy that already exists), this we expect as we are using the
FROMLASTCOPY parm and some of the tablespaces in the copy have not changed.
Our issue is that the utility is ending RC=08, and remaining object(s) in
the list are not processed. Our interpretation of the DSNU1402i message is
that this should be a rc=04 warning and the remaining objects should be
processed."

Jim Hannis
Senior Database Administrator
Transamerica Distribution Finance
5595 Trillium Blvd.
Hoffman Estates, IL 60192
847-747-6627
847-456-0902 (cell)
[login to unmask email]

-----Original Message-----
From: Horacio Villa [mailto:[login to unmask email]
Sent: Thursday, December 18, 2003 4:14 PM
To: [login to unmask email]
Subject: Re: COPYTOCOPY utility and DSNU1402I msg

There are other reasons for an RC 8, like tablespace in recover pending
(well, not in a COPYTOCOPY). If you get a 4, how do you know (without
looking at SYSPRINT) that some COPYs didn't work?

Horacio Villa




"Hannis, James"
<[login to unmask email] To:
[login to unmask email]
MERICA.COM> cc:
Sent by: DB2 Data Subject: Re: COPYTOCOPY
utility and DSNU1402I msg
Base Discussion List
<[login to unmask email]
>


12/18/03 07:01 PM
Please respond to
DB2 Database
Discussion list at
IDUG






We have run into the same problem so we tried the OPTIONS
EVENT(ITEMERROR,SKIP). While it did skip the problem COPYTOCOPY and
process
the rest of the control cards, the step still ended with a RC = 08.

We were hoping for a RC = 04 with this situation.


Jim Hannis
Senior Database Administrator
Transamerica Distribution Finance
5595 Trillium Blvd.
Hoffman Estates, IL 60192
847-747-6627
847-456-0902 (cell)
[login to unmask email]

-----Original Message-----
From: Horacio Villa [mailto:[login to unmask email]
Sent: Thursday, December 18, 2003 1:45 PM
To: [login to unmask email]
Subject: Re: COPYTOCOPY utility and DSNU1402I msg

Dave,

if you're using LISTDEF, use OPTIONS EVENT(ITEMERROR,SKIP) before
COPYTOCOPY.

Horacio Villa




Dave Stokes
<[login to unmask email] To:
[login to unmask email]
TAN.CO.UK> cc:
Sent by: DB2 Data Subject: COPYTOCOPY utility
and DSNU1402I msg
Base Discussion
List
<[login to unmask email]
ORG>


12/18/03 08:58 AM
Please respond to
DB2 Database
Discussion list
at IDUG






Hi,

We are new to DB2 on mainframe Z/OS and are currently setting up our
backup/recovery procedures. Through testing out different approaches to
this, we have come across a DSNU1402i msg on the COPYTOCOPY utility
(COPYTOCOPY attempted to make an image copy that already exists), this we
expect as we are using the FROMLASTCOPY parm and some of the tablespaces in
the copy have not changed. Our issue is that the utility is ending RC=08,
and remaining object(s) in the list are not processed.
Our interpretation of the DSNU1402i message is that this should be a rc=04
warning and the remaining objects should be processed.
Of interest, we did find APAR NUMBER: PQ76964 which relates to the above
message and symptom on COPYTOCOPY restarts, however we applied this and
still have the problem.
Is this the expected behaviour of the COPYTOCOPY utility or is this a
bug ?, we are new to this and still finding our feet.

regards
Dave Stokes

OttoUk

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

-----

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm

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

-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm

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

Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm