We do something a little similar using:

//JES2    PROC MEMBER=JES2&SYSNAME,NJEMBR=JES2NJE,ALTMEM=JES2EXPR,


and


//HASPPARM DD DSN=SYS1.PARMLIB(&MEMBER),DISP=SHR
//         DD DSN=SYS1.PARMLIB(&NJEMBR),DISP=SHR

It's not exactly what you're are looking for - but allows a common JES2 deck, 
and then were needed we have the system specific members (everything that is 
"Common" is in the NJEMBR and only where things differ per system is in the 
JES2&SYSNAME member)

Jerry Whitteridge
Manager Mainframe Systems & Storage
Albertsons - Safeway Inc.
925 738 9443
Corporate Tieline - 89443

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 Jesse 1 Robinson
Sent: Thursday, August 11, 2016 12:07 PM
To: [email protected]
Subject: EXTERNAL: Re: Specifying JES2 initialization parameters

My question is whether a parameter like NJEDEF can be specified more than once 
with different keywords such that JES2 honors the 'sum' of the keywords 
encountered.

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-302-7535 Office
[email protected]


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of John McKown
Sent: Thursday, August 11, 2016 11:22 AM
To: [email protected]
Subject: (External):Re: Specifying JES2 initialization parameters

On Thu, Aug 11, 2016 at 1:03 PM, Jesse 1 Robinson <[email protected]>
wrote:

> I need to specify some JES2 NJE-related parameters differently for
> each member. JES2 PARMLIB is shared. Parameters that I need for one
> member do not work for others. I would like to use one common set of
> parms plus a set of parms for the one member that actually engages in
> NJE. I find this in Init and Tuning Guide:
>
> "Initialization statements can be specified by the input source in any
> order. Parameters can also be specified in any order. When a statement
> or parameter is specified, that value is used until that statement or
> parameter is specified again. That is, if the same parameter occurs
> more than once or if the same parameter occurs more than once for a
> statement,
> JES2 will use the value of the last one it reads."
>
> What I want to do is define for example NJEDEF for all members with
> common parameters, then add CONNECT=YES just for one member. Will this
> work in concatenation?
>
> For all members:
>
> NJEDEF   JRNUM=2,JTNUM=2,SRNUM=5,STNUM=5,PATH=8,LINENUM=15,NODENUM=
> 311,OWNNODE=27,MAILMSG=YES
>
> For NJE member only:
>
> NJEDEF   CONNECT=YES
>
> P.S. I know this should go to JES2-L, but I can't get subscribed there.
>
> .
> .
> .
> J.O.Skip Robinson
>

​I use the JES2 INCLUDE directive.
ref:
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.hasa400/include.htm

Example, in SYS1.PARMLIB(JES2PARM)

* COMMON JES2 PARAMETERS
INCLUDE​

​MEMBER=JES2&SYSNAME​ * INCLUDE SYSTEM SPECIFIC PARMS

Example in book:
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.hasa400/has2u60025.htm



--
Klein bottle for rent -- inquire within.

Maranatha! <><
John McKown

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
________________________________
 Warning: All e-mail sent to this address will be received by the corporate 
e-mail system, and is subject to archival and review by someone other than the 
recipient. This e-mail may contain proprietary information and is intended only 
for the use of the intended recipient(s). If the reader of this message is not 
the intended recipient(s), you are notified that you have received this message 
in error and that any review, dissemination, distribution or copying of this 
message is strictly prohibited. If you have received this message in error, 
please notify the sender immediately.
________________________________

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to