Just an update.
IBM has taken the requirement for this issue. If you would like to join the
party, the number is MR0305136942.
Text is:
Add SHCDS Dataset Location Retention
.
Description
-----------
Currently, if the couple data set is lost, redefined or corrupted, the
RLS SHCDS data sets must be manually re-added via the
VARY SMS,SHCDS(SHCDS_name),NEW and NEWSPARE commands. (See info APAR
ii14191 for more detail). Adding and/or changing these data sets is
not a common practice, so in the case of a lost couple data set,
determining where they were located after a long duration is not
necessarily a fast or straightforward process. This requirement aims
to have the information retained in a logical, secondary place outside of
the couple data set so that it can be easily retrieved and re-added.
.
Suggested Solution
------------------
Keep the information in the IGDSMSxx or COUPLxx parmlib member.
.
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf
> Of Jerry Whitteridge
> Sent: Tuesday, March 05, 2013 1:15 PM
> To: [email protected]
> Subject: Re: RLS SMSVSAM and PLEX wide IPL
>
> Yes - This was a surprise when it bit.
>
> Bit more happened in the background than Lizette explained. This was not
just a
> Sysplex wide IPL, but move to new hardware involving new Couple and CFRM
datasets
> with no ability to move gracefully.
>
> However when the review for all the Sysplex JCL members etc. were done
there was
> no indication that the information was ONLY stored in the Sysplex Couple
Dataset. (The
> team that implemented RLS and had any knowledge of the setup unfortunately
is no
> longer available for questions). Obviously doc will now be placed in the
critical info
> locations we use for the Sysplex - but that is after the fact. In no other
Sysplex
> configuration item is there something set via command and no parms left
behind as
> documentation.
>
> Jerry Whitteridge
> Lead Systems Programmer
> Safeway Inc.
> 925 951 4184
>
> If you feel in control
> you just aren't going fast enough.
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf
> Of Skip Robinson
> Sent: Monday, March 04, 2013 4:25 PM
> To: [email protected]
> Subject: Re: RLS SMSVSAM and PLEX wide IPL
>
> 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
