Shell Commands › Application Control › restart (Application Control and Management)--Restart Application

restart (Application Control and Management)--Restart Application

Restart application

Syntax

application restart name (prop=val )* [ --debug ] [ --clean ] [ --norestart ] [ --skipbuild ] [ --force ] [ --cap_cpu ] 

Parameters

name

Name of application.

prop=val

Parameters for scheduling. The following parameters may be specified:

cpu - (optional) CPU allocation (val[%])

mem - (optional) Memory allocation (val[M[B]|G[B]]). If units are not specified, memory is in MB.

bw - (optional) Bandwidth allocation (val[M[b]|G[b]]). If units are not specified, bandwidth is in Mbps.

sched - String specifying scheduling target (see below)

servers - Number of servers on which application is to be started;

--debug

Restart application in debug mode. SCR 779

--clean

Clean application prior to restart.

--norestart

Do not restart application upon grid failure.

--skipbuild

Do not build application prior to restart.

--force

Force releasing any volumes that are currently in use without asking for verification. This is useful when restart is executed over an application that is not currently running. Supported in CA AppLogic for System z® 2.8.8+.

--cap_cpu

Enable the capping of CPU for all components of the application.

Examples

application restart sugarcrm

Restart application 'sugarcrm'

Notes:

• This command combines application stop and start commands.

  The --clean and --skipbuild options may not be specified at the same time.

  The following scheduling targets are supported:

  sched="percentile=(resource percentile)"

  sched=crunch - assign the minimum resources to all components, same as "percentile=0"

  sched=expand - assign the maximum resources to all components, same as "percentile=100"

  sched="mode=(scheduling mode)". While the scheduling target “mode=” property has not been disabled, CA AppLogic for System z® currently supports only one copy of z/VM. Providing “mode=” will have no effect on application scheduling. Valid values are one of the following:

  • 1 - pack servers
  • 2 - round robin with random start
  • 3 - round robin scheduled

  When using the pack server scheduling mode, the servers are chosen in priority order based on their assigned role and the least amount of available resources. CA AppLogic for System z® will always use servers with a role of none first, secondary second and primary last; without regards to the available resources on those servers (that is, the secondary servers won't be used until all of the none servers are used, the primary server won't be used until all secondary and none servers are used).

  The application restart will fail if --debug is specified and the application has field engineering code 16 set.

  Restarting an application resets the component flapping counters that are maintained by CA AppLogic for System z®. A component's flapping counter is the number of times that component has failed within the last 24 hours (each component has its own flapping counter). Once a component fails 3 times in 24 hours, the component is not restarted by CA AppLogic for System z®. comp start/restart or app start may also be used to reset a component's flapping counter.