This topic contains solutions to common problems that you might experience when configuring BARR/RJE.
Cause: The BARR RJE service is currently started. The BARR RJE service must be stopped before you can select an adapter from the 802.2 Link tab or the SDLC Link tab.
Solution: Stop the BARR RJE service, and then try again.
Cause: The logon data in the RJE Configuration Utility is set incorrectly.
Solution: On the RJE Configuration Utility's RJE Description tab, from the Logon type drop-down list, select your appropriate logon type. Type the correct information in the Logon data box. Make sure that your new logon data matches what your host is expecting you to send. The host's rejection will usually occur for every LU that attempts to log on to JES.
Cause: The VTAM PU definition specifies more LUs than the NCP MAXLU parameter.
Solution: Ask the host programmer to configure the MAXLU parameter in the NCP definition to match the number of LUs defined in the VTAM PU definition. For more information, see the Communication link parameters topic.
Cause: A possible hardware conflict exists, involving DMA.
Solution: Change the IRQ setting and/or DMA level setting until you find a successful combination. If no combination of settings will pass the loopback test, you may either have bad hardware or a computer that does not support DMA.
Cause: The Hayes Optima 33.6 modem does not work well with the AT Modem type selection.
Solution: On the RJE Configuration Utility's SDLC Connection Configuration dialog box, set the modem type to Not autodial and then store the phone number internally in the modem. This will set the modem to automatically dial the number when it senses the DTR signal from the software. Your modem manual describes how to enable this feature. This problem does not occur with the Hayes Optima 56K or 28.8K modem.
Cause: The data rate might be set incorrectly.
Solution: On the RJE Configuration Utility's Link tab, verify the data rate setting.
RS232: Less than or equal to 64000.
V.35: Less than or equal to 384000.
In addition, you must check the SME cable length. Depending on the cable length and quality, you may be experiencing signal degradation. Try a shorter cable if possible, or purchase V.35 line drivers from a third party vendor, such as Black Box Corporation.
See also: Configuring the communication link
Cause: RJE is not enabled in the VPS definition.
Solution: Ask the host programmer to set the RJE=YES parameter on the VPS definition.
Cause: The BARR/RJE LUs are not defined as the correct type or there are not enough LUs defined for what RJE is requesting.
Solution: Make sure enough LUs are defined and that they are the correct type. BARR/RJE LUs are defined on the host as RJE type, not 3270. LUs in VTAM should start at LOCADDR=2. A 10082007 Sense Code message indicates data truncation. For more information, see the Configuring VTAM and Communication link parameters topics.
LUs defined in VTAM should look similar to the definitions below.
|
luname02 LU |
LOCADDR=2,BATCH=YES |
|
luname03 LU |
LOCADDR=3,BATCH=YES |
Use
the LU
macro formula to calculate the number of LUs you need.
Check the communication settings, especially MAXOUT and MAXDATA, to make sure they match the settings at the host.