SNA NRJE Node Managers Guide (30292-90007)

Chapter 5 75

SNA NRJE Troubleshooting

Problem Resolution

• SNA Transport activates, but one or more SNA NRJE LUs do

not (MPE V only).

— Ensure that the transmit buffer size (in the Link Conﬁguration:

SNA/SDLC Link Data screen), the maximum RU size (in the SNA

Conﬁguration: LU Data screen), and the RU size (in the NRJE

Conﬁguration: Reader Data screen) are consistent. If the SNA

maximum RU size for the LU has been conﬁgured less than the

NRJE RU size, that LU will not be able to send an INIT-SELF to

request an LU-LU session with the host.

— Ensure that the host has activated the LU. If it has not, make the

LU active by issuing

V NET,ACTIVE,ID=

LUName

at a host operator’s console. You might have to issue a separate

VARY command for each LU.

• SNA Transport activates (case 1).

Although SNA Transport is active when the NRJE

Wsid

command is

typed, this message is received:

WORKSTATION

Wsid

NOT CONFIGURED (CIERR 4435)

SNA NRJE has not found a ﬁle named NMCONFIG.PUB.SYS to use as

its conﬁguration ﬁle. You must name the SNA NRJE conﬁguration

ﬁle NMCONFIG.PUB.SYS.

• SNA Transport activates (case 2).

Although SNA Transport is active when you try to start an SNA

NRJE workstation with a STARTWS or NRJECONTROL STARTWS

command, you get this message:

UNABLE TO STREAM MONITOR JOB (INT=123)

which can be caused by (1) the MPE streaming facility not being

enabled, or (2) an unfound xxx.NRJE.SYS job stream ﬁle for the SNA

NRJE workstation. (See Chapter 4 , “NA NRJE Workstation Startup

and Shutdown,” of this manual for a description of this job stream

ﬁle.)

• This message is logged for each LU just before it terminates:

FMD CANNOT ACCESS READER AND WRITER CONFIGURATION

DATA (SPOOLER=-7) (MIDAS=0) (FMD=4121)

This indicates a probable problem in NMCONFIG.PUB.SYS: You might

have changed data on a conﬁguration screen but not pressed

[f6]

(Update Data) afterwards. So, the conﬁguration was not updated.