> On Aug 11, 2016, at 2:31 PM, Jerry Whitteridge > <[email protected]> wrote: > > 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) > ——————————SNIP————————————————— We just put in the NJE definitions into the same member and shared it across two systems. We had several hundred NJE definitions and we had no issues although the vast majority of the connections were active on one system. We did have active on each system a definition to our “sister” location and two Transmitters and two receivers on a shared spool. We sent thousands of jobs on each shift (its been 30 years so I don’t remember precise #’s). It worked quite well and if my sources are still there I can get better numbers for you.
Ed ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
