Top
Systemwalker Operation Manager Troubleshooting Guide
FUJITSU Software

4.16.20 "Connecting with Jobscheduler ..." Remains Displayed

Applicable versions and levels

Action 1

Points to check

Is there a large number of connections to the Systemwalker Operation Manager server (Jobscheduler function) from the Systemwalker Operation Manager clients?

Cause

The connection was attempted from a client after the limit value for the number of connections to Jobscheduler was exceeded, so connections cannot be made to Jobscheduler in this state.

Action method

As a rough guide, do not connect more than eight Systemwalker Operation Manager clients to a particular Systemwalker Operation Manager server at the same time out of consideration for the response from each client.

Remarks

The following are used in the count of the number of connections:

Note that the number of client connections can also be checked using the jobschprint -u command.

Action 2

Points to check

Did the Systemwalker Operation Manager client end using the correct method?

Cause

The Systemwalker Operation Manager client end may not have been recognized because the Systemwalker Operation Manager client was disconnected unexpectedly.

Action method

Possibilities are as follows, so review the operation:

Remarks

The correct method to terminate the client is to click X in the client window. Do not use Task Manager to terminate the client, or shut down the system while the client is running.