Limited Life Cycle Support

After you have loaded information about your data stores in Data Express, your table definitions may have changed. For this possibility, the Distributed Loader provides the following options:

• Skip - if the data store to be loaded already exists in the Knowledge Base, previously loaded tables are ignored.
• Overwrite - if the data store to be loaded already exists in the Knowledge Base, old definitions are removed and the new definitions are inserted. If the data store is new, definitions are added. This option clears all the data element-class assignment in the existing data store.
• Update with the Automatic update option - if the definition for the data store exists in the Knowledge Base, the following occurs:
  • Metadata is added to the Knowledge Base for new data elements in the data store.
  • Metadata for data elements that have different size values (length or precision or scale) is updated in the Knowledge Base but information for assigned classes remains untouched.
  • Metadata for data elements that have different data types is updated in the Knowledge Base and all class assignments are cleared.
• Update with the Confirm first option - The behavior is exactly the same as the Automatic update option, but at any data store a confirmation is requested before applying the changes.
• Update with the Export option - if the definition for the data store exists in the Knowledge Base, the following occurs:
  • You are asked to fill in the name and location of the IMPSRC flat file.
  • Information about data elements that have different size values (length or precision or scale) is written on the specified flat file.
  • The flat file can be moved on z/OS IMPSRC and used as IMPSRC by the z/OS life cycle, as described in the Front End Guide. Using this option, metadata is updated by the z/OS batch life cycle only.