This topic contains solutions to common problems that you might experience when configuring RJE.
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: 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 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. 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.