SNA NRJE Node Managers Guide (30292-90007)

82 Chapter5
SNA NRJE Troubleshooting
Troubleshooting Output Routing Problems
• A Formid Lookup Table entry specifying both an
environment file and hard copy form mount does not work.
NRJE opens the output file with the hard copy form mount message
but ignores the environment file.
To select both an environment file and hard copy form, always
specify the environment file first. For example, enter:
:checks;dev=pp
;env=checkenv.hpenv.sys;forms=checks.
Do not enter:
:checks2;dev=pp;forms=checks.
;env=checkenv.hpenv.sys
• A submitted file stays in the reader queue and is not
transmitted to the host, even though the workstation is
“active.”
Use the SHOW command to ensure that the file priority is above the
fence for the reader. The reader fence can be displayed by using the
DISPLAY QUEUE command.
Use the STATUS command to check the status of the LUs. If no LUs
have the FMD state set to “no traffic,” then no LUs are available for
sending the job to the host.
One job might have been sent to the host, but the host sent a “Job
Received” message that was in a non-standard format, and so it was
not recognized by NRJE.
Use NMDUMP to format the log file, and then examine the format of
any JES2 “HASP100” or JES3 “IAT6101” messages. (Note that
logging for SNA NRJE must have been configured; otherwise, no log
file was generated for NRJE.) Using NMDUMP for SNA NRJE is
explained earlier in this chapter. Algorithms used to parse the
messages are described in the SNA NRJE User/Programmer
Reference Manual.
• For JES2, verify that the host is not DRAINED.