Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Utilities
  3. createdatamaps - Data Map Creation Utility
  4. DTLCCADW - Adabas PCAT Utility
  5. DTLCUIML - IMS Log Marker Utility
  6. DTLINFO - Release Information Utility
  7. DTLREXE - Remote Execution Utility
  8. DTLUAPPL - Restart Token Utility
  9. DTLUCBRG - Batch Registration Utility
  10. DTLUCDEP - CDEP Maintenance Utility
  11. DTLUCSR2 - IDMS SR2 and SR3 Records Utility
  12. DTLUCUDB - DB2 for Linux, UNIX, and Windows CDC Utility
  13. DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities
  14. DTLURDMO - Data Map Utility
  15. DTLUTSK - Task Control Utility
  16. EDMLUCTR - Log Scan and Print Utility
  17. EDMXLUTL - Event Marker Utility
  18. HOSTENT - TCP/IP Address Reporter Utility
  19. PWXCATMY - MySQL Catalog Utility
  20. PWXUCCLPRT - Print Log Summary Utility
  21. PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
  22. PWXUCREG - Capture Registration Suspend Utility
  23. PWXUCRGP - Capture Registrations Print Utility
  24. PWXUDMX - Data Maps Update Time ECSA Memory Utility
  25. PWXUGSK - SSL Reporting Utility for z/OS
  26. PWXUMAP - Map List Utility
  27. PWXUSSL - PowerExchange SSL Reporting Utility

Schema File for Describing Control Files

Schema File for Describing Control Files

Each control file must conform to the schema that is installed with the Informatica Client and with Informatica services.
The schema file, named DatamapGeneration.xsd, is provided in the following directories on the machines where the Informatica Client and the Informatica services are installed:
  • Informatica_client_installation_directory
    \clients\DeveloperClient\osgi_mf_plugins\jars\resources\
  • Informatica_services_installation_directory
    \pwxmfplugins\resources\
The schema consists of definitions of complex types and elements, where a complex type consists of multiple elements.

Complex Type Definitions in the Schema File

For each complex type, the schema file includes the following information:
  • Name
  • Base type, for complex types that inherit properties from a base type
  • Definitions of each child element

Element Definitions in the Schema File

For each element, the schema file might include the following information, depending on the data type:
  • Name
  • Cardinality, that is, the minimum and maximum number of occurrences
  • Type
  • Documentation
  • Valid values
  • Minimum and maximum length

Using the Schema File to Determine the Control File Hierarchy

You can open the schema file in an XML editor to determine the allowable hierarchy of elements in a control file. You can also derive this information from the schema file.
For example, the root element in the schema is DatamapGeneration. The definition of the DatamapGeneration complex type specifies a choice of one of the following child elements:
  • seqGen, of type SEQGen
  • vsamGen, of type VSAMGen
  • imsGen, of type IMSGen
The definition of the SEQGen type specifies that it is an extension of the GenBase base type, which includes the following elements: globalCopybookParserConfig and cacheConfig. Elements of type SEQGen include the elements defined by the GenBase type in addition to the following elements:
  • globalGenConfig, of type SEQGenConfig
  • globalSeqProperties, of type SEQDatamapProperties
  • datamapInstances, which consists of one element, seqDatamapInstance, that can occur one or more times
The control file for generating SEQ data maps therefore has the following high-level structure:
DatamapGeneration seqGen globalCopybookParserConfig (optional) cacheConfig (optional) globalGenConfig (optional) globalSeqProperties (optional) datamapInstances (required) seqDatamapInstance (at least one required)
You can continue in this manner to determine the complete hiearchy for SEQ control files, as well as for VSAM and IMS control files.

0 COMMENTS

We’d like to hear from you!