Job Management Partner 1/Automatic Job Management System 3 Troubleshooting
This section describes the action to be taken when the status displayed in monitoring mode is Unknown.
Take action based on the message displayed in Information in the Detail Information - [AJS3 Unit Monitored Objects] dialog box.
- Organization of this section
- (1) KAVC6xxx-E messages
- (2) KAVSxxxx-E messages
(1) KAVC6xxx-E messages
If a message from KAVC6001 to KAVC7000 appears, take the action described for the applicable message in 2.1 Messages beginning with KAVC (Messages about JP1/AJS3 Console) in the manual Job Management Partner 1/Automatic Job Management System 3 Messages 1.
(2) KAVSxxxx-E messages
Take the action described in the applicable message in 2.2 Messages beginning with KAVS (Messages about the scheduler) in the manual Job Management Partner 1/Automatic Job Management System 3 Messages 1.
For the following messages, take the action described.
(a) If the KAVS1600-E message (The specified unit name is invalid.) is displayed
Possible causes are as follows:
- The specified unit does not exist.
- The user does not have the required permission for the specified unit.
- The unit type of the specified unit is one of the following:
- Manager job group or manager jobnet
- Nested jobnet or job (the unit must belong to a level lower than the root jobnet)
- In the user mapping settings specified on the JP1/AJS3 Console Agent host, the OS user is mapped to a JP1 user able to access from the JP1/AJS3 Console Manager host, but the OS user is not mapped to a JP1 user on the JP1/AJS3 Console Agent host.
For the AJS3 unit to be monitored, specify a unit whose status you are able to obtain.
(b) If the KAVS1601-E message (Requests to the specified unit could not be processed.) is displayed
The status cannot be obtained because requests to the specified unit are not supported.
For the AJS3 unit to be monitored, specify a unit whose status you are able to obtain.
(c) If the KAVS1005-E message (Cannot connect to Access Control Server.) is displayed
Possible causes are as follows:
- An incorrect authentication server was specified during setup of JP1/Base on the monitored host after monitoring started.
- The authentication server specified on the monitored host stopped after monitoring had started.
- After monitoring started, the monitored host and the authentication server host could not connect over the network.
Eliminate the cause of the error. When this has been done, the correct status will be displayed on the monitored host the next time that the status is acquired.
Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.