Activate CPC
The Activate CPC operation activates the CPC object designated by {cpc-id}. This operation is not permitted when the CPC is enabled for DPM. This operation is supported using the BCPii interface.
HTTP method and URI
POST /api/cpcs/{cpc-id}/operations/activate
In this request, the URI variable {cpc-id} is the object ID of the target CPC object.
Request body contents
The request body is expected to contain a JSON object with the following fields. If none of the optional fields are included, an empty request body must be supplied.
Field name | Type | Rqd/ Opt | Description |
---|---|---|---|
activation-profile-name | String (1-16) | Optional | The name of the activation profile to be used for the request. If not provided, the request uses the profile name specified in the next-activation-profile-name property for the CPC object. |
force | Boolean | Optional | Whether this operation is permitted when the CPC is in "operating" status (true) or not (false). The default is false. |
Response body contents
Once the operation is accepted, the response body contains a JSON object with the following fields:
Field name | Type | Description |
---|---|---|
job-uri | String/ URI | URI that may be queried to retrieve activation status updates. |
Asynchronous result description
Once the operation has completed, a job-completion notification is sent and results are available for the asynchronous portion of this operation. These results are retrieved using the Query Job Status operation directed at the job URI provided in the response body.
Field name | Type | Description |
---|---|---|
message | String | The message text describing the detailed error that occurred when the operation was partially successful or not successful. |
Description
Activation is a process that makes a CPC operational, which means either:
- The CPC is ready to have a control program or operating system loaded, or
- The CPC has loaded and is running a control program or operating system.
Activation makes a CPC operational by:
- Using predefined information, referred to as an activation profile, to set the operational capabilities and characteristics of the CPC
- Checking the current status of the CPC, and then performing only the operations necessary to make it operational as specified in the activation profile.
So, using activation is not limited to starting the system. Using activation is recommended whenever you want to make the CPC or its logical partitions operational.
A complete activation activates the CPC and its logical partitions completely in a single step. The result of a complete activation is an operational CPC with logical partitions loaded and running operating systems. The current status of the CPC and its logical partitions determines which operations are performed during activation to make them operational. Activation may include:
- Turning CPC power on.
- Performing a power-on reset, this includes allocating system resources to the CPC.
- Then activating logical partitions to support multiple images.
Activating each logical partition includes:
- Initializing it.
- Allocating system resources to it.
- Loading it with a control program or operating system.
Because the status of the CPC and its logical partitions determines which operations must be performed during activation to make them operational, one or more operations listed above may not be performed during activation. For example:
- Activating the CPC does not perform a power-on reset if the CPC has already been power-on reset and the applicable settings in its assigned activation profile, such as the operating mode and active input/output configuration data set (IOCDS), are already in effect.
- Activating the CPC does not perform any operations if the CPC is already operational and all settings in its assigned activation profile are already in effect.
When the operation is initiated, a 202 (Accepted) status code is returned. The response body includes a URI that may be queried to retrieve the status of the operation. See Query Job Status for information on how to query job status. When the operation has completed, an asynchronous result message is sent, with Job Status and Reason Codes described in Job status and reason codes.
Authorization requirements
This operation has the following authorization requirements:
- For the web services interface:
- Object-access permission to the CPC object designated by {cpc-id}
- Action/task permission for the Activate task.
- For the BCPii interface the source partition must have receive BCPii security controls permissions for the CPC object.
HTTP status and reason codes
On success, HTTP status code 202 (Accepted) is returned and the response body is provided as described in Response body contents.
The following HTTP status codes are returned for the indicated errors, and the response body is a standard error response body providing the reason code indicated and associated error message.
HTTP error status code | Reason code | Description |
---|---|---|
400 (Bad Request) | Various | Errors were detected during common request validation. See Common request validation reason codes for a list of the possible reason codes. |
403 (Forbidden) | 0 | The request used the BCPii interface and the source partition does not have receive BCPii security controls permission for the CPC object. |
1 | The API user does not have the required permission for this operation. | |
404 (Not Found) | 1 | The object ID in the URI ({cpc-id}) does not designate an existing CPC object, or the API user does not have object-access permission to the object. |
409 (Conflict) | 4 | The operation cannot be performed because the CPC object designated by {cpc-id} is currently enabled for DPM, which is not supported in this operation. |
329 | The operation cannot be performed because the CPC designated by the request URI is an unmanaged CPC, which is not supported by this operation. | |
500 (Server Error) | 280 | An IO exception occurred during the scheduling of the asynchronous request. |
503 (Service Unavailable) | 1 | The request could not be processed because the HMC is not communicating with the SE needed to perform the requested operation. |
Additional standard status and reason codes can be returned, as described in Invoking API operations.
Job status and reason codes
Job status code | Job reason code | Description |
---|---|---|
204 (No Content) | N/A | Operation completed successfully. |
500 (Server Error) | 263 | Operation failed or was rejected due to the current CPC status and use of the force=false parameter. If rejected due to force=false, the CPC status is unchanged. If the operation failed, the CPC status is unknown. Refer to the message parameter in the error response body for details. |
Additional standard status and reason codes can be returned, as described in Invoking API operations.
Usage note
This operation activates a CPC object that is not enabled for DPM. If the targeted CPC object is enabled for DPM, the Start CPC operation may be used instead. Refer to Start CPC for details.