Shell Commands › Application Control › config (Application Control and Management)--Configure Application › application config Command Output Specification

application config Command Output Specification

The output is the following when --batch is not specified:

application : <app>
<name>      : <val>
...

The output is the following when --batch is specified:

appconfig <app>
   {
   <name> = <val>
   ...
   }

can be one of the following:

• .name - attribute
• name - property
• resource.val - resource, resource can be cpu, mem, val can be min, max, dflt
• vol. name - volume
• servers. val - set servers, val can be min, max, set.

start (Application Control and Management)--Start Application

Start application

Syntax

application start name ( prop=val )* [ --debug ] [ --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 in whole CPUs or percent (val[%])

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

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

sched - String specifying scheduling target (see below)

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

--debug

Start application in debug mode.

--norestart

Do not restart application upon grid failure.

--skipbuild

Do not build application prior to start.

--force

Force releasing any volumes that are currently in use without asking for verification.

--cap_cpu

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

Examples

application start sugarcrm

Start application 'sugarcrm'

Notes: 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

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

Starting 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 restart may also be used to reset a component's flapping counter.