Re: SMP/E change volumes on DDDEF in new Target Zone
I always something similar to what Ed did. On the target packs, which I always called ALTRS1 ALTRS2, no datasets were catalogued. The DDDEFs pointed to them. On the RES packs, the datasets were catalogued. I clipped the ALTres packs the day before IPLing. I always thought that it was faster to allocate fewer ISPF datasets when you logged on. I merged all of the panels into SYS1.ISPPLIB, Skels into ISPSLIB, etc. I actually changed the DDDEFs to point to those libraries on the ALTres pacs, so SMP handled everything. I had one set of IBM SYS1.ISP librarys, and one set of program product libraries that where SYS2.ISP. Of course, if I ever find a job as a sysprog again, if the new company I work for likes the way they do ISPF libraries, I'll leave it. If they like my ideas, then I'll change it. Eric Bielefeld Sr. z/OS Systems Programmer Milwaukee, Wisconsin 414-475-7434 - Original Message - From: Ed Gould [EMAIL PROTECTED] Paul, I have never cataloged DLIB type datasets . At least in my case, I don't catalog any non operational datasets. Which ones are those? There is not hard and fast rules other than if nobody should be referencing the datasets then they aren't cataloged. One example that comes to mind are the ICQ (TSO) datasets. Frankly I have never found a use for them, so if I can't find a use then neither can an applications type can (unless they can show me a need). I have yet to run into any person that *needs* them. Call me a hard a** but if I have to support them then I need to know what the user is doing. I do this with almost all non sys1 type datasets the one big exception are the ISR and ISP (ISPF) datasets. Those get renamed to sys1.isrplib etc. for all to have read access to. I am just skimpy with any datsets that are delivered from IBM. If the user needs access then the datasets are cataloged otherwise they are not. Yes it is a little bit of work at install time, but I have felt the need to be vary careful what I give out access to, if they aren't cataloged then the user has to work just a little bit harder to sneak around looking. They also just can't browse them as I don't give out read access either. Ed -- 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
Re: SMP/E change volumes on DDDEF in new Target Zone
On Thu, 8 Nov 2007 09:57:47 -0600, Paul Gilmartin [EMAIL PROTECTED] wrote: On Wed, 7 Nov 2007 11:37:15 -0500, Pinnacle wrote: Run the UNLOAD command to get the DDDEF's in UCLIN format. Then you'll have to hack the UCLIN yourself to add VOLUME and UNIT parms, and run the UCLIN through SMP/E. What data sets will SMP/E create NEW? SYSUT1-4, SMPWRK1-6 (SMPWRK5 no longer used IIRC). I guess SMPPUNCH or any of the sysout DDs could be, but they really should be MOD if DASD. I have seen SMPLOG/SMPLOGA allocated as new also when people don't care about keeping the logs or just from vendors who provide samples and just don't know better. If SMP/E creates the data sets, must SPACE be specified also? Defaults taken from the system (ALLOCxx, SMS), so no but you most likely want to. Is UNIT necessary? Won't SMP/E or DYNALLOC infer the UNIT from a default if VOLSER is specified? If you use UNIT you need VOLSER as far as I know. Just like you do with JCL. If the data sets are created by some other mechanism prior to SMP/E, won't SMP/E obtain the VOLUME and UNIT from the catalog? If you use DISP=OLD or SHR. Why would anyone ever use uncatalogued data sets? Typically for MVS maintenance SMP/E zones to access something other than the running system. But I have seen it done for vendor products also (even non SYSRES). Obviously this doesn't work for SMS controlled DSNs. If I am designing sample JCL/UCLIN for customers, should I provide VOLUME (and UNIT) templates in the UCLIN? I'd supply VOL=SER= in JCL, but commented out. I'd supply UNIT as a SET symbol. What granularity of VOLUME would customers desire: o A different VOLUME for each zone? Typically by zone / type (for those that aren't using SMS for the whole thing).Also, some prefer to have the SMP/E dsns as there own HLQ / volsers, so that can be separate. TGTVOL TGTUNIT TGTHLQ DLBVOL DLBUNIT DLBHLQ SMPVOL SMPUNIT SMPHLQ That should give most shops the flexibility they need. But you should also have something for STORCLAS in your allocation JCL samples for those that SMS control the HLQs because volume will be ignored. Since most people deal with cataloged data sets for ISV software, having UNIT / VOLSER in the DDDEFs can be comments and SHR or OLD would work. o A different VOLUME for each data set? No. But that could happen with SMS control, but who cares. o Should VSAM be separated from PS from PDS from PDSE? Only VSAM are the SMP/E zones. Covered above. Prior to non-SMS PDSE it made sense to possibly keep that separate. Now, it doesn't matter. I assume if someone has HLQ=whatever and VOLSER=whatever for all the other data sets (if not under SMS control), they want them all in the same place. I know I do. HTH, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: SMP/E change volumes on DDDEF in new Target Zone
On Wed, 7 Nov 2007 11:37:15 -0500, Pinnacle wrote: Run the UNLOAD command to get the DDDEF's in UCLIN format. Then you'll have to hack the UCLIN yourself to add VOLUME and UNIT parms, and run the UCLIN through SMP/E. What data sets will SMP/E create NEW? If SMP/E creates the data sets, must SPACE be specified also? Is UNIT necessary? Won't SMP/E or DYNALLOC infer the UNIT from a default if VOLSER is specified? If the data sets are created by some other mechanism prior to SMP/E, won't SMP/E obtain the VOLUME and UNIT from the catalog? Why would anyone ever use uncatalogued data sets? If I am designing sample JCL/UCLIN for customers, should I provide VOLUME (and UNIT) templates in the UCLIN? I'd supply VOL=SER= in JCL, but commented out. I'd supply UNIT as a SET symbol. What granularity of VOLUME would customers desire: o A different VOLUME for each zone? o A different VOLUME for each data set? o Should VSAM be separated from PS from PDS from PDSE? Etc. Thanks, gil -- 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
Re: SMP/E change volumes on DDDEF in new Target Zone
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. (psusing 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 DownloadsUtility 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() VOLUME(vv). 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
Re: SMP/E change volumes on DDDEF in new Target Zone
Why would anyone ever use uncatalogued data sets? Multiple SMP/E zones with the same named datasets on different volume sets. One could use an alias (like the SSAs that server pac generates), but I prefer to know that when I set a boundary to a particular zone, that the right set of data sets managed by that zone get updated. Using DDDEFS with volume and unit coded guarantee this. I'd hate to accidentally update the running SYS1.LINKLIB (obviously cataloged) when I really wanted the SYS1.LINKLIB on a volume that isn't the current IPL volume! Tom Chicklon -- 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
Re: SMP/E change volumes on DDDEF in new Target Zone
Hi Gil, Of course we want/need uncataloged datasets for our target datasets. At present in my sandbox, I am supporting 3 different levels of our IPL res set as targets, and 3 different versions as active IPL res setsthat gives me 6 sets of duplicated datasets. It is far simpler to use uncataloged SMP/E target datasets, with UNIT and VOL specified on the DDDEF, than the alternative use of ALIAS entries. Much less chance of ALIAS entries getting broken. K.I.S.S. :-) On Thu, 8 Nov 2007 09:57:47 -0600, Paul Gilmartin [EMAIL PROTECTED] wrote: snip Why would anyone ever use uncatalogued data sets? snip Thanks, gil 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
Re: SMP/E change volumes on DDDEF in new Target Zone
On Nov 8, 2007, at 9:57 AM, Paul Gilmartin wrote: ---SNIP--- Why would anyone ever use uncatalogued data sets? -SNIP- Paul, I have never cataloged DLIB type datasets . At least in my case, I don't catalog any non operational datasets. Which ones are those? There is not hard and fast rules other than if nobody should be referencing the datasets then they aren't cataloged. One example that comes to mind are the ICQ (TSO) datasets. Frankly I have never found a use for them, so if I can't find a use then neither can an applications type can (unless they can show me a need). I have yet to run into any person that *needs* them. Call me a hard a** but if I have to support them then I need to know what the user is doing. I do this with almost all non sys1 type datasets the one big exception are the ISR and ISP (ISPF) datasets. Those get renamed to sys1.isrplib etc. for all to have read access to. I am just skimpy with any datsets that are delivered from IBM. If the user needs access then the datasets are cataloged otherwise they are not. Yes it is a little bit of work at install time, but I have felt the need to be vary careful what I give out access to, if they aren't cataloged then the user has to work just a little bit harder to sneak around looking. They also just can't browse them as I don't give out read access either. Ed -- 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
Re: SMP/E change volumes on DDDEF in new Target Zone
Here is an extract from an EDIT macro that I wrote to generate DDDEF UCLIN from
*any* dataset that had the DATASET as the first word and then the VOLSER as the
2nd word (it uses the llq as the DDDEF name).
address ISREDIT MACRO
/*---*/
/* Option 4 : SMP/E DDDEF Statements */
/*---*/
address ISREDIT (NUMLINES) = LINENUM .ZLAST
i = 1
c = 1
do until c numlines
address ISREDIT (LINEDATA) = LINE i
dsn = word(linedata,1)
vol = word(linedata,2)
unt = SYSALLDA
z = lastpos('.',dsn)
ddc = substr(dsn,z+1,8)
newline = REP DDDEF (ddc)
address ISREDIT LINE i = 'newline'
newline = SHR .
address ISREDIT LINE_AFTER i = 'newline'
newline = UNIT(unt) VOLUME(vol)
address ISREDIT LINE_AFTER i = 'newline'
newline = DATASET(dsn)
address ISREDIT LINE_AFTER i = 'newline'
i = i + 4
c = c + 1
end
end
exit
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 Mark
Zelden
Sent: 07 November 2007 16:45
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: SMP/E change volumes on DDDEF in new Target Zone
On Wed, 7 Nov 2007 10:40:47 -0600, Mark Zelden [EMAIL PROTECTED] wrote:
UCLIN.
REP DDDEF(nn) VOLUME(vv).
ENDUCL.
Of course if you add volume you will need unit also.
UCLIN.
REP DDDEF(nn) VOLUME(vv) UNIT(SYSALLDA).
ENDUCL.
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead Zurich North America /
Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems
Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: SMP/E change volumes on DDDEF in new Target Zone
On Wed, 7 Nov 2007 10:40:47 -0600, Mark Zelden [EMAIL PROTECTED] wrote: UCLIN. REP DDDEF(nn) VOLUME(vv). ENDUCL. Of course if you add volume you will need unit also. UCLIN. REP DDDEF(nn) VOLUME(vv) UNIT(SYSALLDA). ENDUCL. -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: SMP/E change volumes on DDDEF in new Target Zone
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. UCLIN. REP DDDEF(nn) VOLUME(vv). ENDUCL. Or you can SET BOUNDARY (zonename). UNLOAD DDDEF. And massage the UCLIN it creates and run it back in. 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. Sorry... no help for that unless you RYO. If the HLQ is unique, an ISPF 3.4 listing and a SAVE mylist command might help along with the DDDEF unload. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.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
Re: SMP/E change volumes on DDDEF in new Target Zone
- Original Message - From: Mark S. House [EMAIL PROTECTED] Newsgroups: bit.listserv.ibm-main Sent: Wednesday, November 07, 2007 10:27 AM Subject: SMP/E change volumes on DDDEF in new Target Zone 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. Mark, Run the UNLOAD command to get the DDDEF's in UCLIN format. Then you'll have to hack the UCLIN yourself to add VOLUME and UNIT parms, and run the UCLIN through SMP/E. Regards, Tom Conley -- 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
Re: SMP/E change volumes on DDDEF in new Target Zone
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 DownloadsUtility 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() VOLUME(vv). 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 [EMAIL PROTECTED] This e-mail message and any attachments may contain confidential, proprietary or non-public information. This information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this e-mail are those of the author personally. -- 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
SMP/E change volumes on DDDEF in new Target Zone
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 [EMAIL PROTECTED] This e-mail message and any attachments may contain confidential, proprietary or non-public information. This information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this e-mail are those of the author personally. -- 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
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() VOLUME(vv). 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 [EMAIL PROTECTED] This e-mail message and any attachments may contain confidential, proprietary or non-public information. This information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this e-mail are those of the author personally. -- 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
Re: SMP/E change volumes on DDDEF in new Target Zone
UCLIN There is a dump of the DDDEF's, you can bring that into ISPF, add the volume, then run it back thru UCLIN. At 10:27 AM 11/7/2007, Mark S. House 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 [EMAIL PROTECTED] This e-mail message and any attachments may contain confidential, proprietary or non-public information. This information is intended solely for the designated recipient(s). If an addressing or transmission error has misdirected this e-mail, please notify the sender immediately and destroy this e-mail. Any review, dissemination, use or reliance upon this information by unintended recipients is prohibited. Any opinions expressed in this e-mail are those of the author personally. -- 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 Brian W. France Systems Administrator (Mainframe) Pennsylvania State University Administrative Information Services - Infrastructure/SYSARC Rm 25 Shields Bldg., University Park, Pa. 16802 814-863-4739 [EMAIL PROTECTED] To make an apple pie from scratch, you must first invent the universe. Carl Sagan -- 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
