Hi, Incase if you are trying to move your HSM control Files(MCDS,OCDS,BCDS). Then probably you might get this error because HSM control files are Normal VSAM files. If this is your case then you have to stop HSM and Invoke DFDSS to move on the VSAM datasets.
Regards, Jags On Tue, Apr 5, 2011 at 8:28 PM, chen lucky <[email protected]> wrote: > In original post, there is no 'delete' parameter specified, but even so, > there are still some DataSets had been copied successfully. Do not know > why, > may these copied ones are not cataloged. > > 2011/4/5 SAURABH KHANDELWAL <[email protected]> > > > Thanks Richard, > > I tried using STORAGE CLASS parameter( > > NOSMS). but still got same error. Now I am searching for the parameter > you > > suggested. > > > > Regards > > > > > > On 4/5/2011 7:38 PM, Richard Marchant wrote: > > > >> Saurabh, > >> > >> There is a parameter in ADRDSSU where you can bypass the ACS routines, > >> something like BYPASSACS. Check out the manual. > >> > >> HTH > >> > >> Richard > >> > >> ________________________________________ > >> From: IBM Mainframe Discussion List [[email protected]] on behalf of > >> McKown, John [[email protected]] > >> Sent: 05 April 2011 03:06 PM > >> To: [email protected] > >> Subject: Re: ADRDSSU issue > >> > >> My __guess__ is that your STORCLAS ACS routine is assigning a storage > >> class to the new allocations. In my shop, I __must__ specify the > parameter: > >> STORAGECLASS(NONSMS) which is tested in the ACS routines to make a > dataset > >> non SMS managed. Again, AT MY SHOP, this is a requirement. Why? Because > >> that's how I wrote the ACS routine. The ACS routines are in house > written. > >> > >> -- > >> John McKown > >> Systems Engineer IV > >> IT > >> > >> Administrative Services Group > >> > >> HealthMarkets(r) > >> > >> 9151 Boulevard 26 * N. Richland Hills * TX 76010 > >> (817) 255-3225 phone * > >> [email protected] * > >> www.HealthMarkets.com<http://www.healthmarkets.com/> > >> > >> Confidentiality Notice: This e-mail message may contain confidential or > >> proprietary information. If you are not the intended recipient, please > >> contact the sender by reply e-mail and destroy all copies of the > original > >> message. HealthMarkets(r) is the brand name for products underwritten > and > >> issued by the insurance subsidiaries of HealthMarkets, Inc. -The > Chesapeake > >> Life Insurance Company(r), Mid-West National Life Insurance Company of > >> TennesseeSM and The MEGA Life and Health Insurance Company.SM > >> > >> > >> > >> -----Original Message----- > >>> From: IBM Mainframe Discussion List > >>> [mailto:[email protected]] On Behalf Of SAURABH KHANDELWAL > >>> Sent: Tuesday, April 05, 2011 7:58 AM > >>> To: [email protected] > >>> Subject: ADRDSSU issue > >>> > >>> Hello, > >>> I am trying to copy my SYSRES volume( ex: IPE100) > >>> into one > >>> new volume ( ex IPE101). All the dataset inside IPE100 is managed by > >>> indirect cataloging. > >>> > >>> I am using below JCL for this function. > >>> > >>> //DUMPUP01 JOB CLASS=A,MSGCLASS=A,MSGLEVEL=(1,1), > >>> // NOTIFY=&SYSUID > >>> //STEP2 EXEC PGM=ADRDSSU,REGION=0M,COND=(0,LT) > >>> //SYSPRINT DD SYSOUT=* > >>> //RES1IN DD UNIT=3390,VOL=SER=DMTRES,DISP=SHR > >>> //RES1OUT DD UNIT=3390,VOL=SER=RES001,DISP=SHR > >>> //SYSIN DD * > >>> COPY INDD(RES1IN) OUTDD(RES1OUT) - > >>> DS(EXCLUDE(SYS1.VTOCIX.* - > >>> SYS1.VVDS.* - > >>> )) - > >>> TOLERATE(ENQF) SHARE ALLEXCP ALLDATA(*) CANCELERROR. > >>> > >>> > >>> But, I am getting below error while doing copy for some of > >>> the dataset. > >>> > >>> *ADR713E (001)-ALLOC(01), UNABLE TO ALLOCATE SMS MANAGED DATA SET > >>> TCPIP.SEZAXAWL* > >>> ADR713E (001)-ALLOC(01), UNABLE TO ALLOCATE SMS MANAGED DATA SET > >>> CEE.SCEESAMP BE > >>> ADR396I (001)-NEWDS(01), DATA SET SYS1.SISTASN1 ALLOCATED, ON > >>> VOLUME(S): > >>> RES001 > >>> ADR396I (001)-NEWDS(01), DATA SET SYS1.SBPXMENU ALLOCATED, ON > >>> VOLUME(S): > >>> RES001 > >>> ADR713E (001)-ALLOC(01), UNABLE TO ALLOCATE SMS MANAGED DATA SET > >>> CEE.SCEELKED BE > >>> ADR396I (001)-NEWDS(01), DATA SET SYS1.SISTCMIP ALLOCATED, ON > >>> VOLUME(S): > >>> RES001 > >>> ADR396I (001)-NEWDS(01), DATA SET SYS1.DBBLIB ALLOCATED, ON > >>> VOLUME(S): > >>> RES001 > >>> ADR396I (001)-NEWDS(01), DATA SET SYS1.MIGLIB ALLOCATED, ON > >>> VOLUME(S): > >>> RES001 > >>> ADR713E (001)-ALLOC(01), UNABLE TO ALLOCATE SMS MANAGED DATA SET > >>> ISF.SISFJCL BEC > >>> *ADR713E (001)-ALLOC(01), UNABLE TO ALLOCATE SMS MANAGED DATA SET > >>> CEE.SCEEH.SYS.H* > >>> ADR396I (001)-NEWDS(01), DATA SET SYS1.MSGENU ALLOCATED, ON > >>> VOLUME(S): > >>> RES001 > >>> ADR396I (001)-NEWDS(01), DATA SET SYS1.DGTTLIB ALLOCATED, ON > >>> VOLUME(S): > >>> RES001 > >>> ADR396I (001)-NEWDS(01), DATA SET SYS1.SAPPMOD1 ALLOCATED, ON > >>> VOLUME(S): > >>> RES001 > >>> ADR744W (001)-MRPAM(01), NO VALID MEMBERS WERE FOUND FOR PDS DATA SET > >>> SYS1.SAPPM > >>> ADR396I (001)-NEWDS(01), DATA SET SYS1.HRFCLST ALLOCATED, ON > >>> VOLUME(S): > >>> RES001 > >>> ADR396I (001)-NEWDS(01), DATA SET SYS1.SBLSKEL0 ALLOCATED, ON > >>> VOLUME(S): > >>> RES001 > >>> > >>> > >>> As per my knowledge, only non SMS managed dataset used to be on RES > >>> volume. Then I am not sure, why I am getting above error. > >>> Also the RES > >>> volume is non SMS managed. > >>> > >>> Can anybody help me to resolve this issue. > >>> > >>> > >>> Regards > >>> Saurabh > >>> > >>> > >>> ---------------------------------------------------------------------- > >>> For IBM-MAIN subscribe / signoff / archive access instructions, > >>> send email to [email protected] with the message: GET IBM-MAIN INFO > >>> Search the archives at http://bama.ua.edu/archives/ibm-main.html > >>> > >>> > >>> ---------------------------------------------------------------------- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to [email protected] with the message: GET IBM-MAIN INFO > >> Search the archives at http://bama.ua.edu/archives/ibm-main.html > >> > >> ---------------------------------------------------------------------- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to [email protected] with the message: GET IBM-MAIN INFO > >> Search the archives at http://bama.ua.edu/archives/ibm-main.html > >> > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: GET IBM-MAIN INFO > > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
