Chapter 11. SNA over Ethernet 179
NJEDEF DELAY=120, /*Max.Msg Delay Time ohwnc*/
HDRBUF=(LIMIT=100, /*Number of NJE header +trailer ohwnc*/
/*buffers */
WARN=80), /*Warning Threshold ohwnc*/
JRNUM=2, /*Number of job receivers hwnc*/
JTNUM=2, /*Number of job xmitters hwnc*/
LINENUM=5, /*Number of lines for NJE hwnc*/
MAILMSG=NO, /*Don't automatically issue ohwnc*/
/*notification message */
MAXHOP=0, /*Num.of iterations to limit hwnc*/
/*hoping in network */
/*0 means no hop counting */
NODENUM=50, /*Max.number of NJE nodes nc*/
OWNNODE=3, /*this node's number c*/
PATH=1, /*number of paths hwnc*/
RESTMAX=8000000, /*Max.resistance tolerance ohwnc*/
RESTNODE=150, /*this node's resistance ohwnc*/
RESTTOL=300, /*Alt.resistance tolerance ohwnc*/
SRNUM=2, /*number of sysout receivers hwnc*/
STNUM=2, /*number of sysout xmitters hwnc*/
TIMETOL=30 /*Time variation between clocks ohwnc*/
We changed the OWNNODE= statement on each system to match the node number we had
assigned; we then let the SMF system ID match the node name list in order to select a node
number. We had to cold start the systems in order for the change of OWNNODE to become
effective.
11.15.1 NJE verification
On z370, zsna, and z232 we placed the following commands in the automatic startup script:
$SLOGON1
$SLINE1
We then used the console at zos1 to start the NJE network, producing the following console
activity:
ZOS1 $slogon1
ZOS1 $HASP881 LOGON1 APPLID=ZOS1NJE1,STATUS=INACTIVE
ZOS1 $HASP091 LOGON1 IS ACTIVE
ZOS1 $sline1-3
ZOS1 $HASP880 LINE1 UNIT=SNA,STATUS=INACTIVE
ZOS1 $HASP880 LINE2 UNIT=SNA,STATUS=INACTIVE
ZOS1 $HASP880 LINE3 UNIT=SNA,STATUS=INACTIVE
ZOS1 $sn,a=z370nje1
ZOS1 $HASP000 OK
ZOS1 $HASP200 Z370 STARTED ON LNE3 SESSION Z370NJE1 BFSZ=03840
ZOS1 $HASP524 L3.JT1 INACTIVE
ZOS1 $HASP524 L3.JT2 INACTIVE
ZOS1 $HASP534 L3.ST1 INACTIVE
ZOS1 $HASP534 L3.ST2 INACTIVE
ZOS1 $sn,a=z232nje1
ZOS1 $HASP000 OK
ZOS1 $HASP200 Z232 STARTED ON LNE2 SESSION Z232NJE1 BFSZ=03840
ZOS1 $HASP524 L2.JT1 INACTIVE
ZOS1 $HASP524 L2.JT2 INACTIVE
ZOS1 $HASP534 L2.ST1 INACTIVE
ZOS1 $HASP534 L2.ST2 INACTIVE
ZOS1 $sn,a=zsnanje1
180 EFS Systems on a Linux Base: Additional Topics
ZOS1 $HASP000 OK
ZOS1 $HASP200 ZSNA STARTED ON LNE1 SESSION ZSNANJE1 BFSZ=03840
ZOS1 $HASP524 L1.JT1 INACTIVE
ZOS1 $HASP524 L1.JT2 INACTIVE
ZOS1 $HASP534 L1.ST1 INACTIVE
ZOS1 $HASP534 L1.ST2 INACTIVE
.
To verify that NJE was operating properly we transmitted a message from zos3 to a user on
z370, with the following results at the TSO terminal:
INMX000I 0 message and 1 data records sent as 4 records to Z370.IBMUSER
INMX001I Transmission occurred on 06/28/2003 at 19:54:09.
READY
On zos1, we saw the following message traffic indicating the file had been sent:
ZOS1 $HASP530 FLEX ON L3.ST1 4 RECORDS
ZOS1 $HASP534 L3.ST1 INACTIVE
On z370, we saw the following message indicating the file had been received:
19.54.39 $HASP540 FLEX ON L1.SR1 FROM FLEX AT ZOS1 4 RECORDS
Finally. we logged onto z370 and submitted a job to be run on sysplex member zos3 at node
ZOS1, producing the following output:
SDSF OUTPUT DISPLAY TESTNJE JOB00851 DSID 2 LINE 0 COLUMNS 02-133
COMMAND INPUT ===>SCROLL ===>PAGE
J E S 2 J O B L O G --S Y S T E M Z O S 3 --N O D E Z O S 1
19.59.20 JOB00851 ----SATURDAY,28 JUN 2003 ----
19.59.20 JOB00851 $HASP373 TESTNJE STARTED -INIT SYS -CLASS A -SYS ZOS3
19.59.20 JOB00851 $HASP395 TESTNJE ENDED
- - - - - - JES2 JOB STATISTICS - - - - - -
28 JUN 2003 JOB EXECUTION DATE
4 CARDS READ
21 SYSOUT PRINT RECORDS
0 SYSOUT PUNCH RECORDS
1 SYSOUT SPOOL KBYTES
0.00 MINUTES EXECUTION TIME
1 //TESTNJE JOB 0,FLEX,CLASS=A,NOTIFY=FLEX
JOB00851
/*ROUTE XEQ ZOS1
00011015
/*JOBPARM SYSAFF=ZOS3
00012015
2 //S1 EXEC PGM=IEFBR14
00020009
IEF142I TESTNJE S1 -STEP WAS EXECUTED -COND CODE 0000
IEF373I STEP/S1 /START 2003179.1959
IEF374I STEP/S1 /STOP 2003179.1959 CPU 0MIN 00.02SEC SRB 0MIN 00.00SEC VIRT
4K SYS 232K EXT 4K SYS 10960K
IEF375I JOB/TESTNJE /START 2003179.1959
IEF376I JOB/TESTNJE /STOP 2003179.1959 CPU 0MIN 00.02SEC SRB 0MIN 00.00SEC
As should be expected, the job was routed to the ZOS1 node, where an initiator on system
zos3 picked it up for execution. The job output was then returned to the spool on z370, where
we displayed it with SDSF.

Get S/390 PartnerWorld for Developers, ITSO/EFS Project EFS Systems on a Linux Base: Additional Topics now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.