Hello All, Thanks for responding.
Here my statement looks little confusing. >From the LPAR99, The SOCKET statement has NETSRV(0) for LPAR77 with its IP address. Also, LPAR99 has NETSRV(0) with its LOCAL >From the LPAR77, The SOCKET statment has NETSRV(1) for LPAR77 with its IP ADDRESS as LOCAL. The LPAR99 has again NETSRV(0) with its IP address. Here I would like to understand if NETSRV(Suffix values like 0 or 1) makes any differences ?? On Thu, Sep 26, 2013 at 1:03 AM, Lizette Koehler <[email protected]>wrote: > Correct, I was only asking if the OP was using one or the other. I can see > how it is confusing with my last statement. > > However, if the OP cannot PING the TCPIP connection, then it is not > established. > > Validation of the connection in TCPIP and the JES2 definitions needs to be > done to determine if the connection is good. > > Lizette > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Wissink, Brad [ITSYS] > Sent: Wednesday, September 25, 2013 11:47 AM > To: [email protected] > Subject: Re: Setting up NJE > > I have NJE setup between two Lars using TCP/IP. And I have no VTAM > definitions. > > Brad Wissink > Sent from my Verizon Wireless 4G LTE DROID > > > mf db <[email protected]> wrote: > > Lizette, > > I am using TCPIP, VTAM definitions are not done, but I have made those NJE > definition on JES2PARMS and related NETSRV1 address spaces have been > defined. > > Could you please point me the VTAM definition if it is required for NJE > over > TCPIP ? > > > On Wed, Sep 25, 2013 at 12:45 PM, Lizette Koehler > <[email protected]>wrote: > > > I forgot - > > > > Are you using SNA, TCPIP, or other for JES2 NJE Connections? > > > > JES2 alone cannot connect without a VTAM (TCPIP or SNA) connection. > > Check that your VTAM definitions are in place and active. > > > > Lizette > > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:[email protected]] > > On Behalf Of Lizette Koehler > > Sent: Wednesday, September 25, 2013 12:12 AM > > To: [email protected] > > Subject: Re: Setting up NJE > > > > Cross Posting to IBM Main and JES2 > > > > First > > > > The JCL card should read /*ROUTE XEQ nodename > > > > And I am not sure what your VTAM, JES2 deck, and other parts might be. > > > > If you are running use SDSF or MVS Console to do > > > > D NET,ID=vtamapplid,E > > > > $DNODEnodename > > > > > > Please look up the commands as you will need to know how to do this. > > > > This is a good overview of SDSF (If you use that) > > http://www.mabu.org/sdsf_overview.pdf > > > > > > XMITTER typically means your nodes are not connected. But that is > > unique to your shop. > > > > Also, you can do internet searches on your issues and see if you can > > work them out. Use phrases like > > > > IBM JES2 NJE > > > > For other documentation. > > > > Lizette > > > > > > -----Original Message----- > > From: JES2 discussion group [mailto:[email protected]] On Behalf > > Of mf db > > Sent: Tuesday, September 24, 2013 9:28 PM > > To: [email protected] > > Subject: Re: Setting up NJE > > > > --001a1133eaca44df1304e72daf24 > > Content-Type: text/plain; charset=ISO-8859-1 > > > > Hello All, > > > > Cross posted to IBM MAIN and JES2 listserves > > > > I submitted a job with a route card /*ROUTE LPAR99 from the > > LPAR77(Both the LPARS are MVA guest running on Z/VM), But the Job > > stays in XMITTER status and the Job is not executing on the target > > LPAR(LPAR99) > > > > NETSRV1 is active on both the LPAR(LPAR99 and LPAR77). > > > > Z/OS : 1.13 > > > > Could someone point me to the right direction. > > > > > > > > > > On Wed, Sep 18, 2013 at 10:45 AM, mf db <[email protected]> wrote: > > > > > Hello, > > > > > > Yes, the two MVS guest are coupled with CTC's > > > > > > > > > > > > > > > On Wed, Sep 18, 2013 at 2:49 AM, Tom Wasik <[email protected]> wrote: > > > > > >> It would seem to me that using TCP/IP would be the easiest way to > > >> make this NJE connection happen (again as long as they are not in > > >> the > > same MAS). > > >> Assuming each MVS image has an IP address that can be accessed > > >> from the other MVS image, then it is just a matter of defining the > > >> needed NJE NETSERVs, SOCKETs, and LINEs in JES2. > > >> If you do not have TCP/IP for some reason, and you are 2 guests on > > >> the same VM image, you can use virtual CTC adapters in VM to set up > > >> a BSC connection between the 2 guest images. This is a bit old > > >> fashion, but it still works and is probably the easiest NJE to set > > >> up (assuming you understand the VM commands to couple the virtual > CTCs). > > >> You can look in the JES2 initialization and tuning guide for more > > >> information or there is a SHARE presentation that could help: > > >> > > >> https://share.confex.com/share/119/webprogram/Handout/Session11757/ > > >> Wh at%20are%20all%20these%20JES2%20NJE%20Options.pdf > > >> > > >> Tom Wasik > > >> JES2 Development > > >> > > > > > > > > > > --001a1133eaca44df1304e72daf24 > > Content-Type: text/html; charset=ISO-8859-1 > > Content-Transfer-Encoding: quoted-printable > > > > <div dir=3D"ltr"><div><div><div><div>Hello > > All,<br><br></div><div>Cross pos= ted to IBM MAIN and JES2 > > listserves<br></div><div><br></div>I submitted a j= ob with a route > > card /*ROUTE LPAR99 from the LPAR77(Both the LPARS are MVA = guest > > running on Z/VM), But the Job stays in XMITTER status and the Job is = > > not executing on the target LPAR(LPAR99)<br> > > <br></div>NETSRV1 is active on both the LPAR(LPAR99 and > > LPAR77).<br><br></d= > > iv>Z/OS : 1.13<br><br></div>Could someone point me to the right > > iv>direction.<= > > br><div><br><br></div></div><div class=3D"gmail_extra"><br><br><div > > br>class= > > =3D"gmail_quote"> > > On Wed, Sep 18, 2013 at 10:45 AM, mf db <span dir=3D"ltr"><<a > > href=3D"ma= ilto:[email protected]" > > target=3D"_blank">[email protected] > > </a>></= > > span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 > > span> 0 .8e= > > x;border-left:1px #ccc solid;padding-left:1ex"> <div > > dir=3D"ltr"><div>Hello,<br><br></div>Yes, the two MVS guest are > > couple= d with CTC's<br><br><br></div><div class=3D"HOEnZb"><div > > class=3D"h5"><= div class=3D"gmail_extra"><br><br><div > > class=3D"gmail_quote">On Wed, Sep 18= , 2013 at 2:49 AM, Tom Wasik > > <span dir=3D"ltr"><<a href=3D"mailto: > > wasik@= > > us.ibm.com" target=3D"_blank">[email protected]</a>></span> > > wrote:<br> > > > > <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 > > .8ex;border-left:1p= x #ccc solid;padding-left:1ex">It would seem to > > me that using TCP/IP would = be the easiest way to make this NJE > > connection happen (again as long as the= y are not in the same MAS). > > =A0Assuming each MVS image has an IP address th= at can be accessed > > from the other MVS image, then it is just a matter of de= fining the > > needed NJE NETSERVs, SOCKETs, and LINEs in JES2.<br> > > > > > > If you do not have TCP/IP for some reason, and you are 2 guests on the > > same= > > VM image, you can use virtual CTC adapters in VM to set up a BSC > connectio= > > n between the 2 guest images. =A0This is a bit old fashion, but it still > > wo= > > rks and is probably the easiest NJE to set up (assuming you understand > the > > = > > VM commands to couple the virtual CTCs).<br> > > > > > > You can look in the JES2 initialization and tuning guide for more > > informati= > > on or there is a SHARE presentation that could help:<br> <a > > href=3D" > https://share.confex.com/share/119/webprogram/Handout/Session117= > > 57/What%20are%20all%20these%20JES2%20NJE%20Options.pdf" > > target=3D"_blank">h= > > ttps:// > > share.confex.com/share/119/webprogram/Handout/Session11757/What%20ar= > > e%20all%20these%20JES2%20NJE%20Options.pdf</a><br> > > > > > > <span><font color=3D"#888888"><br> > > Tom Wasik<br> > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
