If it is SMS managed, then the volume doesn't matter. You specified a specific volume, so I assumed a non-sms volume.
On Fri, Mar 22, 2013 at 8:28 AM, willie bunter <williebun...@yahoo.com> wrote: > Elardus, > > I tried your suggestion : > > HSEND RECALL 'HESPDE02..ABACKUP.IMS1.HLIST' DFDSSOPTION(VOLCOUNT(ANY)) - > FORCENONSMS VOLUME(SMTP17) UNIT(3390) > /* > However it didn't work. According to the error message ADR472E 72 : > During a non-SMS allocation, no target volumes were available and at least > one output volume was not selected because it was SMS-managed. > > Programmer response : > If you expect the target data set to be SMS-managed, ensure the ACS routine > assigns a storage class or use the BYPASS ACS and STORCLAS keywords to force > the data set to be SMS-managed. I tried the BYPASS ACS however I was using > NULLSTORCLAS. Could that be my error? > > PAGE 0001 5695-DF175 DFSMSDSS V1R13.0 DATA SET SERVICES 2013.081 > 09:20 > ADR035I (SCH)-PRIME(06), INSTALLATION EXIT ALTERED BYPASS FAC CLASS CHK > DEFAULT > TO YES > RESTORE INDDNAME(SYS00115) CAT - > BYPASSACS(HESPDE02.ABACKUP.IMS1.HLIST ) - > NULLMGMTCLAS NULLSTORCLAS - > OUTDYNAM((SMTP17)) - > REBLOCK(HESPDE02.ABACKUP.IMS1.HLIST ) - > VOLCOUNT(ANY) - > FORCECP(0) - > DATASET(INCLUDE(HESPDE02.ABACKUP.IMS1.HLIST )) > ADR101I (R/I)-RI01 (01), TASKID 001 HAS BEEN ASSIGNED TO COMMAND 'RESTORE ' > ADR109I (R/I)-RI01 (01), 2013.081 09:20:11 INITIAL SCAN OF USER CONTROL > STATEME > NTS COMPLETED > ADR050I (001)-PRIME(01), DFSMSDSS INVOKED VIA APPLICATION INTERFACE > ADR016I (001)-PRIME(01), RACF LOGGING OPTION IN EFFECT FOR THIS TASK > ADR006I (001)-STEND(01), 2013.081 09:20:11 EXECUTION BEGINS > ADR780I (001)-TDDS (01), THE INPUT DUMP DATA SET BEING PROCESSED IS IN > LOGICAL DATA SET FORMAT AND WAS CREATED BY DFSMSDSS VERSION > 1 RELEASE 13 MODIFICATION LEVEL 0 ON 2013.079 > 12:50:07 > ADR472E (001)-NEWDS(06), UNABLE TO SELECT A TARGET VOLUME FOR DATA SET > HESPDE02.A > BACKUP.IMS1.HLIST, 72 > ADR415W (001)-TDLOG(01), NO DATA SETS WERE COPIED, DUMPED, OR RESTORED FROM > ANY > VOLUME > ADR480W (001)-TDLOG(01), THE FOLLOWING DATA SETS WERE NOT PROCESSED FROM THE > LO > GICALLY FORMATTED DUMP TAPE DUE TO ERRORS: > HESPDE02.ABACKUP.IMS1.HLIST > ADR006I (001)-STEND(02), 2013.081 09:20:11 EXECUTION ENDS > ADR013I (001)-CLTSK(01), 2013.081 09:20:11 TASK COMPLETED WITH RETURN CODE > 0008 > ADR012I (SCH)-DSSU (01), 2013.081 09:20:11 DFSMSDSS PROCESSING COMPLETE. > HIGHES > T RETURN CODE IS 0008 FROM: > TASK 001 > ARC1001I HESPDE02.ABACKUP.IMS1.HLIST RECALL FAILED, RC=0069, REAS=0472 > ARC1169I RECALL/RECOVER FAILED DUE TO AN ERROR IN DFDSS > > > ________________________________ > From: Elardus Engelbrecht <elardus.engelbre...@sita.co.za> > To: IBM-MAIN@LISTSERV.UA.EDU > Sent: Friday, March 22, 2013 9:12:59 AM > Subject: Re: DFHSM QUESTION - RECALLING DSN TO ITS ORIGINAL VOLUME > > willie bunter wrote: > > HSEND RECALL 'HESPDE02.ABACKUP.IMS1.HLIST' DFDSSOPTION(VOLCOUNT(ANY)) - > FORCENONSMS VOLUME(SMTP17) - > BYPASSACS(**) - > NULLSTORCLAS > > Where is your UNIT(<???>) keyword? As documented, you MUST specify UNIT when > specify VOLUME. (and vice versa too). > > I'm not sure about inlusion of BYPASSACS(**) and NULLSTORCLAS, because > FORCENONSMS is sufficient, IMHO. > I could not find them also in the manuals for HSEND RECALL command. > > Groete / Greetings > Elardus Engelbrecht > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
