Re: SMSVSAM Sharing control data set - delete and activate

2011-04-14 Thread Skip Robinson 
I'm not currently in a position to look this up in a manual, but in 
general parallel sysplex configurations do not require system outages to 
modify, nor are such outages commonly advised. While the procedure you 
outline may work, I'd explore doing your migration dynamically with no 
outages at all.

-- Migrate to new SHRCDS nondisruptively vis OS commands
-- IPL a new sysplex member nondisruptively

The biggest strength of doing these things dynamically is that if 
something is wrong, you get an error message, and life goes on. When you 
implement changes at IPL, problems may well cause IPL to fail. 

.
.
JO.Skip Robinson
SCE Infrastructure Technology Services
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com



From:   "Buckton, T. (Theo)" 
To: IBM-MAIN@bama.ua.edu
Date:   04/14/2011 04:36 AM
Subject:SMSVSAM Sharing control data set - delete and activate
Sent by:IBM Mainframe Discussion List 



Please advise:

We need to activate new sharing control data sets for SMSVSAM. Our plan
is:
- terminate the SMSVSAM address space
- delete the active and space shcds (v sms,smsvsam(shscds),delete
- IPL the machine (reason: new lpar is added to the sysplex)
-activate the new shcds on current and new lpar.
- display the SMSVSAM address space.

 Please confirm if these steps are correct and in the correct sequence.

Regards
Theo



--
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

Re: SMSVSAM Sharing control data set - delete and activate

2011-04-17 Thread Ambat Ravi Nair 
read the relevant IBM's SMS manuals first, Theo.

just like altering SYS1.MANx or SYS1.DUMPx datasets, you ADD first, DELETE
thereafter.

another (terrible) alternative is to get the Sysplex CFRM CDS redefined.
this will force SMSVSAM to request re-registration of the SHCDS - the impact
of this action is Sysplex-wide.


- ravi.


On Thu, 14 Apr 2011 13:30:30 +0200, Buckton, T. (Theo)
 wrote:

>Please advise:
>
>We need to activate new sharing control data sets for SMSVSAM. Our plan
>is:
>- terminate the SMSVSAM address space
>- delete the active and space shcds (v sms,smsvsam(shscds),delete
>- IPL the machine (reason: new lpar is added to the sysplex)
>-activate the new shcds on current and new lpar.
>- display the SMSVSAM address space.
>
> Please confirm if these steps are correct and in the correct sequence.
>
>Regards
>Theo

--
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

Re: SMSVSAM Sharing control data set - delete and activate

2011-04-18 Thread Buckton, T. (Theo) 
SYSNAME:   ... 
SYSNAME:   ... 

DISPLAY SMS,SMSVSAM - LOCK TABLE STATUS
FOR STRUCTURE  IGWLOCK01   
  CONNECT STATUS:  
SYSNAME:  D0A1 ACTIVERSN:  RbldNotActive   
SYSNAME:  D0A0 ACTIVERSN:  RbldNotActive   
SYSNAME:  D0E0 FAILED PERSISTANT RSN:  
SYSNAME:   . RSN:  
SYSNAME:   . RSN:  
SYSNAME:   . RSN:  
SYSNAME:   . RSN:  
SYSNAME:   . RSN:  
   
  COMPOSITE STATUS:
ORIGINAL STRUCTURE: NOT VOLATILE   FAILURE ISOLATED

STRUCTURE STATUS: 
  SYSNAME: D0A1  Simplex ENABLE3  
  SYSNAME: D0A0  Simplex ENABLE3  
  SYSNAME: D0E0  NOT CONN..   
  SYSNAME:   ... ..   
  SYSNAME:   ... ..   
  SYSNAME:   ... ..   
  SYSNAME:   ... ..   
  SYSNAME:   ... ..   


 Anyone that can assist as what we're doing wrong here?

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
Behalf Of Skip Robinson
Sent: 14 April 2011 04:49 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: SMSVSAM Sharing control data set - delete and activate

I'm not currently in a position to look this up in a manual, but in 
general parallel sysplex configurations do not require system outages to

modify, nor are such outages commonly advised. While the procedure you 
outline may work, I'd explore doing your migration dynamically with no 
outages at all.

-- Migrate to new SHRCDS nondisruptively vis OS commands
-- IPL a new sysplex member nondisruptively

The biggest strength of doing these things dynamically is that if 
something is wrong, you get an error message, and life goes on. When you

implement changes at IPL, problems may well cause IPL to fail. 

.
.
JO.Skip Robinson
SCE Infrastructure Technology Services
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com



From:   "Buckton, T. (Theo)" 
To: IBM-MAIN@bama.ua.edu
Date:   04/14/2011 04:36 AM
Subject:SMSVSAM Sharing control data set - delete and activate
Sent by:IBM Mainframe Discussion List 



Please advise:

We need to activate new sharing control data sets for SMSVSAM. Our plan
is:
- terminate the SMSVSAM address space
- delete the active and space shcds (v sms,smsvsam(shscds),delete
- IPL the machine (reason: new lpar is added to the sysplex)
-activate the new shcds on current and new lpar.
- display the SMSVSAM address space.

 Please confirm if these steps are correct and in the correct sequence.

Regards
Theo



--
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


Nedbank Limited Reg No 1951/09/06. The following link displays
the names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ]
This email is confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]


--
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