Deploy Request Main Screen
When option DP is entered on the ISPW Main Menu, the Deploy Request Queue screen is displayed as shown in the following figure.
Deploy Request Queue Screen
Filter Dates Field
The Filter Dates line highlighted in the preceding figure, Deploy Request Queue screen, is used to control the Deploy Request Queue display. The following table describes the field values:
Value | Description |
|---|---|
T (Today) | Requests created today |
D (Day) | Requests created in the last day |
W (Week) | Requests created in the last week |
M (Month) | Requests created in the last month |
R (Range) | Requests created between the range of dates specified on the Filter Line |
N (No Range) | All Requests will be listed |
When entering the Deploy Request Queue for the first time, the date filtering will be set to W. If the User preferences (option U.S) are set to Session Save=Y, whatever value is typed in the Filter Dates line will be saved across sessions.
The following table describes the Deploy Request Queue Column:
Column | Description |
|---|---|
ReqId | Unique ID that identifies a Request |
Set | ISPW Set that the Deploy Request was created for |
DplyEnv | Deploy Environment |
Status | Overall Status of the Request. See the subsequent row for a description of the Status values |
Description | Taken from the Set Description |
Date | Date/Time that the Request was created. |
Deploy Request Status
The following table lists the different Deploy Request statuses.
Deploy Request Statuses
Status | Description |
|---|---|
Planned | After the Set Lock process, the Deploy Request is created with a status of Planned to indicate that this Request contains the intended list of parts for deployment. |
Confirmed | When the Set has executed, the Tasks are checked for completeness and the Request status is updated to Confirmed, meaning the Tasks are ready for the Deployment process. |
Staged | If a staging warehouse is defined, staging will be done. During staging, ISPW Deploy will transfer the component parts to the target platform and store them in a warehouse, ready to be deployed. |
Implemented | For deployments with an Activation process, a status of Implemented indicates that the Implemented Process is complete. |
Completed | Indicates that the whole deployment process for this Request is complete—whether it included Activation or not. |
Failed | A Package (or multiple Packages) has a Failed status. |
Terminated | The Deploy Request has been manually terminated. |
Deploy Request Queue Operations
The following operations are valid on the Deploy Request Queue screen:
- S—Select Request to shown Package detail
- L—List Messages
- M—Modify Request.
Sections later in this chapter describe each of these operations.