Error message in ADRDSSU utility

Nikhil Bhole · New User Joined: 25 Feb 2008 Posts: 12 Location: Pune

//STEP03 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//IN1 DD VOL=SER=ZHTW04,UNIT=DISK,DISP=SHR
//OUT1 DD VOL=SER=ZHTW05,UNIT=DISK,DISP=SHR
//SYSIN DD *
COPY DATASET(INCLUDE(ABC.XYZ.LMN)) -
OUTDDNAME(OUT1) -
INDDNAME(IN1) -
ALLX -
ALLDATA(*) -
CANCELERROR -
CATALOG -
DELETE PURGE
/*

For this step I get the following error:

UNABLE TO SELECT A TARGET VOLUME FOR DATA SET ABC.XYZ.LMN
DATA SET FILTERING IS COMPLETE. 1 OF 1 DATA SETS WERE SELECTED: 0 FAILED SERIALIZATION AND 0 FAILED FOR OTHER REASONS.
THE FOLLOWING DATA SETS WERE NOT SUCCESSFULLY PROCESSED
ABC.XYZ.LMN

Note: There is sufficient space on the volume serial ZHTW05 to accomodate the PS ABC.XYZ.LMN.

gcicchet · Posted: Tue Mar 11, 2008 11:45 am

Hi,
try pasting the entire MSG from job output.

Gerry

Nikhil Bhole · New User Joined: 25 Feb 2008 Posts: 12 Location: Pune

PAGE 0001 5695-DF175 DFSMSDSS V1R08.0 DATA SET SERVICES 2008.071 00:48
COPY DATASET(INCLUDE(ABC.XYZ.LMN)) -
OUTDDNAME(OUT1) -
INDDNAME(IN1) -
ALLX -
ALLDATA(*) -
CANCELERROR -
CATALOG -
DELETE PURGE
ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'COPY '
ADR109I (R/I)-RI01 (01), 2008.071 00:48:53 INITIAL SCAN OF USER CONTROL STATEMEN
ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK
ADR006I (001)-STEND(01), 2008.071 00:48:53 EXECUTION BEGINS
ADR472E (001)-NEWDS(11), UNABLE TO SELECT A TARGET VOLUME FOR DATA SET ABC.XYZ.LMN
ADR801I (001)-DDDS (01), DATA SET FILTERING IS COMPLETE. 1 OF 1 DATA SETS WERE SELECTED: 0 FAILED SERIALIZATION AND 0 FAILED FOR OTHER REASONS.
0ADR455W (001)-DDDS (02), THE FOLLOWING DATA SETS WERE NOT SUCCESSFULLY PROCESSED
0 ABC.XYZ.LMN
0ADR006I (001)-STEND(02), 2008.071 00:48:54 EXECUTION ENDS
0ADR013I (001)-CLTSK(01), 2008.071 00:48:54 TASK COMPLETED WITH RETURN CODE 0008
0ADR012I (SCH)-DSSU (01), 2008.071 00:48:54 DFSMSDSS PROCESSING COMPLETE. HIGHEST RETURN CODE IS 0008 FROM:
TASK 001

gcicchet · Posted: Tue Mar 11, 2008 12:40 pm

Hi,
if volumes are SMS managed then it's possible that the dataset is trying to go to a different volume than the one mentioned in the JCl.

This volume may not have sufficient space.

Check the JCL output and see the volume it allocated for DDNAME OUT1.

Gerry

expat · Posted: Tue Mar 11, 2008 12:51 pm

And if you must use a specific volume and it is SMS managed, then consider that to honour a specific volume allocation you must use a STORCLAS with the guaranteed space attribute.

What did the explanation of ADR472E tell you when you looked it up ?

Is this a multi volume dataset that you are attempting to put onto a single volume ?

Srihari Gonugunta · Posted: Tue Mar 11, 2008 12:57 pm

publib.boulder.ibm.com/infocenter/zos/v1r9/index.jsp?topic=/com.ibm.zos.r9.ieam100/iea2m18021.htm

ADR472E(xxx)-mmmmm(yy), UNABLE TO SELECT A TARGET VOLUME FOR DATA SET dsname [IN CATALOG catalog_name], reason_code
Explanation:
DFSMSdss was unable to select a target volume from the available target volumes for one of the following reasons, (reason_code):

08
At least one duplicate data set was encountered on a target volume, and the REPLACE or REPLACEUNCONDITIONAL keyword was not specified. If the duplicate data set is named SYS1.xxxx, you must also specify PROCESS(SYS1). However, DFSMSdss will not replace a SYS1.xxxx data set that is a CVOL, integrated catalog facility user catalog, VVDS, or VTOCIX, regardless of the REPLACE or REPLACEUNCONDITIONAL and PROCESS(SYS1) keywords.
If the target volume did not contain a duplicate data set, this reason code means the target volume did not have enough space for the data set.

amolph · New User Joined: 28 Dec 2007 Posts: 4 Location: pune

Here in Nikhil's case ,all datasets are of single database & should be in single volser.The vol ser mentioned also have sufficient space ,required for all those datasets.Then also it is failing .Could any one explain why?

Candice157 · New User Joined: 20 Jul 2007 Posts: 1 Location: USA

I just had this same problem and got the same error - An UN-CATALOGED dataset by the SAME DSN existed on the RECEIVING DASD(Pack).

The DSN on the SENDING(IN) pack was CATALOGED. The DSN on the RECEIVING(out) PACK was NOT CATALOGED.

I didn't really need the Dataset on the Input pack, so I deleted that dataset and cataloged the one on the new DASD - We just received new DASD and I was trying to move my dataset and got this error.

Now I know at least one or 2 things to look for, if I get the same error again.

I've still got PLENTY of unused space on the new DASD.