Job Management Partner 1/Automatic Job Management System 3 Troubleshooting

2.3 Troubleshooting problems related to login to JP1/AJS3 - View

This section describes how to troubleshoot problems that might occur when you attempt to log in to JP1/AJS3 - View.

Organization of this section

(1) Login to JP1/AJS3 is not possible

(2) The connection is lost immediately after login to JP1/AJS3

(1) Login to JP1/AJS3 is not possible

Possible causes are as follows:

If the KAVV400-E message (Cannot connect to the host (host-name). Detailed information: port-number, IP-address) is output:
Check the following and take appropriate actions.

Use the ping utility to ping the destination host. If pinging fails, the destination either host is not running or is unable to connect to the network.

Check whether the JP1/AJS3 service is running on the destination host.
To check the service status:
In Windows:
In the Services dialog box or the Services window, check whether the status of the JP1/AJS3 service is Start. Alternatively, open the Task Manager window, and on the Processes page, check whether the ajsinetd process is running.
In UNIX:
Execute the ps command to check whether the ajsinetd process is running.

Check whether there is a firewall between the source and destination hosts. If there is, check whether packet filtering is configured correctly. To do so, read the explanation in A. List of Port Numbers in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

Check whether the port number in the message matches the port number defined in the services file of the destination host.

If the KAVV412-E message (The host name is specified incorrectly.) is output:
Specify settings so that the host name can be resolved.

If the KAVV458-E message (User mapping failed. The user was not associated with an OS user at the connection destination.) is output:
Execute the jbsgetumap command on the destination host, check the standard output data, and check the points discussed below. For details about the jbsgetumap command, see the Job Management Partner 1/Base User's Guide.

If the JP1 user name that you entered when you logged in to JP1/AJS3 - Manager from JP1/AJS3 - View is not directed to the standard output, the user mapping settings on the destination host are invalid (no mapping is completed between JP1 users and OS users).

If anything other than * is output as the server host name for the JP1 user name, check whether the server host name matches the name of the local host.
Also see the explanation of user mapping in the Job Management Partner 1/Base User's Guide, and make sure that the name of the local host is specified correctly.

Make sure that the OS user name output to the standard output is the name of an existing OS user.
Also check the following if the destination host runs on Windows:
- Make sure that the OS user name to be mapped to the JP1 user name has not been changed in the JP1/Base password management settings.
- Make sure that the password of any mapped OS user has not been changed in the OS.
- Make sure that the accounts of mapped OS users have not been locked out.

If the KAVV459-E message (An error occurred in JP1/Base at the connection destination.) is output:
Check the following:

Make sure that the authentication server host name specified on the destination host is correct.

If the authentication server host name is correct, make sure that an authentication server is running on that host.
Note that if the local host is specified as the authentication server in a UNIX environment, you must set up JP1/Base so that JP1/Base starts as the authentication server. For details, see the explanation of the authentication server settings in the Job Management Partner 1/Base User's Guide.

(2) The connection is lost immediately after login to JP1/AJS3

Possible causes are as follows:

If the KAVV401-E message (The data to the connection destination could not be sent or received.) is output:
If the destination host is a Windows host, its desktop heap area might be insufficient.
To reduce consumption of the desktop heap area on the destination host, specify the following environment setting parameters:

REUSELOGON environment setting parameter (method for starting the logon session process)

LOGONSHMAX environment setting parameter (number of sessions sharing the logon)

For details, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

[Contents][Back][Next]

[Trademarks]