Bulk Data Movement Guide

10.5.2
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Bulk Data Movement Security

A PowerExchange user must have the proper level of authority to connect to the PowerExchange Listener and to access the PowerExchange resources and the data sources and targets.

On z/OS and i5/OS systems, you can include the SECURITY statement in the DBMOVER configuration member to require a user ID and password from an attached client for access to PowerExchange resources and data sources and targets.

On supported Linux, UNIX, and Windows systems, you can include the SECURITY statement along with related statements in the DBMOVER configuration member to require LDAP authentication to verify the credentials of a client that is trying to connect to the PowerExchange Listener or PowerExchange Logger.

On z/OS, the following additional levels of security are available, depending the type of data source or target:

For DB2 for z/OS data, you can include the MVSDB2AF statement in the DBMOVER configuration member to control whether PowerExchange uses the call attachment facility (CAF) or Recovery Resource Services attachment facility (RRSAF) to connect to DB2. To use DB2 authentication methods to control user access to DB2 tables, select RRSAF. To use the PowerExchange Listener user ID to verify user access, select CAF.

For Datacom data, you can define RACF resource profiles to prevent unauthorized READ access to Datacom tables.

For Adabas data, you can use any of the following security methods:

Adabas password security at the file level

Adabas Security by Value method

RACF resource profiles to restrict WRITE access to Adabas databases and files

For more information about security, see the PowerExchange Reference Manual
.

Introduction to PowerExchange Bulk Data Movement

Download Guide

Watch

Comments

Communities

Knowledge Base