Writer instructions

Purpose

Use this page to display a banner announcement on each page of the space. Create the Space announcements page in the master space, outside of the Home branch.

You can version the Space announcements page to enable different banners to be published into different target spaces, however, the banner that is displayed in the versioned (master) space itself only displays the most recently-published banner.  If you find errors in the banner area of your versioned space and you are sure the Space announcements page is set up correctly, try publishing the page to the same space.

For more information, see Space-announcements-banners.

Removing

When an announcement is no longer needed, remove the BMC Space Banner macro.

Translation

Localized spaces using the L10n Viewport theme must change the name of this page to Space announcements l10n.  See Configuring-the-Scroll-ViewPort-theme-for-translated-spaces.

Usage

Choose one or none of the following BMC Space Banner macros.

If your space requires another kind of announcement, you can use this page in coordination with your team lead and editors.

When should I use a space announcement banner?

Use the space organization announcement after you change the content from a book-like organization (such as User Manual, Configuration Manual, and Administration Guide) to the product model.

Use the latest version announcement to push traffic to later versions. You do not need to add this to every previous version, but if you have a specific reason that you want users to be aware—for example, Google searches show content for an obsolete version—use the banner to help users find a relevant version.

When an announcement is no longer needed, remove the BMC Space Banner macro.

Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

File-AID Data Privacy Environment


Important

Required for:

  • File-AID/Data Solutions with Topaz Workbench Data Studio’s Data Privacy option.
  • File-AID for IMS/ISPF with Topaz Workbench Data Studio’s Data Privacy option.
  • File-AID/RDX with Topaz Workbench Data Studio’s Data Privacy option.
  • File-AID for Db2 with Topaz Workbench Data Studio’s Data Privacy option

The File-AID Data Privacy parameters provide configuration options for the Dynamic Privacy Rules (DPR) created with Data Studio’s Data Privacy. These parameters are only needed when the Data Studio’s Data Privacy component of the Topaz Workbench is installed and DPR is to be used.

Important

Data Studio’s Data Privacy must have been installed per the instructions in Topaz for Enterprise Data Installation and Configuration Guide before proceeding with this step.

Also, this task can be skipped during initial configuration of File-AID and returned to later, after the Data Studio’s Data Privacy installation (File-AID Services1, File-AID Rules Engine, etc.) has been completed.

Important

1: File-AID Services used to be called Compuware Workbench Server in previous releases.

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.

Important

z/OS UNIX file/path names are CaSe SEnSiTiVE. Enter all path names fully qualified without quotes.

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)

FILEAID_SERVICES_IP_ADDRESS

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 Topaz Enterprise Data. 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.

    Example

    10.10.10.0

  • 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.

    Example

    2001 : db8: 3333 : 4444 : 5555 : 6666 : 7777 : 8888

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:Data Studio’s 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:Data Studio’s 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 Data Studio’s 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.

Important

JAVA_VIRTUAL_MACHINE_PATH parameter can point to either a 31-bit or a 64-bit Java, but a 64-bit Java requires a File-AID Rules Engine (FARE) from Topaz for Enterprise Data 20.06.01 or later.

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

Data Studio’s Data Privacy Environment Additional Parameters (FADPALL) 

Important

Review the ALL PARMLIB member to see which of the additional parameters require site specific changes. You only need to copy those individual parameters to your site PARMLIB member that require non-default parameter values.

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 Data Studio’s 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 Data Studio’s 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:

-Dfile.encoding=UTF-8
-Dlog.encoding=IBM1047

Adding these two lines will make it possible to run an Oracle translation while the log will be generated in EBCDIC.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*