Concept

Before the implementation and modeling can be started, you must design a concept for how a PDS Explorer should be connected to Eclipse using the AWM. Consider the following questions:

1. What structure should the Tree view have (container element types)?
   • How deep should the container hierarchy go?
   • What properties are relevant for the application per container element type?
2. What other element types are there?
   • How fine should the difference between the element types be?
   • What properties are relevant for the application per element type?
   • What properties make an element unique (ID definition)?
3. How does a user want to search for elements (filter type)?
4. How should elements be shown in the Element Table view (element list structure)?
   • Which properties are to be defined as columns? The performance of the available tools for the determination of the table contents must be considered here. 
5. What actions will be needed (action, tool descriptor)?

These questions have been answered and implemented as follows for the example AWM model:

1. The first level of the Container Tree view should show a “Project” that will be interpreted as the first qualifier for PDS files. The Userid of the logged-in user will be used for this as standard.

   The second and last level contains all the PDS files for this project (1st qualifier).

   Only the container element types “Project” and “Data Set” need therefore be modeled.

   The following properties are supported per dataset: volume, organization, record format, record length, block size, creation date, last used date, is migrated. 

2. A rough categorization with the types “EDITABLE”, “NON-EDITABLE” and “UNKNOWN” has been selected for the definition of the element types.

   A PDS member is uniquely identified through the dataset name and its member names on the assigned system. “Data Set Name” and “Member name” are the only two key properties. The following additional properties are assigned: creation date, change date and time, change user, file suffix.

3. The user should be able to use generic symbols (* %) in the search for files. The only Search criteria are “Data Set Name” and “Member name”.
4. The setup of the element list structure should correspond to the table structure of the ISPF dataset list utilities (Data Set name, Member name, date created, date and time modified, change user).
5. Remote Edit and Browse are the only element actions supported.