Table of Contents


  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging and Reporting
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. DTLDESCRIBE Metadata
  12. PowerExchange Globalization
  13. Using the PowerExchange ODBC Drivers
  14. PowerExchange Datatypes and Conversion Matrix
  15. Appendix A: DTL__CAPXTIMESTAMP Time Stamps
  16. Appendix B: PowerExchange Glossary

Adabas Security

Adabas Security

You can use the following Adabas security options with PowerExchange:
  • Password security
  • SAF security
  • Security by Value
To use Adabas password security, specify file passwords in PowerExchange data maps. To use Adabas SAF security or security by value, no action is required in PowerExchange.
PowerExchange does not support Natural Security, which is a Natural application. PowerExchange supports Adabas data access directly, not through an application layer.
PowerExchange checks PowerExchange-specific resource profiles to determine whether to permit write access to Adabas files. For this security checking to occur, specify 2 in the first parameter of SECURITY statement in the DBMOVER configuration file. PowerExchange then uses the MVS System Authorization Facility (SAF) interface to check access to the resource profiles.
By default, PowerExchange checks resource profiles in the FACILITY class. Use the RACF_CLASS parameter in the DBMOVER configuration file to specify a different class for checking security profiles. If you specify a different class, it must be defined in RACF or the security product you use, with a resource name that has a maximum length of 8 bytes.


We’d like to hear from you!