Troubleshooting Output Routing Problems

The value specified for Host Standard Print Form Name or Host Standard Punch Form Name in the NRJE Configuration: Workstation Data Page 2 screen must match the eight-byte field Standard form name in the host. Obtain the host Standard form name from the host generation.

For JES2 and JES3, the "Job Received" message must be in a format that can be parsed by NRJE. If the "Job Received" message is non-standard, you must install an exit procedure to parse this message. If you do not want parsing to occur, you must disable the check for "Job Received" messages by specifying N in the Job Management field of the NRJE Configuration: Workstation Data screen. See the SNA NRJE User/Programmer Reference Manual for information on the internal parsing algorithms used by SNA NRJE. Information to develop your own parsing procedures for user exits available with NRJE can also be found in that manual.

The SOLICITED JCW might be set.

The JES2 banner might be turned off.

NRJE rejects job output from the host.

Verify that the host sends a PDIR before the output. NRJE requires that the host send an FMH2 PDIR after the FMH1 BDS (Begin Destination Selection) command before sending job output. Incorrect host configuration or problems in host user exit procedures may cause the PDIR not to be sent.

PRINT= and PUNCH= designations in the SUBMIT command do not work.

Output always goes to the default destination. (This feature applies to JES2 and JES3 only. It is not supported with VSE/POWER.)

Try routing with the FORMS= keyword even though the output is presumably being received on the "standard" form. If output is routed to the desired destination this time, then either the configuration for the Host Standard Print Form Name or Host Standard Punch Form Name in the NRJE Configuration: Workstation Data Page 2 Screen is incorrect, or your job is actually generating "special forms" output.

If output continues to go to the default destination with the FORMS= keyword, then use the SHOW command to display the job status. If no Joblog entry is displayed, then either (1) NRJE failed to parse the "Job Received" message correctly, and you need to install an exit procedure to do the parsing, or (2) no "Job Received" message was sent by the host (in which case you must work with host system programmers to resolve the problem).

If the SHOW command does display the Joblog entry but indicates that the status is either (1) "TRANSMITTED TO HOST" (that is, apparently no data sets have been received), or (2) "n DATA SETS RECEIVED," where n is a number less than expected. In either case, if you know more data sets were received by NRJE but NRJE failed to associate the output with your job, then verify that the host is transmitting banners (separator pages) with the output.

Alternately, NRJE might be unable to correctly parse the host banners and an exit procedure might be needed to do this parsing. See the SNA NRJE User/Programmer Reference Manual.

If the SHOW command indicates that the correct number of data sets have been received but output still goes to the incorrect destination, check any messages which might have been logged by NRJE indicating any failures to route output as requested.

The copies parameter in your JCL is not recognized.

NRJE opens the output spool file with number of copies = 1 regardless of whether you request additional copies in your JCL (such as with the DD card copies parameter).

Verify that the PDIR actually sent by the host with the data set has the "copies" field set to the requested number of additional copies.

A back-referenced file equation does not work.

(This is used with either the SUBMIT command routing options for PRINT, PUNCH, or FORMS, or for a Formid Lookup Table entry.)

Check any messages logged by NRJE upon attempting to execute the file equation. Ensure that MANAGER.SYS has write access to the destination file.

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.