Joined: 30 Jun 2010 Posts: 85 Location: Toronto, ON
I am getting the following abend while copying a VSAM file to another VSAM file with same attributes using FLASHCOPY utility. This job in which I got this error runs everyday without any issues. There were no changes done to it. It is working fine with the other files except two files for which it is giving the below error. Following control card is passed to the FLASHCOPY step:
Could someone please advise for what the below error could come for?
ADR711I (001)-NEWDS(01), DATA SET ABC.VSAM.TEST HAS BEEN ALLOCATED WITH NEWNAME ABC.VSAM.TEST.BACKUP USING STORCLAS
SCPRD, DATACLAS DCVSEXTC, AND MGMTCLAS MCNOACT
ADR763E (001)-DDFLT(01), DATA SETS IN SPHERE OF BASE CLUSTER ABC.VSAM.TEST WITH NEWNAME ABC.VSAM.TEST.BACKUP WERE NOT
ADR801I (001)-DDDS (01), DATA SET FILTERING IS COMPLETE. 1 OF 1 DATA SETS WERE SELECTED: 0 FAILED SERIALIZATION AND 0 FAILED FOR
ADR455W (001)-DDDS (01), THE FOLLOWING DATA SETS WERE NOT SUCCESSFULLY PROCESSED
ADR013I (001)-CLTSK(01), 2011.221 07:39:14 TASK ABENDED WITH USER ABEND CODE 0001
ADR012I (SCH)-DSSU (01), 2011.221 07:39:14 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS 0008 FROM:
ADR763E (ttt)-mmmmm(yy), DATA SETS IN SPHERE OF BASE CLUSTER cluster_name1
[WITH NEWNAME cluster_name2] WERE NOT ALL RENAMED
Explanation: When copying a sphere without specifying DELETE or RECATALOG, you must rename all parts of the sphere. If the target sphere is to be SMS-managed, the data sets must be renamed even if RECATALOG was specified, because RECATALOG is ignored for SMS-managed data sets.
System Action: Processing continues with the next data set. The return code is 8.
Operator Response: None.
Application Programmer Response: Do one of the following, then rerun the job:
Specify the DELETE or RECATALOG keyword.
Add or change the RENAMEUNCONDITIONAL keyword specification to rename all data sets in the sphere.
Routing Code: MISSING INFO.
Descriptor Code: MISSING INFO.
Joined: 06 Jun 2008 Posts: 8201 Location: Dubuque, Iowa, USA
You need to specify DELETE and / or RECATALOG, depending upon what you are doing exactly -- which is what the message from the manual tells you to do. Or you could figure out exactly what the meaning of the message is and from there figure out which component(s) of the VSAM sphere are causing the problem.