Setting up NJE really isn't that difficult. I can send you a short set of
directions for how to set it up if you want. If your systems are both on
the same physical processor (2 LPARs), and if it's a z-series box with an
OSA/e or similar, it's even easier.
I would bet that your systems people
Gilbert Cardenas wrote:
On Sat, 8 Mar 2008 12:45:28 EST, Ed Finnell <[EMAIL PROTECTED]> wrote:
Guess if all you got is PFCSKs DEST='IP:ipaddr' might suffice w/o NJE
<<>>
DEST=destination
The destination subparameter for JES2 is one of the following:
LOCAL|ANYLOCAL
'IP:ipaddr'
name
|
On Sat, 8 Mar 2008 12:45:28 EST, Ed Finnell <[EMAIL PROTECTED]> wrote:
>Guess if all you got is PFCSKs DEST='IP:ipaddr' might suffice w/o NJE
>
><<>>
> DEST=destination
>The destination subparameter for JES2 is one of the following:
>LOCAL|ANYLOCAL
>'IP:ipaddr'
>name
>| Nn
>|
On Sat, 8 Mar 2008 09:21:53 -0800, Edward Jaffe
>The OP indicates that he already has TCP/IP connectivity between all
>LPARs and FTP servers running on each. Therefore, the JES FTP interface
>should be available without any additional configuration. (Though I
>would highly recommend specifying "JE
In a message dated 3/8/2008 11:03:41 A.M. Central Standard Time, r
[EMAIL PROTECTED] writes:
vote for a NJE connection, with routing JECL where appropriate. It's a
LOT less prone to error than trying to do spool OFFLOAD and LOAD.
Shared spool may be out for valid reasons.
>>
Guess if all
Rick Fochtman wrote:
That will make a very reasonable physical connection; the next step is
to configure software to actually use it. :-)
I vote for a NJE connection, with routing JECL where appropriate. It's
a LOT less prone to error than trying to do spool OFFLOAD and LOAD.
The OP indicate
-
I haven't been following this but has anyone suggested setting up a CTC
between the LPAR's. The connection is setup over Escon channels.
---
That will make a very reasonable physical connection; the next step is
to config
7 matches
Mail list logo
