Skip/Mark Thanks for the input.
My concern is the young ones coming up will not be able to understand the diagnostics when a new couple dataset is created. Which I agree are rare. IBM used a very old technique for the RLS datasets (I am not sure when RLS came into play). But the fact that 1) You must use the prefix SYS1.DFPSHCDS and end with the VOLSER the dataset resides on 2) You must know to use the V SMS,SHCDS(dsname) command when they go missing Is a little old school for the next generation. I prefer that parms be available so that when something goes missing, you have a good starting place to look. I think I will go ahead with the SHARE requirement and see how it goes Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf > Of Skip Robinson > Sent: Monday, March 04, 2013 10:42 AM > To: [email protected] > Subject: Re: RLS SMSVSAM and PLEX wide IPL > > I'm with Mark on the unlikely impact of CPU upgrade on couple data sets. > We went through a full push-pull upgrade in 2008 and another one-by-one push-pull in > 2012. As long as the IODF is coded properly and recabling performed correctly, there > should be no loss of access to any previously defined volume. > > However, I'm also sympathetic to Lizette's complaint about the severe effect of losing > all share control data sets. Our biggest user of RLS is HSM, which IIRC will not come up > if RLS is broken. IPLing without HSM can be a nasty swim in the swamp. Providing an > emergency definition in PARMLIB a la CFRMPOL parameter in COUPLExx might be a day > saver. > > . > . > JO.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > [email protected] > > > > From: Mark Zelden <[email protected]> > To: [email protected], > Date: 03/04/2013 07:55 AM > Subject: Re: RLS SMSVSAM and PLEX wide IPL > Sent by: IBM Mainframe Discussion List <[email protected]> > > > > On Sun, 3 Mar 2013 01:32:26 -0700, Lizette Koehler > <[email protected]> wrote: > > >We upgraded the CPU this weekend, and SMSVSAM would not come up. > > > >We got the IGW611a and IGW609A messages > > > >After a bit of investigation, I did the V SMS,SHCDS(xxx),NEW putting back > >the Prim/Sec/Spare files. > > > >There were no issues with the definition and the only changes were > >un-cabling/re-cabling the DASD from the old CPU to the new CPU and IPLing > >with new CF datasets. > > > >I am curious if when there is a PLEX wide IPL (All Lpars down at the same > >time then IPL one at a time up) if there is some way to prevent the loss > of > >the SHCDS data set names? > > > >Any thoughts? > > > >My hunts through the manuals and internet is not providing much detail on > >PLEX wide IPLs and SHCDS datasets > > > > New CF (CFRM) couple data sets or new SYSPLEX (XCF) couple data sets? The > names are stored in the sysplex couple ds. But you shouldn't replace > either > for a CPU upgrade. > > -- > Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
