Validate remote systems is beginning for deployment: CA product name Validating System: sysname ERROR: No data destination exists for System: sysname ERROR: No FTP location exists for System: sysname.
Under the system registry tab, click the maintain data destination link on the left under actions.
This displays the Data Destination panel. In this example a data destination, dd was previously added. Even though a data destination was added here if it was not assigned to the ( target ) system/LPAR to which the deployment is being done the "No data destination exists for System" failure would still occur. All data destinations must first be added here.
To add a data destination click create. This displays the following panel. It defaults to the Shared DASD transmission method. If FTP;ing between the ( source ) LPAR that CA CSM runs on and the ( target ) LPAR to which the deployment is being done then use Shared DASD. This means that the ( source ) CA CSM LPAR and the ( target ) LPAR to which the deployment is being done must share the same DASD's. Enter the mount point directory path, which is a directory path that must exist on the ( target ) LPAR to which the deployment is being done.The user that is doing the deployment must have write permission to this directory, and mount authorization on the target system
If FTP is available check off FTP and you will see the following changes to the fields.
Click save to complete the data destination creation.
Now two data destinations are shown.
Click the system/LPAR name to which the data destination should be assigned.
Click add as shown above and the panel below will be displayed.
Select a data destination, data destination 1 as in this example and click select resolve the ERROR: No data destination exists for System: sysname.
Now a data destination is assigned. Click Network Locations.
Enter the hostname or IP address for the ( target ) LPAR to which the deployment will be done. The port number which is usually defaults to 21. Enter the FTP path that is on the ( target ) LPAR. This path is created by the install jobs ETN0100 and ETN0200. Click save to resolve the ERROR: No FTP location exists for System: sysname.