JES3 does not support sending data to the host.Configure MVS/JES3 to add an NJE node for Barr. You must also define lines and streams for the node. Later we will test to make sure the NJE node has been configured correctly.
JES3 does not support sending data to the host.
Define the BARR/NJE node to JES3 by adding another NJERMT in SYS1.PARMLIB(JES3IN00)and a BDT macro An instruction in a source language that points to a sequence of instructions in the same language to replace it. in SYS1.PARMLIB(BDTIN00). The following JES3 NJE definition contains statements your host programmer must enter for each Barr node. More advanced macros and parameters are documented in IBM's OS/390: JES3 Initialization and Tuning Reference.
If this is an initial installation of BDT, you must define your host's NJE node to BDT. This is completed by defining the JES3 host node. See the following example.
|
SYSID,NJENAME=hostnodename,NJEAPPL=hostnodename |
For SNA connectivity, add the following line.
|
NJERMT,NAME=hostnodename,HOME=YES |
|
NJERMT,NAME=nodename,HOME=NO,TYPE=SNA |
|
Parameter |
Description |
|
NAME=nodename |
Replace nodename with the BARR/NJE node name. This is the value the BARR/NJE node will be identified as on your NJE network. It is used for routing, messages, and JCL. This value is also the Barr node name specified when configuring BARR/NJE for Barr SNA or SNA. |
|
APPL=luname |
Replace luname with the NJE LU name specified during VTAM configuration. This must also match the NJE LU name specified when configuring BARR/NJE for Barr SNA or SNA and the SNA gateway. |
|
L=BARRMOD |
Replace BARRMOD with the VTAM logmode table entry specified during VTAM configuration. |
To improve efficiency, you can set other parameters such as
LU,
BUFSIZE,
and BUFNO.
See IBM's OS/390: V2R6.0
BDT Installation manual for more information.
|
DEVICE,DTYPE=NJELINE,JNAME=BARRL1,JUNIT=(XXX,M,TP) |
|
Parameter |
Description |
|
DTYPE=NJELINE |
Replace NJELINE with the line for data transmission. |
|
JNAME=BARRL1 |
Replace BARRL1 with the name of the line. This must match the value assigned to LINE=BARRL1. |
|
JUNIT=(XXX,M,TP) |
Replace XXX with the device number of the CTC device. Replace M with the name of the main that has access to that line. Replace TP with the destination class for receiving messages about the line. |
|
NAME=nodename |
Replace nodename with the BARR/NJE node name. This is the value the BARR/NJE node will be identified as on your NJE network. It is used for routing, messages, and JCL. This value is also the Barr node name specified when configuring BARR/NJE for CTC. |
|
RDLY=nminutes |
When AUTO=YES, RDLY=nminutes sets the number of minutes to wait before restarting a connection. |
For CTC connections, remember to set the JES3 parameter BUFFER,BUFSIZE=nnnn to its
maximum value, 4084. If you do
not have the value set to 4084, then you need to set NJERMT,BFSIZ=mmmm
to BFSIZE=44.
The following is a sample SYS1.PARMLIB(JES3IN00) configuration for a single host node connected to BARR/NJE.
|
NJERMT,NAME=JESA1,HOME=YES |
|
|
NJERMT,NAME=BAR1NJE,HOME=NO,TYPE=SNA,STREAM=2 |
|
|
BDTNODE,N=BAR1NJE,APPL=TB201NO1,A=YES,ASR=50,TYPE=NJE,BFSIZ=4096,BUFNO=8,CS=NJEDUP, |
+ |
|
L=BARRMOD,LU=17 |
|
where:
|
Parameter |
Description |
|
JESA1 |
The host's NJE node. |
|
BAR1NJE |
The NJE node definition for BARR/NJE's node. It has 2 transmitters. It is an SNA connection with 17 virtual LUs and the maximum RU size. |