Colin,
I believe the answer is the collection of the following JES2 parameters:
JRNUM, JTNUM, SRNUM, STNUM
These parameters define, respectively, the number of job receivers, job
transmitters, sysout receivers and sysout transmitters. These parms can be
specified either as part of the LINE(xx) definition or as part of the
NJEDEF definition. NJEDEF provides the installation-wide default which can
be individually overridden on the LINE definition. We use NJEDEF, which is
why it wasn't specified in the LINE definition I sent you.
Let me know if you have further questions.
Dennis
"Colin Allinson"
<[EMAIL PROTECTED]
us.com> To
Sent by: "The IBM [email protected]
z/VM Operating cc
System"
<[EMAIL PROTECTED] Subject
ARK.EDU> Re: RSCS NJE link to MVS over Basic
CTC (Non-SNA)
07/01/2006 03:53
AM
Please respond to
"The IBM z/VM
Operating System"
<[EMAIL PROTECTED]
ARK.EDU>
Dennis,
Thanks for the example. I have forwarded this to our MVS sysprog asking how
it compares to our current JES definition. I will speak to her on Monday
and see what she says.
One question, (because I am an MVS illiterate), where is the number of
streams defined on the JES side? Is there a streams parameter somewhere? or
is it called something else?
Regards
Colin
Dennis Schaffer <[EMAIL PROTECTED]> Wrote:
Colin,
We've been using basic ESCON CTC NJE links between our VM and MVS systems
for at least a decade. We do run two streams but I can't tell you
specifically why. We don't have any of the problems you described.
However, I'm including our RSCS and JES2 definitions in the hope they might
help you. The VM system is V037 and the MVS system is USMUO002.
RSCS
LINK USMUO002 NJE 7040 0 * 16 * * * * NOAST
NORET
PARM USMUO002 STREAMS=2 TA=1
JES2
NODE(7) COMPACT=0,
NAME=V037,
AUTH=(DEVICE=NO,
JOB=NO,
SYSTEM=NO,
NET=NO),
LINE=40,
LOGMODE=,
PATHMGR=NO,
PRIVATE=NO,
REST=300,
TRACE=NO,
TRANSMIT=BOTH,
RECEIVE=BOTH,
HOLD=NONE,
PENCRYPT=NO
LINE(40) UNIT=7000,TRANSPAR=YES
Hope this helps.
Dennis
