We are defining a NEW LPAR to a Sysplex I have two questions :
Let me ask my Sysplex later, I have a clarification on JES2 MAS.
When we need to add a NEW LPAR JES2 to a JES2 MAS, I understand I need to add a statement in JES2PARM - MEMBER(nn) Name=xxxx.
For eg, In this case, MEMBER(6) NAME=S33. I am trying to understand, When IPLed how system understands the new LPAR and shares the same spool, Ckpt, nodes etc ?
Please help with the steps or documentation if any. I am referring to Jes2 Initialization Reference Guide, but I could not get all about MASDEF.
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
This quote from the JES2 Initialization and Tuning Guide manual might help:
Quote:
Initially, one member of the MAS must do a cold start, other members are added, deleted, or changed on a warm start. As each new member is warm started and initialized, all other members of the MAS are made aware of its existence because each member shares the same spool volumes and checkpoint data sets and communicates through the JES common coupling services (JES XCF).
along with
Quote:
A Defining multi-access spool configuration members:
MEMBER(1) NAME=SY01 /* Define member SY01 */
MEMBER(2) NAME=SY02 /* Define member SY02 */
MEMBER(3) NAME=SY03 /* Define member SY03 */
MEMBER(4) NAME=SY04 /* Define member SY04 */
MEMBER(5) NAME=SY05 /* Define member SY05 */
MEMBER(6) NAME=SY06 /* Define member SY06 */
MEMBER(7) NAME=SY07 /* Define member SY07 */
MEMBER(8) NAME=SY08 /* Define member SY08 */
.
.
.
MEMBER(32) NAME=SY32 /* Define member SY32 */
MASDEF OWNMEMB=SY01 /* Define own member */
In example A , member MEMBER(1) NAME=SY01, defines the first member of a multi-access spool configuration. Each member has been assigned a member name (SY01 through SY32, respectively). If you have defined all 32 possible members to your multi-access spool configuration with MEMBER statements, all available slots in the member ID table will be allotted. You must activate each member by adding that member's name on the OWNMEMB= parameter of its MASDEF statement or the member will not be able to perform any work. When an OWNMEMB= parameter was added to example A , only MEMBER(1) was assigned at that time. Therefore, as you start each new member in your MAS, you will need to provide an OWNMEMB= parameter for that member within its initialization stream.
