Thanks for your help Bruce and Paul. I was able to ask this to the IBM support team and they told me about the "XCFGRPNM" parm on the JES2 MASDEF statement.
I hadn't specified a value for this, so both were using the default of "JES2". This was causing the conflict, even though my intent was that they not be part of the same MAS. Adding “XCFGRPNM=someuniqueval” to the MASDEF statements allowed both systems to come up, apparently independently of each other. (I used JES2Z3 on my S0W3 system and JES2Z4 on my S0W1 system.) I did a cold start on the S0W3 JES, and these Groups/Members were used: GROUP SYSJES MEMBER S0W3 GROUP JES2Z3 MEMBER JES2$S0W3 GROUP SYSJ2$XD MEMBER JES2Z3$S0W3$$$$$ I did not do a cold start on the S0W1 JES, and I believe it used the former/default value: GROUP SYSJES MEMBER S0W1 GROUP JES2 MEMBER JES2$S0W1 GROUP SYSJ2$XD MEMBER JES2$S0W1$$$$$$$ Thanks again, Wendell ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
