Import PDS Members - Documentation for BMC AMI DevX Workbench for Eclipse 20.14
Matthew Perez Code Pipeline allows users to import external PDS files (datasets and members) into Code Pipeline and create new tasks from them. This makes it easy to define applications to Code Pipeline or bring in a new release of vendor software. See the field definitions for additional definitions. Import of PDS members can be done for any application levels that have been configured to reside in Code Pipeline PDS datasets.
Do one of the following:
From the Repository Explorer view, right-click the Application node and select Import>PDS Member.
From the Containers view, right-click an assignment and select Import PDS Member.
From the View menu in a view that supports tasks (with the exception of the Set view), select Import PDS Member.
The Import PDS Members dialog box appears.
From the Host list, select the host that contains the files to be imported, or click Configure to configure a new host connection. See to the Host Explorer User Guide for instructions on configuring a new host connection. The PDS datasets/members box populates with the files from the selected host.
Important
The host must reside on the same LPAR as the Code Pipeline server.
Use the Add, Edit, Remove, and Remove All buttons to select the files to be imported.
Click Add to open the Add Datasets dialog box and type or browse to datasets/members to be added to the Import PDS Members dialog box.
Select a file and click Edit to edit the name of the file.
Select a file and click Remove to remove the files from the search.
Click Remove All to remove all files from the search.
Important
Selecting a dataset imports the entire dataset while selecting a member imports only that member. Multiple datasets/members can be imported from various locations in one import action, however all must be of the same type.
From the Assignment list, select the name of the assignment that contains or will contain this task. If Code Pipeline can determine the assignment based on the context, this field will be prepopulated; even so, the assignment can be changed, if desired. Optionally, do any of the following to select the assignment:
From the Type list, select the type of component. All listed PDS files will be imported to the specified type.
Optionally, change the application by selecting from the Application list of the applications in the stream. You can also change the subapplication by selecting from the SubAppl list. The Stream, Application, and SubAppl fields are initially prepopulated based on the context of the Code Pipeline view the action was invoked from. The stream cannot be changed.
From the Path list, select the path. The path is enabled after the type is specified.
If the task should be associated with a release, from the Release list, select from the list the release with which the task should be associated. If Code Pipeline can determine the release based on the context, this field will be prepopulated; even so, the release can be changed, if desired.
Select None to not relate assignments to a release.
Select Default to associate the task with the default release for the currently selected assignment. If the assignment has a default release, this is the default selection.
Optionally, to filter the list of releases, click Filter to open the Releases Filter dialog box and enter criteria to filter the Release list.
Optionally, to add a new release, click New.
Important
An assignment can have tasks in different releases.
Click OK. A task is created at the specified path for each file and the tasks are added to the assignment, and are checked out. If, however, an error occurs during the import process, the Import PDS Members Results dialog box appears showing the results of the import and the reasons for any failures.
