Re: SMPE DDDEF modify Issue

2014-09-04 Thread Mainframe Mainframe
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mainframe Mainframe Sent: Wednesday, 3 September 2014 6:06 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: SMPE DDDEF modify Issue We have two copies of RES volume. Primary and Secondary in our z/OS 1.13 systems.While setting up SMPE

SMPE DDDEF modify Issue

2014-09-03 Thread Mainframe Mainframe
We have two copies of RES volume. Primary and Secondary in our z/OS 1.13 systems.While setting up SMPE initially, we always make sure that SMPE DDDEF of target dataset should point to only Alternate RES volume and we always run system with primary RES volume. So, while applying Maintenance new

Re: SMPE DDDEF modify Issue

2014-09-03 Thread Andy Taylor
Hello Not quite sure why you think you can't update a single DDDEF entry, but is it because you're looking at the ZONEEDIT command as opposed to the UCLIN command? UCLIN will allow you to update a single DDDEF entry. Regards Andy T. On 3 Sep 2014, at 09:36, Mainframe Mainframe

Re: SMPE DDDEF modify Issue

2014-09-03 Thread Mainframe Mainframe
Thanks for reply. But I am not looking for single DDDEF entry. I want to update all target dataset DDDEF using single JCL. I don't want to do it manually. As this will consume lots of time. On Wed, Sep 3, 2014 at 2:42 PM, Andy Taylor a...@purplemongoose.co.uk wrote: Hello Not quite sure why

Re: SMPE DDDEF modify Issue

2014-09-03 Thread Andy Taylor
Ok, I believe I understand. In which case, are the DDDEFs for the target libraries the only DDDEFs in your target zone with VOLUME pointing at your sysres? If so can't you use ZONEEDIT with a conditional? (SMP/E Commands Manual has an example). Regards Andy T. On 3 Sep 2014, at 10:21,

Re: SMPE DDDEF modify Issue

2014-09-03 Thread Mainframe Mainframe
Yes. But the issue is.. if I set boundary to TARGET zone then all dataset under target zone ( target and distribution ) both volume will be changed, which I dont want. I want to change only for Target dataset. On Wed, Sep 3, 2014 at 3:02 PM, Andy Taylor a...@purplemongoose.co.uk wrote: Ok, I

Re: SMPE DDDEF modify Issue

2014-09-03 Thread Andy Taylor
Yes, I understand that. And so you need to differentiate the DDDEFs for target libraries from the DDDEFs for dlib libraries and other datasets. Which is why I asked if it is only the target libraries that have VOLUME pointing to the sysres. From the SMP/E Commands Manual there is the

Re: SMPE DDDEF modify Issue

2014-09-03 Thread Juergen Keller
Hi, maybe this helps: //UNLOAD EXEC PGM=GIMSMP,REGION=4M, //PARM='CSI=csi,PROCESS=END' //SMPPUNCH DD DSN=dataset,UNIT=SYSDA, // DISP=(NEW,CATLG),SPACE=(TRK,(1,1)), // DCB=(LRECL=80,RECFM=FB)

Re: SMPE DDDEF modify Issue

2014-09-03 Thread Kurt Quackenbush
On 9/3/2014 6:15 AM, Andy Taylor wrote: ... And so you need to differentiate the DDDEFs for target libraries from the DDDEFs for dlib libraries and other datasets. Which is why I asked if it is only the target libraries that have VOLUME pointing to the sysres. The ZONEEDIT command has no

Re: SMPE DDDEF modify Issue

2014-09-03 Thread Staller, Allan
See the ZONEEDIT SMP/E command snip We have two copies of RES volume. Primary and Secondary in our z/OS 1.13 systems.While setting up SMPE initially, we always make sure that SMPE DDDEF of target dataset should point to only Alternate RES volume and we always run system with primary RES

Re: SMPE DDDEF modify Issue

2014-09-03 Thread Anthony Thompson
DDDEF modify Issue We have two copies of RES volume. Primary and Secondary in our z/OS 1.13 systems.While setting up SMPE initially, we always make sure that SMPE DDDEF of target dataset should point to only Alternate RES volume and we always run system with primary RES volume. So, while applying