Problem:
In Data View Explorer, when loading 2 SQL DDL Sources, only the last "Load" is visible in the SQL tree structure.
Even if an already created Data View is edited to add a second SQL Source, the result is that the content of the existing Data View is replaced with the new source loaded.
Solution:
The behavior in AMB in ED is not changed compared to AMB in MFE.
In AMB for MFE, when you create a new Data View, and you load multiple SQLDDL members, only the last one loaded is used when you press "BUILD". This is by design. The AMB plugin for Enterprise Developer 2.2.2 behaves in the same way.
A single Data View can contain multiple database targets (e.g. SQL and/or IMS and/or VSAM). When you load IMS and VSAM sources, their definitions can exist in multiple source files. For IMS and VSAM, the load process adds these into the intermediate DDIFILE which it then uses at "BUILD" time to include the information from all of these sources into a single Data View.
However, for SQLDDL, there are two options for loading SQL into a Data View - from either a SQLDDL member or from a SQL Schema member.
If the user wants to load directly from SQLDDL, then only the last SQLDDL member will be included in the Data View when it is built. However, the user also has the option of creating a SQL Schema member which can contain tables from multiple SQLDDL files. Once the SQL Schema member has been created, it can be
loaded into the Data View. When "BUILD" is pressed, all the tables in the SQL Schema file will be included in the Data View.
Maybe you are confused by the term “load multiple sources”, but actually this means that SQL, and VSAM and IMS sources can all be loaded into a SINGLE Database View.
#EnterpriseDeveloper
#MFDS
#AMBDataViewSQLsource
