Initialization problems

Initialization problems can occur when IBM Workload Scheduler is started for a new production period. This can be caused by having IBM Workload Scheduler processes running on an agent or domain manager from the previous production period or a previous IBM Workload Scheduler run. To initialize the agent or domain manager in this situation, perform the following steps:
  1. For a domain manager, log into the parent domain manager or the master domain manager. For an agent, log into the agent domain manager, the parent domain manager, or the master domain manager.
  2. Run the Console Manager and issue a stop command for the affected agent.
  3. Run a link command for the affected agent. This initializes and starts the agent.

If these actions fail to work, check to see if netman is running on the affected agent. If not, issue the StartUp command locally and then issue a link command from its domain manager.

If there are severe network problems preventing the normal distribution of the new Symphony file, a fault-tolerant agent or subordinate domain manager can be run as a standalone system, provided the following conditions are met:
  • The Sinfonia file was generated on the master domain manager after the network problem occurred, and so has never been transferred to the agent or domain manager
  • You have some other method, such as a physical file transfer or FTP to transfer the new Sinfonia file from the master domain manager to the agent or subordinate domain manager.
  • The master domain manager and the agent or subordinate domain manager have the same processor architecture.
If these conditions are met, perform the following steps:
  1. Stop the agent or domain manager.
  2. Delete the <TWA_home>/TWS/Symphony file on the agent or domain manager.
  3. Copy the file <TWA_home>/TWS/Sinfonia from the master domain manager to the <TWA_home>/TWS directory on the agent or domain manager.
  4. Rename the copied file <TWA_home>/TWS/Symphony
  5. Run StartUp to start the agent or domain manager.

    Any inter-workstation dependencies must be resolved locally using appropriate console manager commands, such as Delete Dependency and Release.