On Tue, 28 Apr 2015 12:49:44 +0800, Timothy Sipples wrote:
>>>I thought JES3 can still spread workload over multiple LPARs?
>>That has nothing to do with PolyASP, which was the ability to run a
>>secondary ASP on the same CPU.
>
>I disagree with the word "nothing." Multiple LPARs often exist on "the same
>CPU," of course.
>
>It is possible to have even a single LPAR with multiple JES3 globals.
No, it's not possible to start multiple JES3 subsystems (global or local) in
the same LPAR (at the same time).
You can start one (and only one) JES3 subsystem per MVS image/LPAR/system and
JES3 must be the primary subsystem.
See SYS1.SIATSRC(IATINTK) (JES3 initialization task):
*-------------------------------------------------------------
* VERIFY WE ARE THE PRIMARY SUBSYSTEM
*-------------------------------------------------------------
SPACE 1
TM SSIBFLG1,SSIBPJES ARE WE THE PRIMARY SUBSYS?
BC ALLOFF,NOTPRIME NO, GO ISSUE MSG AND ABEND
The message is "IAT3010 JES3 IS NOT THE PRIMARY SUBSYSTEM", ABEND S2FB
There's only one primary subsystem per MVS image:
IEF735I IEFSSNyy: PRIMARY IGNORED. PREVIOUSLY SPECIFIED IN IEFSSNzz
Explanation: Two IEFSSNxx parmlib members specified a primary subsystem.
The system accepts the first specified primary subsystem name and ignores
any subsequent primary subsystem names.
... and there's an ENQ in the JES3 initialization task (SYS1.SIATSRC(IATINTK):
* ENQUEUE-RESOURCES = ENQUEUES ON FOLLOWING TO PREVENT
* TWO JES3 PRIMARY SUBSYSTEMS FROM
* BEING STARTED AT THE SAME TIME:
*
* QNAME - SYSZIAT
* RNAME - SUBSYSTEM NAME
* CONCATINATED WITH
* THE CHARACTER STRING
* 'ACTIVE'
You can have multiple JES3 globals in a multi-system sysplex (more than 1
LPAR/MVS image), but not in a single-system sysplex.
Norbert Friemel
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
