Thank you to all who have made suggestions to Mark. I have shared a lot of
additional researhc with him.
I have discussed this on a couple of different occassions with RSCS
development teams. The only RSCS link that meets the current requirements
is the MRJE link. An SNARJE link will not work
On Friday, 09/26/2008 at 10:02 EDT, Mark T. Regan, K8MTR
[EMAIL PROTECTED] wrote:
Since we have VM/RSCS appearing as a RJP workstation to JES3 using EP
and a
3745, can it do the same using the SNA protocol to look like a 3770
device, but
minus the 3745?
Your best bet is to try it. Create
Doesn't JES3 speak TCP/IP these days? If so, use the TCP/IP NJE driver to
connect RSCS to
JES3.
I think it does (or it's trivial to use our NJE Bridge to provide an impedance
matcher), but it sounds like the original setup has some kind of modified RJE
exit on the JES3 side that sets
On Fri, Sep 26, 2008 at 12:27 AM, Mark T. Regan, K8MTR
[EMAIL PROTECTED] wrote:
Our VM systems are already connected to JES3 using NJE via SNA. The problem
is that when the jobs are submitted via NJE they are considered remote jobs.
When they are submitted via the Bisync RJP connection, they
Since we have VM/RSCS appearing as a RJP workstation to JES3 using EP and a
3745, can it do the same using the SNA protocol to look like a 3770 device, but
minus the 3745?
Thanks.
Mark T. Regan, K8MTR
CTO1 USNR-Retired (1969-1991)
From:The IBM z/VM
I'm not sure what the 'JL' command is but it sounds like you want your
job sysout, jesmsg, etc. to stay over on the JES3 side. You might try
editing the jcl on the VM side to include a //*MAIN ORG statement to
override the origin similar to //*MAIN ORG=jes3node.LOCAL where jes3node
is your zOS BDT
That would probably work for output, but if they're used to job progress
messages on VM from JES via NJE msgs, that would break message routing,
I think. Worth a try, though.
Rob's idea is intriguing; the approach of letting a service machine mung
the JCL into IEBGENR and submitting it via
Since we have VM/RSCS appearing as a RJP workstation to JES3 using EP
and a 3745, can it do the same using the SNA protocol to look like a
3770 device, but minus the 3745?
If I'm reading the RSCS docs correctly, no. The RJE drivers really do
expect a physical line, as far as I can tell. The
We have an old process that is used to support submitting jobs from VM to JES3.
The current process uses a 3745 running EP on it. Here's the EP configuration
for them:
The RSCS Side:
*##
EPNCPAB GROUP DIAL=NO, X
LNCTL=BSC, X
We have NJE connections between our VSE guests and RSCS connected via Virtual
CTCA as VSE runs as a guest under VM.
Does you JES system run under VM? If so a virtual CTCA will work or if not, an
emulated CTCA connection.
Ray Waters
From: The IBM z/VM
Doesn't JES3 speak TCP/IP these days? If so, use the TCP/IP NJE driver to
connect RSCS to JES3.
2008/9/25 Ray Waters [EMAIL PROTECTED]
We have NJE connections between our VSE guests and RSCS connected via
Virtual CTCA as VSE runs as a guest under VM.
Does you JES system run under VM? If
Our VM systems are already connected to JES3 using NJE via SNA. The problem is
that when the jobs are submitted via NJE they are considered remote jobs. When
they are submitted via the Bisync RJP connection, they are considered a locally
submitted job. We want the JES3 system to keep thinking
12 matches
Mail list logo
