Mark,

My answers are just after your questions:

1)   Is this something that was done prior to acquisition and you just need  to 
documented it, or was it never set up to do this before? As far as I know, it 
has not been done before.

2)  Are both LPARs in the same MAS? Yes they are

3) Are there any static NJE  connections defined (CONNECT statements in JES2)? 
Not sure on this. Our JES2 person has been out this week.

4) Is it SNA or  TCP/IP NJE? Primarily SNA/NJE due to them have some NJE with 
external business partners, but we would want to expand this to TCP/NJE once it 
has been set up on the same JES2 MAS.


 Thanks,

Mark Regan




________________________________
From: Mark Zelden <mzel...@flash.net>
To: IBM-MAIN@bama.ua.edu
Sent: Thu, September 9, 2010 2:22:24 PM
Subject: Re: Moving JES2 NJE function from one system to another in a MAS?

On Thu, 9 Sep 2010 10:57:52 -0700, Mark T. Regan, K8MTR
<netsfw-ibmm...@yahoo.com> wrote:

>We've never had to do this before, but since acquiring these two JES2 (we're a
>JES3 shop) systems via an acquisition, we need to set up a process to move NJE
>from one JES2 LPAR to another. Can anyone supply me with the commands to move
>NJE?
>

A lot of assumptions made below so we need more information. 

1)   Is this something that was done prior to acquisition and you just
need to documented it, or was it never set up to do this before?

2) Are both LPARs in the same MAS?

3) Are there any static NJE connections defined (CONNECT statements in JES2)?

4) Is it SNA or TCP/IP NJE? 


Assuming it is SNA and both LPARs are in the same MAS:

1) If both LPARs have their own LOGON (VTAM APPL), all you may need
to do is restart the connections from the other LPAR ($SN,A=applid).  
You need to have the LOGON active and active/idle lines.

2) If they have the same APPL, then you probably have to $PLGN(n) from
one LPAR and start it on the other before you can start nodes. Again, you also
need defined / active and idle lines.  This assumes the other LPARs
VTAM definitions are in place to do so.   If the VTAMLST is shared, you 
probably inact the node on one LPAR and activate it on the other.

3) If static connections are defined, the other end must have the mas
member defined or it won't connect. 

I've seen it done both ways: Same APPLID that gets moved or each LPAR with
its own APPLID.  If you define a new / 2nd appl, then coordination is needed
with your partners, so I think sharing the same APPLID is more common.

I haven't had to do something like this from scratch (I've defined new nodes
and swapped SNA for IP) in more years than I can recall specifically, so I
hope I didn't forget something or give you wrong information.

Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS      
mailto:mzel...@flash.net                                          
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html 
Systems Programming expert at http://expertanswercenter.techtarget.com/

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to