NJE - Common questions

These common questions are typically associated with NJE. If you can't find the answer to your question here, click the Index or Search tab of the Help to search for a specific word or phrase.

• Why am I receiving a missing Barr node message?

• How do I send ASCII files to the mainframe as SYSIN data with carriage control?

• How do I obtain valid data set names in NJE?

• How do I resolve differences between transmitter and receiver values?

• How should the Accounting section of the JCL be written?

• How do I create an NJE host printer for Barr-to-host job submission?

• How do I use an override table to auto-assign header fields?

• How do I download host resources?

See also:

• NJE overview

• Getting started

• Troubleshooting

Missing Barr node message

If you delete a connection from the Communications Profile tab, the next time you select the Routing tab the NJE Routing Table -Missing Barr Node dialog box displays. Perform one of the following actions.

• To ignore the warning, select Ignore. The next time you display the Routing tab, the message box will display again.

• To substitute a different Barr node, select Assign a Different Barr Node and select a defined node from the list. The new Barr node will be mapped to the host NJE nodes that were previously assigned to the deleted node.

• To remove the host nodes associated with the deleted Barr node, select Remove Host Nodes.

• To unmap the host nodes from the deleted Barr node, without deleting the host nodes, select Clear Host Nodes. You can then reassign the host nodes to another Barr node.

Sending ASCII files to the mainframe as SYSIN data with carriage control

You must perform the following steps to send ASCII files to the mainframe as SYSIN data with carriage control. This procedure assumes the data is a text file (ASCII characters) with lines delimited by a carriage return and line feed (CRLF). You will convert the data to ASCII with ASA carriage control.

1. Use Print Utility to add the file to the spool. Print Utility imports the ASCII file with CRLFs. Use the following settings:

• File type – Standard ASCII

• Code page (Incoming data format) – 437 (MS-DOS United States)

• Code page (Outgoing data format) – 3037 (Barr Custom)

When SYSIN jobs are added to the Spool Window, they appear shaded in a light blue background.

2. Write the file to disk. The Barr File port writes the file to a folder with CRLFs and ASA carriage control. Use the following settings:

• On the File Format tab, from the drop-down list, select the ASCII format and the ASCII with ASA carriage control check box.

• Make sure the file name you choose is constant. Do this by selecting a header field that will always have the same value.

The file now has ASCII characters (as before), but it also has added ASA carriage control.

3. Use Print Utility to send a JCL file with an embedded ## statement to the host in ASCII send mode. The embedded ## statement includes the file generated by the Barr File port. When Print Utility imports the JCL and reaches the ##D:\<file> statement, it will read the file and convert it to EBCDIC (leaving the ASA carriage control intact, but removing the CRLFs). Use the following Print Utility settings:

• File type – SYSIN data (JCL)

• Code page (Incoming data format) – 437 (MS-DOS United States)

• Code page (Outgoing data format) – 3037 (Barr Custom)

Sample JCL file:

Make sure you add the /A133 to the ##<file> statement or it will truncate to 80 bytes. Also, note the DCB parameter on the sysut2 line, RECFM=FBA tells it to process the file as ASA carriage control.

4. Route the file to your host/mainframe printer, by changing the state of the file and printer to Ready.

Obtaining valid data set names in NJE

The host does not populate the NJE header field with the data set name unless it is explicitly coded on the SYS statement in the JCL that generates the output. To obtain a valid data set name from the host, the DSN parameter must be coded on the SYSOUT line that generates the output in the JCL.

The following job example will generate two separate data sets, one from each JCL step, S1 and S2. Since the SYSOUT statement in each step does not specify a data set name, the host does not populate the NJE header field for data set name. Thus, NDHGNAME for each data set will be "?" or unknown. Because the Barr software uses the job name and data set name for the document name, the data sets will appear in the Spool Window with document names of "P390A?" and "P390A?" (JobnameDatasetname).

In order to obtain valid data set names, the data set name must be specified in the JCL by coding DSN= on the SYSOUT statement of each step. The following job will generate the same two data sets, except now the data set names will be "FIRST" for step S1, and "SECOND" for step S2. Thus, the NDHGNAME header field will be filled in properly by the host, and the data sets will appear in the Spool Window with document names of "P390AFIRST" and "P390ASECOND". When coding the DSN parameter, preface the data set name with "&&" to tell the host that the name is simply a label, rather than referencing a true data set file on the host.

See also: Learning about JCL (SYSIN) jobs

Resolving differences between transmitter and receiver values

Complete the following steps to resolve differences between transmitter and receiver values in NJE.

1. Enter $DNJEDEF on the host operator console to obtain the default settings for the host node.

2. Note the values for the following parameters JTNUM, JRNUM, STNUM, SRNUM. The following graphic shows an example, with the parameters highlighted in yellow.

3. In the NJE Configuration Utility's Advanced Node Settings dialog box, enter the number of transmitters and receivers based on the values obtained from the host console.

Writing the Accounting section of the JCL

The Barr software conforms to IBM standards for handling job accounting information. Although a user can create custom accounting fields which deviate from IBM standards, the host will not be able to fill these fields in correctly if they do not follow the IBM standards. The job line format should follow IBM's JCL accounting standards as shown in the following example.

All letters in JCL statements must be uppercase.

See also: Learning about JCL (SYSIN) jobs