49546 MD RSCB1G
p 616.653.8429
f 616.653.8497
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Ravi Kumar
Sent: Tuesday, December 28, 2010 8:11 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: spool to spool output transfer
if you guys have connect
if you guys have connect direct as third party product spool to spool
transfer is pretty easy stuff..
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM
At 11:59 -0600 on 12/01/2010, Dana Mitchell wrote about Re: spool to
spool output transfer:
> would take JES2 -> JESA -> JESB -> JES2
Interesting puzzle. Seems to me that still wouldn't work, since JESA wouldÂ
need to know about JES2 (left) because it's connected t
> would take JES2 -> JESA -> JESB -> JES2
>
Interesting puzzle. Seems to me that still wouldn't work, since JESA would
need to know about JES2 (left) because it's connected to it, and JES2
(right) in order to know it needs to route traffic destined for JES2 (right)
via
JESB.
Dana
-
, David
> Sent: Wednesday, December 01, 2010 9:17 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: spool to spool output transfer
>
> Well, I thought about that, but I don't think that works either. JESA
> would have to know about both JES2's of the same name, and tha
ssion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of McKown, John
Sent: Wednesday, December 01, 2010 9:45 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: spool to spool output transfer
I don't think this is what you will want, but I'll just throw it out
there anyway. Have you considered running two JES
ance Company.SM
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:ibm-m...@bama.ua.edu] On Behalf Of Jousma, David
> Sent: Wednesday, December 01, 2010 8:21 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: spool to spool output transfer
>
> Tha
Subject: Re: spool to spool output transfer
I had a similar requirement a few months back because for some reason,
they
have NJE locked up real tight around here.
I created a rexx routine that basically ftps the spool file to the
intended lpar
by ip address.
I initiate the process by performing an
I had a similar requirement a few months back because for some reason, they
have NJE locked up real tight around here.
I created a rexx routine that basically ftps the spool file to the intended
lpar
by ip address.
I initiate the process by performing an SE on the spool entry and then typing
Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Bob Shannon
Sent: Tuesday, November 30, 2010 1:36 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: spool to spool output transfer
> Doesn't NJE over IP have the same restrictions as standard NJE of
>connecting two nodes of the sa
> Doesn't NJE over IP have the same restrictions as standard NJE of
>connecting two nodes of the same name?
I overlooked that detail. You should be able to use a node number as long as
they are different.
Bob Shannon
Rocket Software
--
46 MD RSCB1G
p 616.653.8429
f 616.653.8497
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Bob Shannon
Sent: Tuesday, November 30, 2010 1:19 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: spool to spool output transfer
1. NJE over TCP would result i
On Tue, 2010-11-30 at 13:09 -0500, Jousma, David wrote:
> Looking for ideas for doing spool to spool transfer of output NOT using
> NJE.
Maybe Sine Nomine's NJE/IP Bridge package would be useful here?
http://www.sinenomine.net/products/vm/njeip
--
David Andrews
A. Duda and Sons, Inc.
dav
1. NJE over TCP would result in one hop (assuming IP connectivity between the
two MASs)
2. If it's a one-time exercise, can you do a spool unload/reload?
Bob Shannon
Rocket Software
--
For IBM-MAIN subscribe / signoff / archive
All,
Looking for ideas for doing spool to spool transfer of output NOT using
NJE.Issue is transferring output between two different MAS-plex of
the same node-name. NJE would work if multi-hopped, NODE-A connected to
NODE-B, NODE-B connected to NODE-C, and finally NODE-C connects to the
other
15 matches
Mail list logo