Mark, I wrote some similar REXX last December, during our end of year change freeze.
Because of our procedures/standards, I know the VOLSER format of all our target/dlib/smpe volumes. Passing a volser mask for target and dlib volumes, and knowing the standard smpe volsers, the code finds all eligble online volumes, uses IEHLIST to get a vtoclist of all datasets on these volumes. All SMPE CSI datasets comply to our naming standards, so the exec can locate and identify all zones. Calling SMPE internally the REXX can retrieve all the DDDEF information. Comparing dataset names, dddef volume names, and what is found on disk, the code can verify all the DDDEF values in all zones. Where the code can positively identify re-located datasets the exec generates a UCLIN job to correct them The various reports can be edited externally, and then UCLIN JCL can be auto generated using some simple ISPF Edit Macros. And since our standards say all datasets on the target and dlib volumes are SMPE managed, we also list out all datasets found with no matching DDDEF. Having all DDDEF information externalised into a single sequential dataset allows for global standards to be inplemented easily. (ps....using this FIXDDDEF exec as a model, I also now have lists of all FMIDS, PTFS, APARs, USERMODs externalised. These lists have been a great resource for our teams). On Wed, 7 Nov 2007 11:01:49 -0500, Rob Scott <[EMAIL PROTECTED]> wrote: >Mark, > >Can I also suggest that you try out my free DDDEFCHK utility that I wrote when I was a sysprog. > >It uses the SMP/E API to get the list of DDDEFs and then tests for the dataset existance of each. > >If the DDDEF entry has a VOLUME - it will check that the dataset does indeed exist on the volume. >If no VOLUME was specified - the utility returns the volser indicated by the catalog. > >You can download it from : www.mximvs.com under the "Downloads>Utility Programs" section. > >There is also a DDDEFPTH program too that does a similar thing for PATH entries. > >I used this programs extensively when I was in clone-CSI mode. > > >Rob Scott >Rocket Software, Inc >275 Grove Street >Newton, MA 02466 >617-614-2305 >[EMAIL PROTECTED] > > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Peter X. DeFabritus >Sent: 07 November 2007 15:53 >To: IBM-MAIN@BAMA.UA.EDU >Subject: Re: SMP/E change volumes on DDDEF in new Target Zone > >If no VOLUME currently exists, you can do the following for each DDDEF: > >UCLIN. >ADD DDDEF(xxxxxxxx) VOLUME(vvvvvv). >ENDUCL. > >This will add the volume to the existing DDDEF. > > >On Wed, 7 Nov 2007 09:27:24 -0600, Mark S. House <[EMAIL PROTECTED]> wrote: > >>I am cloning a target region for maintenance. I would like to find a >>utility that will insert a VOLSER in the VOLUME parameter on the DDDEF. >>Currently none of the DDDEF's have volsser numbers in them. The >>ZONEDIT CHANGE command will not let me do a global change on VOLUME >>when the VOLUME is nulls. >> >>Ideally, what I would like to do is search the catalog for the dataset >>name on the DDDEF, then extract the volser, and build REP DDDEF >>statements to be used to update the new target library. >> >>Any help would be appreciated. Thanks. >> >> >>Mark House >>(402) 778-1966 >>IBM Mainframe Systems <snip>. Regards Bruce Hewson ---------------------------------------------------------------------- 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
