activity

activity kill [-s signal] -t activity_ID | -a alloc_ID | -p consumer_name | -c client_name | all

Terminates all activities for the specified allocation, consumer or client.

-s signal

Sends a specific signal.

Signals are operating-system dependent. Refer to the list of signals available for your operating system.

-t activity_ID

Specifies the activity to terminate.

-a alloc_ID

Specifies the allocation to which this action applies.

-p consumer_name

Terminates all activities for the specified consumer.

Specify the unique consumer name, or the full path to the consumer name. Specify as many levels within the consumer tree as required to uniquely identify the consumer, using this format:

/first-level_consumer_name/. . . /leaf_consumer_name

-c client_name

Specifies the name of the client to which this action applies.

all

Terminates all activities.

activity list [-l] [-ll] [-f] [ -t activity_ID | -a alloc_ID | -p consumer_name | -c client_name |-r resource_name]

Lists all activities in the cluster. An activity is in RUN state as long at least one process in the activity's progress group is alive.

-l

Provides the same information with a longer name field, if some are truncated when -l is not specified.

-ll

Provides the same information as the -l option, and in comma-separated values (CSV) format.

-f

Lists the failed activities. These activities are in finish state and the exit reason is not any of these reasons:

• None
• Terminated by SIGKILL
• Terminated by job controller
• Terminated by SIGKILL, job controller does not exist or failed

.

-t activity_ID

Specifies the activity to list.

-a alloc_ID

Lists all activities that belong to the specified allocation.

-p consumer_name

Lists all activities for the specified consumer.

Specify the unique consumer name, or the full path to the consumer name. Specify as many levels within the consumer tree as required to uniquely identify the consumer, in this format:

/first-level_consumer_name/. . . /leaf_consumer_name

-c client_name

Specifies the name of the client to which this action applies.

-r resource_name

Lists all the activities that are using the specified resource.

activity start -a alloc_ID -r resource_name [-t activity_name] [-d CWD] [-C CPU_limit] [-F file_limit] [-D data_limit] [-S stack_limit] [-O core_limit] [-R rss_limit] [-N nofile_limit] [-A as_limit] [-e env_name=value[;env_name=value] …] [-f OUT=file;ERR=file | -f ERR=file;OUT=file] [-decision decision_ID] command

Starts an activity on the specified host.

-a alloc_ID

Specifies the allocation this activity belongs to.

-r resource_name

Specifies the host on which to start the activity.

-t activity_name

Specifies to start the activity using the name specified.

-d CWD

Specifies the current working directory from which the activity is started.

If you do not specify a directory, /tmp is used on Linux® systems, and %TEMP% is used on Windows systems.

-C CPU_limit

Specifies the maximum amount of CPU time this activity may use before being terminated by the system.

After specifying a value, specify the units for measuring CPU time:

• s: seconds. For example, 20s specifies a CPU limit of 20 seconds.
• m: minutes. For example, 40m specifies a CPU limit of 40 minutes.
• h: hours. For example, 2h specifies a CPU limit of two hours.

-F file_limit

Specifies the maximum file size this activity may use before being terminated by the system.

After specifying a maximum file size, specify one of the following values:

• b: bytes. For example, 400b specifies a limit of 400 bytes.
• k: kilobytes. For example, 40k specifies a limit of 40 kilobytes.
• m: megabytes. For example, 4m specifies a limit of 4 megabytes.
• g: gigabytes. For example, 4g specifies a limit of 4 gigabytes.

-D data_limit

Specifies the maximum data segment size limit for each of the processes belonging to the activity. If this limit is exceeded, the activity is terminated by the system.

After specifying a value, specify the units for measuring the data limit:

• b: bytes. For example, 400b specifies a limit of 400 bytes.
• k: kilobytes. For example, 40k specifies a limit of 40 kilobytes.
• m: megabytes. For example, 4m specifies a limit of 4 megabytes.
• g: gigabytes. For example, 4g specifies a limit of 4 gigabytes.

-S stack_limit

Specifies the maximum stack segment size for each of the processes belonging to the activity. If this limit is exceeded, the activity is terminated by the system.

After specifying a value, specify the units for measuring the stack limit:

• b: bytes. For example, 400b specifies a limit of 400 bytes.
• k: kilobytes. For example, 40k specifies a limit of 40 kilobytes.
• m: megabytes. For example, 4m specifies a limit of 4 megabytes.
• g: gigabytes. For example, 4g specifies a limit of 4 gigabytes.

-O core_limit

Specifies the maximum core file size for all the processes belonging to the activity. If this limit is exceeded, the activity is terminated by the system.

After specifying a value, specify the units for measuring the core size limit:

• b: bytes. For example, 400b specifies a limit of 400 bytes.
• k: kilobytes. For example, 40k specifies a limit of 40 kilobytes.
• m: megabytes. For example, 4m specifies a limit of 4 megabytes.
• g: gigabytes. For example, 4g specifies a limit of 4 gigabytes.

-R rss_limit

Specifies the maximum resident set size, limiting physical memory usage for each process belonging to the activity. If this limit is exceeded, the activity is terminated by the system.

After specifying a value, specify the units for measuring the physical memory limit:

• b: bytes. For example, 400b specifies a limit of 400 bytes.
• k: kilobytes. For example, 40k specifies a limit of 40 kilobytes.
• m: megabytes. For example, 4m specifies a limit of 4 megabytes.
• g: gigabytes. For example, 4g specifies a limit of 4 gigabytes.

-N nofile_limit

Specifies the maximum number of open file descriptors this activity may use.

-A as_limit

Specifies the maximum process size (address space) for each process belonging to the activity.

After specifying a value, specify the units for measuring the address space limit:

• b: bytes. For example, 400b specifies a limit of 400 bytes.
• k: kilobytes. For example, 40k specifies a limit of 40 kilobytes.
• m: megabytes. For example, 4m specifies a limit of 4 megabytes.
• g: gigabytes. For example, 4g specifies a limit of 4 gigabytes.

-e env_name=value …

Sets the environment variables for this activity. Specify as many environment variable and value pairs as required to define the environment.

To specify multiple environment variable/value pairs, separate the pairs with a space.

-f OUT=file;ERR=file | -f ERR=file[;OUT=file

Redirects standard output and standard error of the activity to the specified files.

Specify an absolute or relative path. If you specify a relative path, the path will be relative to the execution working directory of the activity process creating or opening the file.

If you use relative paths on Windows, the path will be relative to the execution working directory of the parent PEM.

If the files do not exist, they are created. If the files exist, information is appended to the files.

For file naming limitations and conventions, refer to the specific operating-system documentation. In addition, take into account the following when naming files:

• Do not use semicolon (;) or quotation marks (") in the file name.
• Do not use UNC paths. For example, //hostA/mountpoing/myfile. You will need to mount the network accessible mount point as a local drive instead of using an UNC path.
• Spaces in file names are allowed as long as the whole argument is enclosed in quotes.

-decision decision_ID

Specifies the decision ID.

command

Specifies the command to run.

The command to run must always be specified last.

activity transfer [-c activity_ID] -d decision_ID

Transfers an activity between decisions.

activity view [activity_ID …]

Displays detailed information about the activities in the cluster, including its resources, allocations, current status, start time, and so on.

activity_ID …

Specifies the ID for the activity for which you want detailed information.