The new “cluster instance name” local option

About this task

One of the steps of the twsClusterAdmin utility is instance name registration of the IBM Workload Scheduler cluster resource within the local option localopts file.

The IBM Workload Scheduler agent uses the value of this new local option to signal to the IBM Workload Scheduler cluster resource that the agent has received a stop command.

It is important to change the value of the cluster instance name local option every time the IBM Workload Scheduler resource instance name is changed. If the clusterinstancename local option does not point to the right name, the IBM Workload Scheduler resource will be set to failure state from the cluster resource monitor. Do not specify this name in double-byte character set (DBCS) characters.

To change the IBM Workload Scheduler resource instance name use the following procedure:
  1. Take the IBM Workload Scheduler resource instance offline using the Cluster Administrator console. To verify if IBM Workload Scheduler stopped correctly you can use the Cluster Administrator console and check the status of the IBM Workload Scheduler resource instance. If the resource has failed to stop you can check in the cluster and IBM Workload Scheduler logs for the reason. See Traces for more details on the log files.
  2. From the Failover Cluster manager console, select the resource and modify the IBM Workload Scheduler cluster resource name from cluster_resource_name to cluster_resource_name_new.
    Note: Do not specify this name in double-byte character set (DBCS) characters.
  3. Open the localopts file using Notepad. Modify the value of the clusterinstancename local option. Check that the name is the same you specified for the IBM Workload Scheduler cluster resource in Step 2.
  4. Modify the cluster instance name in the StartUp_clu.cmd and ShutDown_clu.cmd scripts.
  5. Bring the IBM Workload Scheduler resource instance online in the Failover Cluster manager console.