We've been doing RLS for lonnnnng time. I was always a bit uncomfortable that command interface was all we had. Even if PARMLIB contained only a backup set to satisfy SMS, we'd be way ahead of the game.
. . 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: Lizette Koehler <[email protected]> To: [email protected], Date: 03/04/2013 03:44 PM Subject: Re: RLS SMSVSAM and PLEX wide IPL Sent by: IBM Mainframe Discussion List <[email protected]> This situation only shows up with brand new CDS environment. So if you create new Couple datasets, then you lose the knowledge of the SHCDS datasets used by RLS. I am so sure running a VARY command at IPL time is an appropriate correction. I think monitoring for the IGW611A message and then validating/taking action would be better. We are going to setup an OPS/MVS rule to do this should we do this again. In the meantime, I have engaged IBM and they have agreed that this would probably be a good change request. So, I will let the list know what the APAR name is, should you wish to watch for its closing. Either IGDSMSxx or COUPLExx will be modified, I think. Probably IGDSMSxx My concept is the names be placed in IGDSMSxx along with the RLSINIT(YES) parm. Then the process could 1) Verify they exist, and if they do continue 2) If they do not exist or are invalid, issue a message. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf > Of Mike Schwab > Sent: Monday, March 04, 2013 4:17 PM > To: [email protected] > Subject: Re: RLS SMSVSAM and PLEX wide IPL > > Could they be added to **.PARMLIB member: > COMMNDxx: Commands to be issued by the control program immediately after > initialization. JES commands may not be included. > > If they can, would they be superfluous if the Coupling datasets were already up? > Alternative would be a separate member with these added for the 1st IPL after starting > with empty coupling datasets. > > On Mon, Mar 4, 2013 at 3:02 PM, Lizette Koehler <[email protected]> wrote: > > 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 > > > -- > Mike A Schwab, Springfield IL USA > Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
