You can delete deployments. You cannot delete deployments in the following situations:
A deployment deletion must be confirmed before a deletion starts.
Note: If system information was changed, not all files may be deleted. In this case, you many need to delete these files manually. For example, if an FTP transmission was changed to a Shared DASD Cluster or if the remote credentials are incorrect or changed.
The message log explains which containers, folders, and files were deleted during processing and which ones were not deleted. See how to investigate a failed deployment for details on finding the message log.
Note: Target libraries are never deleted.
The following artifacts are deleted by status:
All applicable database records
All applicable database records
Archive located at Application Root/sdsroot/Dnnnn where nnnn = Deployment ID automatic number. Application Root is defined in settings under mount point management.
All applicable database records.
Same as Snapshot Completed, plus attempts to delete any transmitted snapshots on target systems.
Same as Transmit in Error.
Same as Transmitted.
Same as Snapshot Completed.
Same as Snapshot Completed.
Follow these steps:
The Deployment page appears.
The detailed deployment information appears.
The deployment is deleted.
Note: If you do not have remote credentials for the systems in your deployment that you want to delete, or you do not have default remote credentials defined on the User Settings, Remote Credentials page, the Remote Credentials Properties dialog appears. You are prompted to define remote credentials for the systems.
|
Copyright © 2014 CA.
All rights reserved.
|
|