standby

The egosh standby sub-command manages standby instances for slot-based scheduling and multidimensional resource scheduling.

standby kill -GLOBAL -t tag | ID ... | all

Terminates instances that have been placed in slot-based scheduling standby mode in the cluster. In slots-based scheduling standby mode, service instances of a IBM® Spectrum Symphony application are kept running on a slot after the slot has been released, enabling reuse by other applications.

You require EGO_STANDBY_CONTROL permission to run this command
-t tag ...
Specifies one or more tags identifying the slot-based scheduling standby instances to terminate. Each tag is configured as the standbyServiceTag in the Service section of the application profile. Use the egosh standby list and egosh standby view commands to view the standby service tag.
ID ...
Specifies one or more IDs for the slot-based scheduling standby instances that you want to terminate.
all
Terminates all slot-based scheduling standby instances running in the cluster.

standby kill -MDS id ... | -P resouce_plan {-T tag | -c conusmer_name | all}

Terminates instances that have been placed in multidimensional scheduling standby mode in the cluster. In multidimensional scheduling standby mode, service instances of an IBM Spectrum Symphony application run on new resources allocated after its previous allocated resources is released.

To run this command, you require EGO_STANDBY_CONTROL permission for standby instances with cluster scope, and EGO_STANDBY_CONTROL permission on the consumer for standby instances with consumer scope.
id ...
Specifies one or more IDs for the multidimensional scheduling standby instances that you want to terminate.
-P resource_plan
Specifies the multidimensional scheduling resource plan name for the multidimensional scheduling standby instance you want to terminate. The -P resource_plan is only required if you also specify any of the -T tag, -c consumer_name, or all options:
-T tag
Specifies the tag identifying the multidimensional scheduling standby instance to terminate. The tag is configured as the standbyServiceTag in the Service section of the application profile. Use the egosh standby list and egosh standby view commands to view the standby service tag.
-c consumer_name
Specifies multidimensional scheduling standby instances that contain the specified consumer name. The command terminates standby services released by the specified consumer with a scope of CONSUMER.
all
Terminates all multidimensional scheduling standby instances for the specified resource plan.

standby list -GLOBAL [-m host_name] [-g group_name] [-t tag] [-l]

Lists slot-based scheduling standby instances in the cluster, displaying their IDs, states, host names, resource groups, tags, and so on. In slots-based scheduling, standby instances are service instances of an IBM Spectrum Symphony application that are kept running on a slot after the slot has been released.

You require EGO_STANDBY_VIEW permission to run this command.
-m host_name
Specifies slot-based scheduling standby instances running on the specified host.
-g group_name
Specifies slot-based scheduling standby instances on the specified resource group (for example, ComputeHosts).
-t tag
Specifies slot-based scheduling standby instances that contain the specified tag. The standby service tag is configured as the standbyServiceTag in the Service section of the application profile; for example, MySI.
-l
Provides the same information with a longer name field to avoid truncated information.

standby list -MDS -P resource_plan [-p consumer_name] [-T tag] [-m "host_name, ..."] [-l]

Lists multidimensional scheduling standby instances in the cluster, displaying their IDs, states, host names, resource groups, tags, and so on. In multidimensional scheduling standby mode, service instances of an IBM Spectrum Symphony application run on new resources allocated after its previous allocated resources is released.

To run this command, you require EGO_STANDBY_VIEW permission for standby instances with cluster scope, and EGO_STANDBY_VIEW permission on the consumer for standby instances with consumer scope.
-P resource_plan
Specifies the multidimensional scheduling resource plan name.
-p consumer_name
Specifies multidimensional scheduling standby instances that contain the specified consumer name. The command displays standby services released by the specified consumer with a scope of CONSUMER.
-T tag
Specifies multidimensional scheduling standby instances that contain the specified tag. The standby service tag is configured as the standbyServiceTag in the Service section of the application profile; for example, MySI.
-m "host_name, ..."
Specifies multidimensional scheduling standby instances running on the specified host or hosts. Use quotation marks (") around each a list of host names, and separate each host name with a comma. For example:
-m "host1, host2, host3"
-l
Provides the same information with a longer name field to avoid truncated information.

standby view -GLOBAL [ID ...]

Displays detailed information about the slot-based scheduling standby instance, including the service ID, state, tag (both short and long), cleanup activity ID and command, host name, resource group, and associated metadata. In slots-based scheduling standby, standby instances are service instances of an IBM Spectrum Symphony application that are kept running on a slot after the slot has been released.

You require EGO_STANDBY_VIEW permission to run this command.
ID ...
Specifies one or more IDs for the slot-based scheduling standby instances for which you want detailed information.

standby view -MDS id ...

Displays detailed information about the multidimensional scheduling standby instance, including the service ID, state, tag (both short and long), cleanup activity ID and command, host name, resource group, and associated metadata. In multidimensional scheduling standby mode, service instances of an IBM Spectrum Symphony application run on new resources allocated after its previous allocated resources is released.

To run this command, you require EGO_STANDBY_VIEW permission for standby instances with cluster scope, and EGO_STANDBY_VIEW permission on the consumer for standby instances with consumer scope.
id ...
Specifies one or more IDs for the multidimensional scheduling standby instances for which you want detailed information.