ERROR: No data destination exists for System: sysname and ERROR: No FTP location exists for System: sysname

book

Article ID: 103980

calendar_today

Updated On:

Products

CA Mainframe Software Manager (Chorus Software Manager)

Issue/Introduction

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.

Environment

Release:
Component: MSM

Resolution

Under the system registry tab, click the maintain data destination link on the left under actions.

<Please see attached file for image>

User-added image
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.

<Please see attached file for image>

User-added image
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

<Please see attached file for image>

User-added image
If FTP is available check off FTP and you will see the following changes to the fields. 

<Please see attached file for image>

User-added image
Click save to complete the data destination creation.

<Please see attached file for image>

User-added image
Now two data destinations are shown.

<Please see attached file for image>

User-added image
Click the system/LPAR name to which the data destination should be assigned.

<Please see attached file for image>

User-added image
Click add as shown above and the panel below will be displayed.

<Please see attached file for image>

User-added image
Select a data destination, data destination 1 as in this example and click select resolve the ERROR: No data destination exists for System: sysname.

<Please see attached file for image>

User-added image
Now a data destination is assigned. Click Network Locations.

<Please see attached file for image>

User-added image
Click add.

<Please see attached file for image>

User-added image
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.

Attachments

1558700281805000103980_sktwi1f5rjvs16k2h.png get_app
1558700280025000103980_sktwi1f5rjvs16k2g.png get_app
1558700277991000103980_sktwi1f5rjvs16k2f.png get_app
1558700276104000103980_sktwi1f5rjvs16k2e.png get_app
1558700274270000103980_sktwi1f5rjvs16k2d.png get_app
1558700272612000103980_sktwi1f5rjvs16k2c.png get_app
1558700270828000103980_sktwi1f5rjvs16k2b.png get_app
1558700268872000103980_sktwi1f5rjvs16k2a.png get_app
1558700267104000103980_sktwi1f5rjvs16k29.png get_app
1558700265014000103980_sktwi1f5rjvs16k28.png get_app
1558700263064000103980_sktwi1f5rjvs16k27.png get_app