Hello Jags,It is not about coping only IODF cluster file. This problem is in general coping VSAM dataset along with NON VSAM dataset. The last JCL which you suggested, that has worked out with Non VSAM dataset, but in my some of the volume I do have VSAM dataset as well, so I was looking for the parameter, which can also copy VSAM as well.
Regards Saurabh Khandelwal On 4/6/2011 6:59 AM, jagadishan perumal wrote:
Hi,1) Instead of copying your IODF cluster. You can even use your existing IODF and Just IPL from the address of the new COD sysres volume, but point LOADPARM at your normal IODF volume. 2) Or else you can define a new Cluster at the target volume and copy the existing IODF cluster from the source using the load module CBDMGHCP. You can google it to find the sample JCL for CBDMGHCP.Regards, JagsOn Tue, Apr 5, 2011 at 8:48 PM, SAURABH KHANDELWAL <[email protected] <mailto:[email protected]>> wrote:Hello, Along with PS and PDS i am also coping VSAM dataset available like IODF cluster file etc and getting below error. 0ADR468E (001)-DDFLT(04), VSAM DATA SET SYS1.IODFD0.WORK.CLUSTER IN CATALOG CATALOG.MASTER.MCAT IS NOT PROCESSABLE 0ADR468E (001)-DDFLT(04), VSAM DATA SET SYS1.IODF00.WORK.CLUSTER IN CATALOG LOG.MASTER.MCAT IS NOT PROCESSABLE 0ADR468E (001)-DDFLT(04), VSAM DATA SET SYS1.IODF01.WORK.CLUSTER IN CATALOG CATALOG.MASTER.MCAT IS NOT PROCESSABLE DR396I (001)-NEWDS(01), DATA SET TCPIP.SEZARNT3 ALLOCATED, ON VOLUME(S): RES001 DR396I (001)-NEWDS(01), DATA SET SYS1.SBLSPNL0 ALLOCATED, ON VOLUME(S): RES001 DR396I (001)-NEWDS(01), DATA SET TCPIP.SEZAINST ALLOCATED, ON VOLUME(S): RES001 DR396I (001)-NEWDS(01), DATA SET TCPIP.SEZATCP ALLOCATED, ON VOLUME(S): RES001 DR801I (001)-DDDS (01), DATA SET FILTERING IS COMPLETE. 262 OF 262 DATA SETS WE FOR OTHER REASONS. DR455W (001)-DDDS (01), *THE FOLLOWING DATA SETS WERE NOT SUCCESSFULLY PROCESSED* *SYS1.IODFD0.WORK.CLUSTER SYS1.IODF00.WORK.CLUSTER SYS1.IODF01.WORK.CLUSTER* DR454I (001)-DDDS (02), THE FOLLOWING DATA SETS WERE SUCCESSFULLY PROCESSED ISF.SISFHELP SYS1.SCUNLOCL TCPIP.SEZAXAWL CEE.SCEESAMP SYS1.SISTASN1 SYS1.SBPXMENUAGE 0011 5695-DF175 DFSMSDSS V1R09.0 DATA SET SERVICES 2011.095 14:07On 4/5/2011 8:33 PM, jagadishan perumal wrote: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]> <mailto:[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]> <mailto:[email protected]>Thanks Richard, I tried using STORAGE CLASS parameter( NOSMS). but still got same error. Now I am searching for the parameteryousuggested. 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] <mailto:[email protected]>] on behalf of McKown, John [[email protected] <mailto:[email protected]>] Sent: 05 April 2011 03:06 PM To:[email protected] <mailto:[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 theparameter:STORAGECLASS(NONSMS) which is tested in the ACS routines to make adatasetnon 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 housewritten.-- 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] <mailto:[email protected]> *www.HealthMarkets.com <http://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 theoriginalmessage. HealthMarkets(r) is the brand name for products underwrittenandissued by the insurance subsidiaries of HealthMarkets, Inc. -TheChesapeakeLife 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] <mailto:[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 [email protected] <mailto:[email protected]> with the message: GET IBM-MAIN INFO Search the archives athttp://bama.ua.edu/archives/ibm-main.html ----------------------------------------------------------------------For IBM-MAIN subscribe / signoff / archive access instructions, send email [email protected] <mailto:[email protected]> with the message: GET IBM-MAIN INFO Search the archives athttp://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email [email protected] <mailto:[email protected]> with the message: GET IBM-MAIN INFO Search the archives athttp://bama.ua.edu/archives/ibm-main.html---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email [email protected] <mailto:[email protected]> with the message: GET IBM-MAIN INFO Search the archives athttp://bama.ua.edu/archives/ibm-main.html---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email [email protected] <mailto:[email protected]> with the message: GET IBM-MAIN INFO Search the archives athttp://bama.ua.edu/archives/ibm-main.html---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email [email protected] <mailto:[email protected]> with the message: GET IBM-MAIN INFO Search the archives athttp://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
