Bob, IMO going back and updating JCL seems like a lot of work. As Ted says, the ISV products are designed to work with SMS and non-SMS data sets. These X37 and allocation ISV products were around long before DFSMS and are pretty good at what they do. As I stated already, many of the recovery actions that these products perform are actually more efficient than DFSMS. What happens in the future after you have removed VAM when the application grows and your JCL changes are no longer adequate enough; BAM! JCL, X37 abend. This condition would be true for other permanent data sets as well. I've been using the StopX37/EasyPOOL product since I got into IT back in 1989 and could not do without it (I installed DFSMS in 1991). I let DFSMS do it's thing where appropriate, and StopX37/II where appropriate. Plus StopX37/II does work that DFSMS does not perform.
Michael Spencer -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Lester, Bob Sent: Tuesday, January 20, 2009 5:22 PM To: IBM-MAIN@bama.ua.edu Subject: Re: SMS and System Temporary Datasets Hi Ted, I do have other SMS-managed data. I'm just doing the conversion a bit backwards. ;-) I can see that the issue, in my current environment, is that I tell VAM (CA-Allocate) to bail out of it's ASR (EXIT CODE(0)) if it sees a non-null Storage Class. We are hoping to be able to eliminate VAM from the mix. My intent with the "extent problem" is to identify which dsns are being twiddled by VAM and (for System Temporary dsns) update the space allocation in the JCL. For permanent dsns being change by VAM, I can either change the JCL to specify data class, or let SMS just add additional volumes. Thanks for the reply! Sounds like SMS-managed System Temporary files is a good thing. BobL > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ted MacNEIL > Sent: Tuesday, January 20, 2009 2:15 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: SMS and System Temporary Datasets > > >My options seem to be: > >1) plow thru all System Temporary allocations being increased by > >CA-Allocate and update the JCL, or > >2) Leave System Temporary datasets non-SMS. > > At the risk of repeating myself, what makes you think these are > mutually exclusive? > Are you assuming that you can't do both in an SMS environment? You > can. > Are you assuming SMS will manage the 'extent problem', and you can get > rid of the product? You can't. > > - > Too busy driving to stop for gas! > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@bama.ua.edu with the > message: GET IBM-MAIN INFO Search the archives at > http://bama.ua.edu/archives/ibm-main.html > > ------------------------------------------------------------------------ ------ This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. OppenheimerFunds may, at its sole discretion, monitor, review, retain and/or disclose the content of all email communications. ======================================================================== ====== ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
