File-AID Data Privacy Environment
The File-AID Data Privacy parameters provide configuration options for the Dynamic Privacy Rules (DPR) created with BMC AMI DevX Data Studio's Data Privacy. These parameters are only needed when the Data Studio’s Data Privacy component of the Data Studio is installed and DPR is to be used.
Also, this task can be skipped during initial configuration of File-AID and returned to later, after the File-AID Data Privacy installation (File-AID Services1, File-AID Rules Engine, etc.) has been completed.
Disguising elements of a data set using DPR can be requested from option D on the File-AID/Data Solutions Main Menu or from File-AID/RDX, File-AID for Db2, or File-AID for IMS if you are also licensed for File-AID/Data Solutions.
The Dynamic Privacy Rules (DPR) rules are stored in a Data Studio’s Data Privacy Repository and are accessed at execution time to disguise data as defined by the data privacy rules.
All repositories which are to be available for DPR from a given install of the File-AID must be configured at the same File-AID Services location as each install of the File-AID Install Image only supports connecting to one File-AID Services location. If multiple File-AID Services locations are required, the File-AID Install Image must be customized multiple times.
File-AID Services
Three parameters are required to specify how to access the File-AID Services location:
- FILEAID_SERVICES_IP_ADDRESS
- FILEAID_SERVICES_USER_INTERFACE_PORT
- FILEAID_SERVICES_EXECUTION_PORT
File-AID Data Privacy environment core parameters (FADP00)
This section describes the data privacy environment core parameters.
FILEAID_SERVICES_IP_ADDRESS
Description: IP addresses (IPV4 or IPV6) or hostname. Max. length 254.
Enter the IP address (IPV4 or IPV6) or host name of the machine on which File-AID Services is running. This must be the same as the value entered during the configuration of the Data Studio. If your site uses dynamic IP address, specifying the host name eliminates updating this parameter whenever the IP address changes.
If you enter an IP address, use one of the following formats:
IPV4 dotted decimal format. None of the four decimal numbers should have a leading zero.
IPV6 in the following format:
x : x : x : x : x : x : x : xIn this format X represents a segment and it can be any hexadecimal value between 0 and FFFF.
or when specifying host name, use the fully qualified domain name servers (DNS) host name string.
Default: Blank
Required: Yes
FILEAID_SERVICES_USER_INTERFACE_PORT
Description: File-AID Data Privacy User Interface Port number (1025 - 65535). Max. length 5.
Enter the open TCP port to be used when repository and project lists are requested in the mainframe File-AID user interface. This must be the same as the File-AID User Interface Port specified during configuration of File-AID Services.
This communication is configured differently than the execution time communication to reduce the region size required for the user; the JVM (JAVA virtual machine) is not required for this communication.
Default: 5180
FILEAID_SERVICES_USER_EXECUTION_PORT
Description: File-AID Data Privacy Execution Port number (1025 - 65535). Max. length 5.
Enter the open TCP port to be used for execution time (batch) communication with File-AID Services. This port will be used to retrieve the appropriate Dynamic Privacy Rules from the requested repository and project.
This must be the same as the File-AID Data Privacy execution port specified during configuration of File-AID Services.
Default: 4180
z/OS UNIX Path Names for Java environment
The following parameters are available to specify z/OS UNIX Path information:
JAVA_VIRTUAL_MACHINE_PATH
Description:Path Name for Java Virtual Machine (JVM). Max. length 512.
Specify the z/OS UNIX path for the directory where your JAVA JVM is installed.
The path must start with a forward slash, e.g. “/usr/lpp/java/J8.0/” and should end with a forward slash.
Default: blank
Required: yes
FILEAID_RULES_ENGINE_PATH
Description: Path Name for File-AID Rules Engine (FARE). Max. length 512.
z/OS UNIX path name of your site’s File-AID Rules Engine (FARE) (formerly Common Disguise Engine, or CDE) - max 512 chars.
All Dynamic Privacy Rules are applied by the File-AID Rules Engine (FARE). When DPR is requested from a mainframe product, FARE must be installed on z/OS UNIX.
Specify the z/OS UNIX path where FARE is installed.
The path must start with a forward slash, e.g. “/u/fa/busezt0/FARE/” and should end with a forward slash.
Default: blank
Required: yes
File-AID Data Privacy Environment Additional Parameters (FADPALL)
FILEAID_RULES_ENGINE_LOG_PATH
Default: Path Name for FARE Log Directory. Max. length 512.
z/OS UNIX path name of your site’s File-AID Rules Engine’s logs.
If the Path for the File-AID Rules Engine Log Directory is not specified (default), then the Path for File-AID Rules Engine will be suffixed with "log" and used as the Log Directory.
The path must start with a forward slash, and should end with a forward slash.none
Java Options
You can specify up to 10 JVM Options, up to 80 chars per option.
JAVAOPN1
JAVAOPN2
JAVAOPN3
JAVAOPN4
JAVAOPN5
JAVAOPN6
JAVAOPN7
JAVAOPN8
JAVAOPN9
JAVAOPNA
Description: Specify the Java runtime parameters for File-AID Data Privacy. Max. length 80.
These Java options are the parameters required for execution of DPR.
Default: -verbose:sizes (for JAVAOPN1 only)
If you use any of the preceding JVM options, the following list describes the minimum requirement for 31-bit:
-Xmns256M
-Xmos256M
-Xms512M
-Xmox512M
-Xmx512M
-Xiss2K
-Xmcrs400M
-Xscmx712M
If you use any of the preceding JVM options, the following list describes the minimum requirement for 64-bit:
-Xmns256M
-Xmos256M
-Xms512M
-Xmox512M
-Xmx1024M
-Xiss2K
-Xmcrs400M
-Xscmx712M
TCP/IP Options
TCPIP_STACK_NAME
Description:TCP/IP Stack Name. Max. length 8.
Specify the name of the TCP/IP stack that File-AID Data Privacy (online / batch) will use. If left blank, the default TCP/IP stack name will be used.
Default: blank.
Special Instructions for Oracle Translate Table
If your Data Privacy job uses Data Translation with an Oracle Translate Table, you need to specify the following two JAVA options:
-Dlog.encoding=IBM1047
Adding these two lines makes it possible to run an Oracle translation while the log is generated in EBCDIC.