We are trying to implementent nje over tcp/ip on z/os1.7 (with ptfs applied)
and getting the following:
IAZ0511I NETSRV1 Server Port number could not be resolved, DEFAULT
assumed: 175
IAZ0545I NETSRV1 Error encountered
the bind failure.
Larry Gray
Large Systems Engineering
Lowe's Companies
336-658-7944
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of L Kaspin
Sent: Tuesday, March 18, 2008 1:52 PM
To: IBM-MAIN@bama.ua.edu
Subject: nje over tcp/ip
We are trying
My nje def's for tcpip followssee if this makes any sensethis
works between the lpar's and as400's I have setup...
/**
/* NJE/IP NETSRV Defs--LIK
/**
NETSRV(01) SOCKET=XXXEI01,
START=YES,
TRACE=NO
Shouldn't 175 be assigned to JES2? I believe that is supposed to be the
PROC name that is going to connect on on that port. I have NJE over IP
working and I do not have port 175 specified at all in my TCP profile.
--
Mark Pace
Mainline Information Systems
I specify it in the jesparm'sit is the default port used...
--
Email Disclaimer
This E-mail contains confidential information belonging to the sender,
which may be legally privileged information. This information is
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of L Kaspin
Sent: Tuesday, March 18, 2008 12:52 PM
To: IBM-MAIN@bama.ua.edu
Subject: nje over tcp/ip
We are trying to implementent nje over tcp/ip on z/os1.7
(with ptfs applied
Thanks to all for your replies
I've got the address space up and listening.
after white boarding the 'execellent' examples in JES2 init and tuning.
In TCP parms for port 175 we put JES2S001 as the job name. which is kicked
off by IEASYSAS and the name is derived from the NETSRV1 definition.
.
It would be in /etc/services ... unless you keep that in an MVS data set.
vmnet 175/tcp # JES NJE over TCP/IP
njenet-ssl 2252/tcp# JES NJE over TCP/IP with SSL
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
The NJE-over-TCP/IP code is now available for z/OS 1.8 JES3.
[
If you're a z/OS veteran, skip this information between brackets:
NJE (Network Job Entry) allows JES-to-JES communication between z/OS
systems, either running on the same machine or across machines. JES (Job
Entry Subsystem
Thought IP (NJE) was brought out in z/OS1.7??
--
Email Disclaimer
This E-mail contains confidential information belonging to the sender,
which may be legally privileged information. This information is intended
only for
Thought IP (NJE) was brought out in z/OS1.7??
1.7 for JES2. 1.8 for JES3.
Bob Shannon
Rocket Software
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET
[EMAIL PROTECTED] wrote:
Thought IP (NJE) was brought out in z/OS1.7??
snip
For JES2, it was. This is for JES3.
--
John Eells
z/OS Technical Marketing
IBM Poughkeepsie
[EMAIL PROTECTED]
--
For IBM-MAIN subscribe / signoff
nay good ref on nje-ip for jes2...like to shake that down.
--
Email Disclaimer
This E-mail contains confidential information belonging to the sender,
which may be legally privileged information. This information is
published in the meantime: SC23-0070-03.
- Original Message -
From: Bob Shannon [EMAIL PROTECTED]
Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@BAMA.UA.EDU
Sent: Tuesday, March 20, 2007 2:41 PM
Subject: Re: JES3 NJE Over TCP/IP Now Available (OA16527)
Thought IP (NJE) was brought out in z
On 20 Mar 2007 02:04:14 -0700, in bit.listserv.ibm-main you wrote:
The NJE-over-TCP/IP code is now available for z/OS 1.8 JES3.
[
If you're a z/OS veteran, skip this information between brackets:
NJE (Network Job Entry) allows JES-to-JES communication between z/OS
systems, either running
In a sense, Ron is correct. It was z/OS V1R7 in which the revered Washington
Systems Center yellow (if my colour memory is correct) NJE protocol manual
appeared in the JES2 bookshelf updated with the TCP/IP support[1]. If you
take a look in Appendix A, System-Dependent Considerations you will
Clark Morris wrote:
snip
I hope it isn't via an extra cost add-on like SNA NJE was. The extra
cost to go NJE may have been the straw that broke the camel's back in
pushing the conversion from JES3 to JES2 by Philips Lighting in the
1980's. I couldn't justify the additional dollars out the
- Original Message -
From: Bob Shannon [EMAIL PROTECTED]
Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@BAMA.UA.EDU
Sent: Tuesday, March 20, 2007 4:23 PM
Subject: Re: JES3 NJE Over TCP/IP Now Available (OA16527)
In a sense, Ron is correct. It was z/OS V1R7 in which the revered
Washington
: Tuesday, March 20, 2007 4:14 PM
Subject: Re: JES3 NJE Over TCP/IP Now Available (OA16527)
nay good ref on nje-ip for jes2...like to shake that down.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email
to pre-announce was a capital offence.
I was at an IBM RoadShow in the mid-1980's, when the manager of VM develop
accidentally pre-announced PR/SM.
The only ones that caught it were the ones using MDF, at the time.
He said that VM was going to run 'closer' to the metal.
Toronto had a lot of
PE train, ALL ABOARD!
- Original Message -
From: Knutson, Sam [EMAIL PROTECTED]
Newsgroups: bit.listserv.ibm-main
Sent: Friday, June 30, 2006 4:13 PM
Subject: UA90255 now available to ENABLE NJE OVER TCP/IP IN JES2 Z/OS 1.7
APAR Identifier .. OA12364 Last Changed
21 matches
Mail list logo
