I have always made do with the ISMF ACS test facility and a bevy of test cases. I think Naviquest will let you do this in batch though I never set it up as the on-line ISPF tools were sufficient for my needs.
If you have the luxury a separate test Sysplex and SMSPlex of course. Vendor product? DTS Software has what sounds like a useful test and debugging tool SMS/Debug you might want to look at. http://www.dtssoftware.com/product_sms.htm Might make debugging safer, faster, more productive in a single image. Best Regards, Sam Knutson, GEICO Performance and Availability Management mailto:[EMAIL PROTECTED] (office) 301.986.3574 "Think big, act bold, start simple, grow fast..." -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Neil Duffee Sent: Monday, July 18, 2005 2:33 PM To: [email protected] Subject: [SMS] testing new SCDS configuration Haven't seen any results so I thought I'd give it another go. Anyone willing to pat me on the back and say, "Go for it, sonny," or shake a mighty finger with, "You *stoopid* fool! Don't you know that..." *grin* I'm/we're trying to move to a more sophisticated SMS setup from the basic StorClas->StorGrp we have now and this's the first leap. How do *you* test a new SMS configuration before the production LPar? Again, tks for any help or suggestions... -----> previous message <----- Date: Thu, 30 Jun 2005 15:16:35 -0400 From: Neil Duffee <[log in to unmask]> Looking for opinions/affirmations on my line of thinking for testing a new SCDS configuration. We're z/OS v1.4, z890, & MonoPlex'd but all the LPar's are in a single SMSPlex ie. sharing COMMDS & ACDS. I've got a major change in both SCDS & ACS which I've hand & batch (NaviQuest) checked over & again but would love to try a live test. >From the single hint in the Storage Admin Ref, "If the COMMDS and ACDS are different from the ones used by the remainder of the SMS complex, then the system runs as a separate SMS complex." then I should be able to, in one fell swoop, issue: SETSMS COMMDS(new) ACDS(new) SCDS(new) - 'cept that COMMDS is exclusive of other all other parms. So I'm thinkin' that, in the testing LPar, I need to: 1 allocate new, empty COMMDS & ACDS 2 SETSMS SAVEACDS(new) 3 create SYS1.PARMLIB(IGDSMSnew) listing both the new ACDS & COMMDS 4 SET SMS=new - starts a 'new' SMSplex containing only this 'test' LPar 5 SETSMS SCDS(new) - activates the new configuration in the 'new' ACDS - should *not* affect any other LPar (different SMSplex) 6 test the snot out of it before trying it on production My biggest worry is that the other LPars might pick up the configuration change; production 'specially. Tks for all hints, warnings, and suggestions. ----------> signature = 6 lines follows <-------------- Neil Duffee, Joe SysProg, U d'Ottawa, Ottawa, Ont, Canada telephone:1 613 562 5800 x4585 fax:1 613 562 5161 mailto:NDuffee of uOttawa.ca http:/ /aix1.uottawa.ca/ ~nduffee "How *do* you plan for something like that?" Guardian Bob, Reboot "For every action, there is an equal and opposite criticism." "Systems Programming: Guilty, until proven innocent" John Norgauer 2004 <> ==================== This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. ---------------------------------------------------------------------- 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
