Specifications

KAVC4512-E
The Access Control Server at the connection destination could not be connected.
User authentication is impossible because the Access Control server cannot be connected at the connection destination.
The user can neither log in nor connect. The possible causes are as follows:
An incorrect host name of the Access Control server is specified in the JP1/Base settings at the connection
destination.
The Access Control server specified at the connection destination is inactive.
(S)
Cancels processing.
(O)
Correct the cause of the error. Then log on and choose File and then Reconnect.
If an authentication server is specified as the local host in UNIX, you must set up JP1/Base to be started as an
authentication server. For details about how to set up this option, see the explanation of the authentication server in
the Job Management Partner 1/Base User's Guide.
KAVC4513-E
The user could not be authenticated at the connection destination.
Detailed information [(maintenance-information)]
The user could not be authenticated at the connection destination.
(S)
Cancels processing.
(O)
Collect the following data, and then contact the system administrator:
A hardcopy of the window
JP1/AJS3 Console View log information
JP1/AJS3 Console Manager log information
Log information about JP1/Base at the connection destination (If the Access Control server is on another host,
also collect log information about JP1/Base on that Access Control server.)
For details on how to collect the logs, see 1.3 Data to be collected when a problem occurs in the manual Job
Management Partner 1/Automatic Job Management System 3 Troubleshooting and 1.4 Collecting data for
troubleshooting in the manual Job Management Partner 1/Automatic Job Management System 3
Troubleshooting.
For details on how to collect the log of JP1/Base, see the Job Management Partner 1/Base User's Guide.
KAVC4514-E
You cannot use the current login information to log in.
2. Messages
Job Management Partner 1/Automatic Job Management System 3 Messages 1
142