Luckily this isn't z/OS. It's a couple 3rd party products. I do apply to both target zones.
The only library with members is SCDS. Does that mean that I'm only potentially in trouble if I need to do a RESTORE? Luke -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Joel C. Ewing Sent: Monday, March 15, 2010 11:19 PM To: IBM-MAIN@bama.ua.edu Subject: Re: SMP/E datasets question If you have done SMP/E apply against both target zones, then there is no guaranteed fix. For example, if there are members in MTS or STS that both target zones think they "own", ACCEPTing the maintenance in one zone will move those members into the appropriate DZONE DLIBs and remove them from MTS or STS (might be some options to prevent the delete, not sure), and a latter attempt to accept related sysmods in the other target zone wouldn't find the members. If you only do SMP/E maintenance against a "test" target zone, then clone the Tzone and TLIBS to install in production and never use SMP/E for APPLY/ACCEPT/RESTORE against the "production" clone TZone, then you don't really have a problem because the libraries at issue are only used during maintenance (possibly could/should delete their DDDEFs in the production Tzone in this case). If you use SMP/E to APPLY to both target zones, then there would always be the risk of unintentionally doing things out of order in a way that SMP/E would think legit but that could cause corruption because of the shared target datasets. If you have been doing SMP/E APPLY to both target zones and accepting maintenance for an extended period while running with MTS/STS/LTS/SCDS shared, depending on what usage was made of the shared datasets and the order in which things were done, you could already have corrupted members in some of your TLIBS and DLIBs. Perhaps not, but actually proving the absence of adverse side effects would be very difficult: The only sure method is to start with a fresh install and re-apply to the current level of maintenance. If you use SMP/E to APPLY to both target zones and are in the resulting "unknown" SMP/E status and don't have the resources for a z/OS re-install, I would be tempted to clone separate copies of the existing MTS/STS/SCDS/LTS libraries for the other target zone, hope there has been no serious damage yet, and gamble that things hang together long enough until a migration to the next release of z/OS, where you can then be sure to observe correct practices with the new zones. JC Ewing On 03/15/2010 01:20 PM, Rabbe, Luke wrote: > I only have one CSI that contains all zones. The SMP SCDS, LTS, MTS, and STS > are the same for all target zones. Each target zone has its own target > libraries. > Do any of these details change your assessment? > > I have a production and test target zone. Can I ACCEPT, delete the test > target zone, clear the SMP/E datasets, and make a fresh clone? Will that > straighten me out? > > Luke > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf > Of Mark Zelden > Sent: Monday, March 15, 2010 12:03 PM > To: IBM-MAIN@bama.ua.edu > Subject: Re: SMP/E datasets question > > On Mon, 15 Mar 2010 11:29:20 -0500, Rabbe, Luke > <luke.ra...@countryfinancial.com> wrote: > >> The SMP/E User's Guide states: >> >> ...each SCDS is directly related to a specific target zone, and each target > zone must have its own SCDS. >> >> It also says this about the MTS, STS, and LTS. >> >> Why is that? I have a couple SMP/E environments with multiple target zones > and only one set of SMP/E datasets. >> > > So do the DDDEFs or APPLY JCL you have used for the other zones share > those same data sets between target zones? If so, then you probably have > a corrupt environment. The LTS may be empty or not used, or even if it > is you can just delete everything from it and allocate separate ones per > zone. The SCDS, MTS and STS - not so. Another possibility is you > only apply to one and clone the other zones, if so, you are also fine, but > the cloning process for a target zone should also clone those 4 data sets > along with the VSAM CSI and the product(s) target data sets. > > Mark > -- > Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS > mailto:mzel...@flash.net > Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html > Systems Programming expert at http://expertanswercenter.techtarget.com/ ... -- Joel C. Ewing, Fort Smith, AR jremoveccapsew...@acm.org ---------------------------------------------------------------------- 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
