Broker attributes

The Broker attribute file contains a series of parameters (attributes) that control the availability and characteristics of clients and servers, as well as of the Broker itself. You can customize the Broker environment by modifying the attribute settings.

This section lists EntireX Broker parameters applicable to operating system Windows only. For attributes applicable to all operating systems, see Broker attributes in the platform-independent Administration documentation.

Name and location of attribute file

The name and location of the broker attribute file is platform-dependent.

Table 1. Attribute file location
Platform	File Name/Location
Windows	File <`BrokerName`>.atr in directory <`InstDir`>\EntireX\config\etb\<`BrokerName`> (default). *

*When starting a broker manually, name and location of the broker attribute file can be overwritten with the environment variable ETB_ATTR.

Attribute syntax

Each entry in the attribute file has the format:

ATTRIBUTE-NAME=value

The following rules and restrictions apply:

A line can contain multiple entries separated by commas.
Attribute names can be entered in mixed upper and lowercase.
Spaces between attribute names, values and separators are ignored.
Spaces in the attribute names are not allowed.
Commas and equal signs are not allowed in value notations.
Lines starting with an asterisk (*) are treated as comment lines. Within a line, characters following an * or # sign are also treated as comments.
The CLASS keyword must be the first keyword in a service definition.
Multiple services can be included in a single service definition section. The attribute settings will apply to all services defined in the section.
Attributes specified after the service definition (CLASS, SERVER, SERVICE keywords) overwrite the default characteristics for the service.
Attribute values can contain variables of the form ${variable name} or $variable name:
- Due to variations in EBCDIC codepages, braces should only be used on ASCII (Linux® or Windows) platforms or EBCDIC platforms using the IBM®-1047 (US) codepage.
- The variable name can contain only alphanumeric characters and the underscore (_) character.
- The first non-alphanumeric or underscore character terminates the variable name.
- Under Linux and Windows, the string ${variable name} is replaced with the value of the corresponding environment variable.
- Under z/OS®, variable values are read from a file defined by the DD name ETBVARS. The syntax of this file is the same as the attribute file.
- If a variable has no value: if the variable name is enclosed in braces, error 00210594 is given, otherwise $variable name will be used as the variable value.
- If you encounter problems with braces (and this is quite possible in a z/OS environment), we suggest you omit the braces.

Broker-specific attributes

The broker-specific attribute section begins with the keyword DEFAULTS=BROKER. It contains attributes that apply to the broker. At startup time, the attributes are read and duplicate or missing values are treated as errors. When an error occurs, the broker stops execution until the problem is corrected.

Tip: To avoid resource shortages for your applications, be sure to specify sufficiently large values for the broker attributes that define the global resources.

Table 2. Broker-specific attributes
Attribute	Values	Opt/Req	Operating System
Attribute	Values	Opt/Req	z/OS	Linux	Windows
ABEND-LOOP-DETECTION	YES \| NO	O	z	u	w
ABEND-LOOP-DETECTION	YES Stop broker if a task terminates abnormally twice, that is, the same abend reason at the same abend location already occurred. This attribute prevents an infinite abend loop. NO Use only if requested by IBM Support. This setting may make sense if a known error leads to an abnormal termination, but a hotfix solving the problem has not yet been provided. Reset to YES when the hotfix has been installed.
ABEND-MEMORY-DUMP	YES \| NO	O	z	u	w
ABEND-MEMORY-DUMP	YES Print all data pools of the broker if a task terminates abnormally. This dump is needed to analyze the abend. NO If the dump has already been sent to Software AG, you can set to NO to avoid the extra overhead.
ACCOUNTING	NO \| 128-255	O	z
	NO \| YES[SEPARATOR`=char`]	O		u	w
	Determines whether accounting records are created. NO Do not create accounting records. nnn The SMF record number to use when writing the accounting records. YES Create accounting data. `char=` separator character(s). Up to seven separator characters can be specified using the SEPARATOR suboption, for example: ACCOUNTING = (YES, SEPARATOR=;) If no separator character is specified, the comma character will be used. For more information, see Accounting in EntireX Broker under z/OS \| Linux \| Windows.
ACCOUNTING-VERSION	1 \| 2 \| 3 \| 4 \| 5	O	z	u	w
ACCOUNTING-VERSION	Determines whether accounting records are created. 1 Collect accounting information. This value is supported for reasons of compatibility with EntireX Broker 7.2.1 and earlier. 2 Collect extended accounting information in addition to that available with option 1. 3 Create accounting records in layout of version 3. 4 Create accounting records in layout of version 4. 5 Create accounting records in layout of version 5. This parameter applies when ACCOUNTING is activated.
ACI-CONVERSION	YES \| NO	O	z	u	w
ACI-CONVERSION	Determines the handling of ACI request and response strings of USTATUS. YES Convert ACI request and response strings with ICU. For more information, see ICU conversion in the Internationalization documentation. NO Translate ACI request and response with internal translation table without support of national characters. For more information, see Translation user exit in the Internationalization documentation. Note: This attribute was undocumented in EntireX versions prior to 10.3 and had default value NO. This meant that a translation user exit was used instead; this is no longer recommended.
APPLICATION-MONITORING or APPMON	YES \| NO	O	z	u	w
APPLICATION-MONITORING or APPMON	Enable application monitoring in EntireX Broker. YES Enable application monitoring. NO Disable application monitoring. For more information, see Application monitoring
ARF-DIAGNOSTIC-MESSAGES	NO	O	z	u	w
ARF-DIAGNOSTIC-MESSAGES	YES Report activities related to Adabas replication services. NO Do not report activities related to Adabas replication services.
AUTOLOGON	YES \| NO	O	z	u	w
AUTOLOGON	YES LOGON occurs automatically during the first SEND or REGISTER. NO The application has to issue a LOGON call.
AUTOSTART	NO \| YES	O		u	w
AUTOSTART	This attribute defines the autostart behavior of a broker. NO Broker is not started automatically with the next system start. YES Broker is restarted automatically with the next system start. Note: Prior to EntireX version 10.5 this was handled by the Broker Administration Service.
BLACKLIST-PENALTY-TIME	5M \| `n` \| `n`S \| `n`M \| `n`H	R	z	u	w
BLACKLIST-PENALTY-TIME	Define the length of time a participant is placed on the PARTICIPANT‑BLACKLIST to prevent a denial-of-service attack. n Same as nS. nS Non-activity time in seconds (max. 2147483647). nM Non-activity time in minutes (max. 35791394). nH Non-activity time in hours (max. 596523). For more information, see Protecting a Broker against Denial-of-Service attacks under z/OS \| Linux \| Windows.
BROKER-ID	A32	R	z	u	w
BROKER-ID	Identifies the broker to which the attribute file applies. The broker ID must be unique per machine.
CLIENT-NONACT	15M \| `n` \| `n`S \| `n`M \| `n`H	R	z	u	w
CLIENT-NONACT	Define the non-activity time for clients. n Same as nS. nS Non-activity time in seconds (max. 2147483647). nM Non-activity time in minutes (max. 35791394). nH Non-activity time in hours (max. 596523). A client that does not issue a broker request within the specified time limit is treated as inactive and all resources for the client are freed.
CMDLOG	NO \| YES	O	z	u	w
CMDLOG	NO Command logging will not be available in the broker. YES Command logging features will be available in the broker.
CMDLOG-FILE-SIZE	1024 \| `n`	O	z	u	w
CMDLOG-FILE-SIZE	Defines the maximum size of the file that the command log is written to, in kilobytes. The value must be 1024 or higher. The default value is 1024. When one command log file grows to this size, broker starts writing to the other file. For more details, see Command logging in EntireX.
CONTROL-INTERVAL	60S \| `n` \| `n`S \| `n`M \| `n`H	O	z	u	w
CONTROL-INTERVAL	Defines the time interval of time-driven broker-to-broker calls. It controls the time between handshake attempts. The standby broker will check the status of the standard broker after the elapsed CONTROL-INTERVAL time. n Same as nS. nS Interval in seconds (max. 2147483647). nM Interval in minutes (max. 35791394). nH Interval in hours (max. 596523). The minimum value is 16 seconds. We strongly recommend the default value (60 seconds), except for very slow machines.
CONTROL-REPLY	NO	O	z	u	w
CONTROL-REPLY	YES Resources will be immediately cleaned up. NO Resources for a cancelled request due to `<connection reset>` will be cleaned up after elapsed timeouts.
CONV-DEFAULT	UNLIM \| `n`	O	z	u	w
CONV-DEFAULT	Default number of conversations that are allocated for every service. UNLIM The number of conversations is restricted only by the number of conversations globally available. Precludes the use of NUM‑CONVERSATION. n Number of conversations. This value can be overridden by specifying a CONV-LIMIT for the service. A value of 0 (zero) is invalid.
DEFERRED	NO \| YES	O	z	u	w
DEFERRED	Disable or enable deferred processing of units of work. NO Units of work cannot be sent to the service until it is available. YES Units of work can be sent to a service that is not up and registered. They will be processed when the service becomes available.
DYNAMIC-MEMORY-MANAGEMENT	YES \| NO	O	z	u	w
DYNAMIC-MEMORY-MANAGEMENT	YES An initial portion of memory is allocated at broker startup based on defined NUM-* attributes or internal default values if no NUM-* attributes have been defined. More memory is allocated without broker restart if there is a need to use more storage. Unused memory is deallocated. The upper limit of memory consumption can be defined by the attribute MAX-MEMORY. For more information, see Dynamic memory management. NO All memory is allocated at broker startup based on the calculation from the defined NUM-* attributes. Size of memory cannot be changed. This was the known behavior of EntireX 7.3 and earlier. If you run your broker with attribute DYNAMIC-MEMORY-MANAGEMENT=YES, the following attributes are not needed: CONV-DEFAULT HEAP-SIZE LONG-BUFFER-DEFAULT SERVER-DEFAULT SHORT-BUFFER-DEFAULT NUM-CLIENT NUM-CMDLOG-FILTER NUM-COMBUF NUM-CONV[ERSATION] NUM-LONG[-BUFFER] NUM-SERVER NUM-SERVICE-EXTENSION NUM-SERVICE NUM-SHORT[-BUFFER] NUM-UOW\|MAX-UOWS\|MUOW NUM-WQE CAUTION: However, if one of these attributes is defined, it determines the allocation size of that particular broker resource.
DYNAMIC-WORKER-MANAGEMENT	NO \| YES	O	z	u	w
DYNAMIC-WORKER-MANAGEMENT	NO All worker tasks are started at broker startup. The number of worker tasks is defined by NUM-WORKER. After this initial step, no further worker tasks can be started. This is default and simulates the behavior of EntireX version 8.0 and earlier. YES The initial portion of worker tasks started at broker startup is determined by NUM-WORKER. However, if there is a need to handle an increased workload, additional worker tasks can be started at runtime without restarting broker. Conversely, if a worker task remains unused, it is stopped. The upper and lower limit of running worker tasks can be defined by the attributes WORKER-MIN and WORKER-MAX. If you run broker with DYNAMIC-WORKER-MANAGEMENT=YES, the following attributes are useful to optimize the overall processing: WORKER‑MAX WORKER‑QUEUE‑DEPTH WORKER‑MIN WORKER‑START‑DELAY WORKER‑NONACT The attribute NUM-WORKER defines the initial number of worker tasks started during initialization. For more information, see Dynamic worker management.
ETBCOM	NO \| YES	O	z	u	w
	YES \| NO	O
	Bundles the output of the various broker tasks in task ETBCOM.
HEAP-SIZE	1024 \| `n`	O	z	u	w
HEAP-SIZE	Defines the size of the internal heap in KB. Not required if you are using DYNAMIC‑MEMORY‑MANAGEMENT. If you are not using dynamic memory management, we strongly recommend specifying - as a minimum - the default value of 1024 KB.
ICU-CONVERSION	YES \| NO	O	z	u	w
ICU-CONVERSION	Disable or enable ICU conversion. YES ICU is loaded and available for conversion. It is a prerequisite for CONVERSION=SAGTCHA and CONVERSION=SAGTRPC. NO ICU is not loaded and not available for conversion. CONVERSION=SAGTCHA and CONVERSION=SAGTRPC cannot be used. If any of the broker service definitions uses the character conversion approach ICU conversion, that is, CONVERSION=SAGTCHA or CONVERSION=SAGTRPC, ICU-CONVERSION must be set to YES. If you are using only a user exit (see User exits) or CONVERSION=NO as character conversion approach for all your broker service definitions, ICU-CONVERSION can be set to NO. ICU requires additional storage to run properly. If ICU conversion is not needed, setting ICU-CONVERSION to NO will help to avoid unnecessary storage consumption.
ICU-DATA-DIRECTORY	Folder or directory name in quotes.	O	z	u	w
ICU-DATA-DIRECTORY	The location where the broker searches for ICU custom converters. See Building and installing ICU custom converters under z/OS \| Linux \| Windows.
ICU-SET-DATA-DIRECTORY	YES \| NO	O	z	u	w
ICU-SET-DATA-DIRECTORY	Disable or enable ICU custom converter usage. YES The broker tries to locate ICU custom converters with the mechanism defined by the platform. See Building and installing ICU custom converters under z/OS \| Linux \| Windows. NO Use of ICU custom converters is not possible.
IPV6	YES \| NO	O	z	u	w
IPV6	YES Establish SSL and TCP/IP transport in IPv6 and IPv4 networks according to the TCP/IP stack configuration. NO Establish SSL and TCP/IP transport in IPv4 network only. This attribute applies to EntireX version 9.0 and later.
LONG-BUFFER-DEFAULT	UNLIM \| `n`	O	z	u	w
LONG-BUFFER-DEFAULT	Number of long buffers to be allocated for each service. UNLIM The number of long message buffers is restricted only by the number of buffers globally available. Precludes the use of NUM‑LONG‑BUFFER. n Number of buffers. This value can be overridden by specifying a LONG-BUFFER-LIMIT for the service. A value of 0 (zero) is invalid.
MAX-MEMORY	0 \| `n` \| `n`K \| `n`M \| `n`G \| UNLIM	O	z	u	w
MAX-MEMORY	Defines the upper limit of memory allocated by broker if DYNAMIC-MEMORY-MANAGEMENT=YES has been defined. 0, UNLIM No memory limit. others Defines the maximum limit of allocated memory. If limit is exceeded, error 671 `Requested allocation exceeds MAX-MEMORY` is generated.
MAX-MESSAGE-LENGTH	2147483647 \| `n`	O	z	u	w
MAX-MESSAGE-LENGTH	Maximum message size that the broker kernel can process. This value is transport-dependent. The default value represents the highest positive number that can be stored in a four-byte integer.
MAX-MESSAGES-IN-UOW	16 \| `n`	O	z	u	w
MAX-MESSAGES-IN-UOW	Maximum number of messages in a unit of work.
MAX-MSG	See MAX‑MESSAGE‑LENGTH.
MAX-TRACE-FILES	4 \| `n`	O		u	w
MAX-TRACE-FILES	Defines the number of backup copies of the trace file ETB.LOG. Minimum number is 1; maximum is 999. A new trace file is allocated when the value for TRACE‑FILE‑SIZE is exceeded. These two attributes prevent a constantly growing ETB.LOG file. For more information, see Trace file handling under Linux \| Windows.
MAX-UOW-MESSAGE-LENGTH	See MAX‑MESSAGE‑LENGTH.
MAX-UOWS	0 \| `n`	O	z	u	w
MAX-UOWS	The maximum number of UOWs that can be concurrently active broker-wide. The default value is 0 (zero), which means that the broker will process only messages that are not part of a unit of work. If UOW processing is to be done by any service, a MAX-UOWS value must be 1 or larger for the broker. The MAX-UOWS value for the service will default to the value set for the broker. NUM‑UOW is an alias of this parameter.
MESSAGE-CASE	NONE \| UPPER \| LOWER	O	z	u	w
MESSAGE-CASE	Indicates if certain error message texts returned by the broker to its clients or written by the broker to its log file are to be in mixed case, uppercase, or lowercase. NONE No changes are made to message case. UPPER Messages are changed to uppercase. LOWER Messages are changed to lowercase.
MUOW	See NUM‑UOW.
NEW-UOW-MESSAGES	YES \| NO	O	z	u	w
NEW-UOW-MESSAGES	YES New UOW messages are allowed. NO New UOW messages are not allowed. This applies to UOW when using Persistence and should not be used for non-persistent UOWs. A usage example could be the following: The broker persistent store reaches capacity and the broker shuts down. You can set NEW-UOW-MESSAGES to NO to prevent new UOW messages from being added after a broker restart. This action allows only consumption (not production) of UOWs to occur after broker restart. After the persistent store capacity has been sufficiently reduced, the EntireX Broker administrator can issue a CIS command, see ALLOW-NEWUOWMSGS. This action allows new UOW messages to be sent to the broker. Reset attribute NEW-UOW-MESSAGES to YES, which permits new UOW messages to be produced in subsequent broker sessions.
NUM-BLACKLIST-ENTRIES	256 \| `n`	O	z	u	w
NUM-BLACKLIST-ENTRIES	Number of entries in the participant blacklist. Default value is 256 entries. Together with BLACKLIST‑PENALTY‑TIME and PARTICIPANT‑BLACKLIST, this attribute is used to protect a broker running with SECURITY=YES against denial-of-service attacks. For more information, see Protecting a Broker against Denial-of-Service attacks under z/OS \| Linux \| Windows. .
NUM-CLIENT	`n`	R	z	u	w
NUM-CLIENT	Number of clients that can access the broker concurrently. A value of 0 (zero) is invalid.
NUM-CMDLOG-FILTER	1 \| `n`	O	z	u	w
NUM-CMDLOG-FILTER	Maximum number of filters that can be specified simultaneously. Tip: We recommend you limit this value to the number of services that are being monitored. Minimum value is 1. A value of zero is invalid when the attribute CMDLOG is set to YES. For more information, see Command logging in EntireX.
NUM-COMBUF	1024 \| 1-999999	R	z	u	w
NUM-COMBUF	Determines the maximum number of communication buffers available for processing commands arriving in the broker kernel. The size of one communication buffer is usually 16 KB split into 32 slots of 512 bytes, but it ultimately depends on the hardware architecture of your CPU. A value of 0 (zero) is invalid.
NUM-CONVERSATION or NUM-CONV	`n` \| AUTO	R	z	u	w
NUM-CONVERSATION or NUM-CONV	Defines the number of conversations that can be active concurrently. The number specified should be high enough to account for both conversational and non-conversational requests. (Non-conversational requests are treated internally as one-conversation requests.) n Number of conversations. AUTO Uses the CONV-DEFAULT and the service-specific CONV-LIMIT values to calculate the number of conversations. Do not set the values used in the calculation to UNLIM. Note: A value of 0 (zero) is invalid. If a wildcard service is defined in the service-specific section of the attribute file, the value of AUTO is invalid. For more information, see Wildcard service definitions.
NUM-LONG-BUFFER or NUM-LONG	4096 \| `n` \| AUTO	R	z	u	w
NUM-LONG-BUFFER or NUM-LONG	Defines the number of long message containers. Long message containers have a fixed length of 4096 bytes and are used to store requests that are larger than 2048 bytes. Storing a request of 8192 bytes, for example, would require two long message containers. n Number of buffers. AUTO Uses the LONG-BUFFER-DEFAULT and the service-specific LONG-BUFFER-LIMIT values to calculate the number of long message buffers. Do not set the values used in the calculation to UNLIM. A value of 0 (zero) is invalid. In non-conversational mode, message containers are released as soon as the client receives a reply from the server. If no reply is requested, message containers are released as soon as the server receives the client request. In conversational mode, the last message received is always kept until a new one is received. Note: If a catch-all service is defined in the service-specific section of the attribute file, the value of AUTO is invalid. For more information, see Wildcard service definitions.
NUM-PARTICIPANT-EXTENSION	`n`	O	z	u	w
NUM-PARTICIPANT-EXTENSION	Defines the number of participant extensions to link participants as clients and servers. n Number of participant extensions. not specified If this attribute is not set, the default value is calculated based on NUM-CLIENT and NUM-SERVER. A value of 0 (zero) is invalid.
NUM-SERVER	`n` \| AUTO	R	z	u	w
NUM-SERVER	Defines the number of servers that can offer services concurrently using the broker. This is not the number of services that can be registered to the broker (see NUM‑SERVICE). n Number of servers. AUTO Uses the SERVER-DEFAULT and the service-specific SERVER-LIMIT values to calculate the number of servers. Do not set the values used in the calculation to UNLIM. Note: Setting this value higher than the number of services allows the starting of server replicas that provide the same service. A value of 0 (zero) is invalid. If a wildcard service is defined in the service-specific section of the attribute file, the value of AUTO is invalid. For more information, see Wildcard service definitions.
NUM-SERVICE	`n`	R	z	u	w
NUM-SERVICE	Defines the number of services that can be registered to the broker. This is not the number of servers that can offer the services (see NUM‑SERVER). A value of 0 (zero) is invalid.
NUM-SERVICE-EXTENSION	`n` \| AUTO	O	z	u	w
NUM-SERVICE-EXTENSION	Defines the number of service extensions to link servers to services. n Number of service extensions. AUTO Uses the value specified or calculated for NUM-SERVER + NUM-CLIENT, plus an extra cushion. not specified If this attribute is not set, the default value is NUM-SERVER multiplied by NUM-SERVICE. The minimum value is NUM-SERVER. The maximum value is NUM-SERVER multiplied by NUM-SERVICE. Caution is recommended with this attribute: Set this attribute only if the storage resources allocated for service extensions need to be restricted. Note that the value `n` allows only the specified number of server instances of `n` to be used. Value AUTO will calculate the number of allowed server instances from NUM-SERVER, which itself might be set to AUTO. In this case, this also considers the value of SERVER-DEFAULT and even the individual SERVER-LIMIT for each service definition.
NUM-SHORT-BUFFER or NUM-SHORT	`n` \| AUTO	R	z	u	w
NUM-SHORT-BUFFER or NUM-SHORT	Defines the number of short message containers. Short message containers have a fixed length of 256 bytes and are used to store requests of no more than 2048 bytes. To store a request of 1024 bytes, for example, would require four short message containers. n Number of buffers. AUTO Uses the SHORT-BUFFER-DEFAULT and the service-specific SHORT-BUFFER-LIMIT values to calculate the number of short message buffers. Do not set the values used in the calculation to UNLIM. Note: In non-conversational mode, message containers are released as soon as the client receives a reply from the server. If no reply is requested, message containers are released as soon as the server receives the client request. In conversational mode, the last message received is always kept until a new one is received. If a wildcard service is defined in the service-specific section of the attribute file, the value of AUTO is invalid. For more information, see Wildcard service definitions.
NUM-UOW	0 \| `n`	O	z	u	w
NUM-UOW	The maximum number of UOWs that can be concurrently active broker-wide. The default value is 0 (zero), which means that the broker will process only messages that are not part of a unit of work. If UOW processing is to be done by any service, a NUM-UOW value must be 1 or larger for the broker. (MAX-UOWS is an alias for this attribute.) The NUM-UOW value for the service will default to the value set for the broker.
NUM-WORKER	1 \| `n` (max. 64)	R	z	u	w
NUM-WORKER	Number of worker tasks that the broker can use. The number of worker tasks determines the number of functions (SEND, RECEIVE, REGISTER, etc.) that can be processed concurrently. At least one worker task is required; this is the default value.
NUM-WQE	1-32768	R	z	u	w
NUM-WQE	Maximum number of requests that can be processed by the broker in parallel, over all transport mechanisms. Each broker command is assigned a worker queue element, regardless of the transport mechanism being used. This element is released when the user has received the results of the command, including the case where the command has timed out.
PARTICIPANT-BLACKLIST	YES \| NO	R	z	u	w
PARTICIPANT-BLACKLIST	Determines whether participants attempting a denial-of-service attack on the broker are to be put on a blacklist. YES Create a participant blacklist. NO Do not create a participant blacklist. For more information, see Protecting a Broker against Denial-of-Service attacks under z/OS \| Linux \| Windows.
PERCENTAGE-FOR-CONNECTION-SHORTAGE-MESSAGE	90 \| 1-100	O	z	u	w
PERCENTAGE-FOR-CONNECTION-SHORTAGE-MESSAGE	Broker will issue a message if the defined percentage value of TCP/IP connections (available file descriptors) is exceeded. Default is 90 percent of the available file descriptors.
POSTPONED-QUEUE	YES \| NO	O	z	u	w
POSTPONED-QUEUE	Enable or disable the creation of a postponed queue for Broker. YES Enable creation of a postponed queue. Define your postponed queue with service-specific attributes POSTPONE‑ATTEMPTS and POSTPONE‑DELAY. NO Disable creation of a postponed queue. See Postponing units of work.
PSTORE	NO \| HOT \| COLD	O	z	u	w
PSTORE	Defines the status of the persistent store at broker startup, including the condition of persistent units of work (UOWs). With any value other than NO, PSTORE-TYPE must be set. NO No persistent store. HOT Persistent UOWs are restored to their prior state during initialization. COLD Persistent UOWs are not restored during initialization, and the persistent store is considered empty. Note: For a hot or cold start, the persistent store must be available when your broker is restarted.
PSTORE-REPORT	NO \| YES	O	z	u	w
PSTORE-REPORT	Determines whether PSTORE report is created. NO Do not create the PSTORE report file. YES Create the PSTORE report file. See Postponing units of work.
PSTORE-TYPE	DIV (z/OS) \| FILESYSTEM (Linux, Windows) \| ADABAS (all platforms)	O	z	u	w
PSTORE-TYPE	Describes the type of persistent store driver required. DIV Data in Virtual. z/OS only, and default on this platform. FILESYSTEM Uses the file system of the Operating System on Linux \| Windows. ADABAS Adabas. All platforms. For more information, see Adabas-specific attributes and Managing the Broker Persistent Store under z/OS \| Linux \| Windows.
PSTORE-VERSION	5 \| 6	O	z	u	w
PSTORE-VERSION	Determines the version of the persistent store. PSTORE-VERSION=5 and PSTORE-VERSION=6 are supported. There is a significant difference for PSTORE-TYPE=ADABAS: 6 Adabas Large Object Files (LOBs) are supported. 5 No LOB support. Default is PSTORE-VERSION=6. Note: To change the value of PSTORE-VERSION, the persistent store must be empty (all units of work must be consumed). If the persistent store is not empty, the start of the Broker with a changed PSTORE-VERSION may fail with error ETBE0741 or ETBM0745. To change the value of PSTORE-VERSION from 5 to 6 for PSTORE-TYPE=ADABAS, you need to create new Adabas files. For more information, see Implementing an Adabas database as Persistent store under z/OS \| Linux \| Windows.
SECURITY	NO \| YES	O	z	u	w
SECURITY	Determines whether EntireX Security is activated. NO EntireX Security is not activated. YES EntireX Security is activated. For more information, see Security.
SECURITY-REPORT	NO \| YES	O	z	u	w
SECURITY-REPORT	Determines whether a report on security-related events in broker is created. NO Do not create security report. YES Create security report if SECURITY=YES is defined. See also Security report in the EntireX Broker documentation.
SERVER-DEFAULT	`n` \| UNLIM	O	z	u	w
SERVER-DEFAULT	Default number of servers that are allowed for every service. n Number of servers. UNLIM The number of servers is restricted only by the number of servers globally available. Precludes the use of NUM-SERVER=AUTO. This value can be overridden by specifying a SERVER-LIMIT for the service. A value of 0 (zero) is invalid.
SERVICE-UPDATES	YES \| NO	O	z	u	w
SERVICE-UPDATES	Switch on/off the automatic update mode of the broker. YES The broker reads the attribute file whenever a service registers for the first time. This allows the broker to honor modifications in the attribute file without a restart. The attribute file is read only when the first server registers for a particular service; it is not reread when a second replica is activated. NO The attribute file is read only once during broker startup. Any changes to the attribute file will be honored only if the broker is restarted.
SHORT-BUFFER-DEFAULT	UNLIM \| `n`	O	z	u	w
SHORT-BUFFER-DEFAULT	Number of short buffers to be allocated for each service. UNLIM The number of short message buffers is restricted only by the number of buffers globally available. Precludes the use of NUM-SHORT-BUFFER=AUTO. n Number of buffers. This value can be overridden by specifying a SHORT-BUFFER-LIMIT for the service. A value of 0 (zero) is invalid.
STORAGE-REPORT	NO \| YES	O	z	u	w
STORAGE-REPORT	Create a storage report about broker memory usage. NO Do not create the storage report. YES Create the storage report. For more information, see Storage report.
STORE	OFF \| BROKER	O	z	u	w
STORE	Sets the default STORE attribute for all units of work. This attribute can be overridden by the STORE field in the Broker ACI control block. OFF Units of work are not persistent. BROKER Units of work are persistent.
TRACE-FILE-SIZE	`n` \| `n`K \| `n`M \| `n`G	O		u	w
TRACE-FILE-SIZE	Defines the size of one trace file in kilobytes, megabytes or gigabytes. If this size is exceeded, a new trace file is allocated until the maximum number of trace files specified with MAX‑TRACE‑FILES is reached. There is no default value. These two parameters help prevent a constantly growing ETB.LOG file. For more information, see Trace file handling under Linux \| Windows.
TRACE-LEVEL	0-4	O	z	u	w
TRACE-LEVEL	The level of tracing to be performed while the broker is running. 0 No tracing. Default value. 1 Traces incoming requests, outgoing replies, resource usage and conversion errors. 2 All of trace level 1, plus all main routines executed. 3 All of trace level 2, plus all routines executed. 4 All of trace level 3, plus Broker ACI control block displays. Trace levels 2, 3 and 4 should be used only when requested by IBM Support. If you modify the TRACE-LEVEL attribute, you must restart the broker for the change to take effect. For temporary changes to TRACE-LEVEL without a broker restart, use Command Central or the EntireX Broker command-line utility ETBCMD.
TRANSPORT	TCP-NET \| TCP \| SSL \| NET	O	z
	TCP \| SSL	O		u	w
	The broker transport may be specified as any combination of one or more of the following methods: TCP TCP/IP is supported. SSL SSL/TLS is supported. NET Entire Net-Work is supported. This value is not supported for a broker under Linux or Windows. Examples: TRANSPORT=NET specifies that only the Entire Net-Work transport method will be supported by the broker. TRANSPORT=TCP-NET specifies that both the TCP/IP and Net-Work transport methods will be supported by the broker. TRANSPORT=TCP-SSL-NET specifies that the TCP/IP, SSL/TLS, and Entire Net-Work transport methods will be supported by the broker. The parameters for each transport method are described in the respective section: TCP \| SSL \| NET.
TRAP-ERROR	`nnnn`	O	z	u	w
TRAP-ERROR	Where `nnnn` is the four-digit API error number that triggers the trace handler, for example 0007 (Service not registered). Leading zeros are not required. There is no default value. See Deferred Tracing under z/OS \| Linux \| Windows.
TRBUFNUM	`n`	O	z	u	w
TRBUFNUM	Changes the trace to write trace data to internal trace buffers. `n` is the size of the trace buffer in 64 KB units. There is no default value.
TRMODE	WRAP	O	z	u	w
TRMODE	Changes the trace mode. WRAP is the only possible value. This value instructs broker to write the trace buffer (see TRBUFNUM) if an event occurs. This event is triggered by a matching TRAP‑ERROR during request processing or when an exception occurs.
UMSG	See MAX‑MESSAGES‑IN‑UOW.
UOW-DATA-LIFETIME	1D \| `n`S \| `n`M \| `n`H \| `n`D	O	z	u	w
UOW-DATA-LIFETIME	Defines the default lifetime for units of work for the service. nS Number of seconds the UOW can exist (max. 2147483647). nM Number of minutes the UOW can exist (max. 35791394). nH Number of hours the UOW can exist (max. 596523). nD Number of days the UOW can exist (max. 24855). If the UOW is inactive - that is, is not processed within the time limit - it is deleted and given a status of TIMEOUT. This attribute can be overridden by the UWTIME field in the Broker ACI control block. For more information, see Timeout considerations for EntireX Broker.
UOW-MSGS	See MAX‑MESSAGES‑IN‑UOW.
UOW-STATUS-LIFETIME	no value \| `n`[S] \| `n`M \| `n`H \| `n`D	O	z	u	w
UOW-STATUS-LIFETIME	The value to be added to the UOW‑DATA‑LIFETIME (lifetime of associated UOW). If a value is entered, it must be 1 or greater; a value of 0 will result in an error. If no value is entered, the lifetime of the UOW status information will be the same as the lifetime of the UOW itself. nS Number of seconds the UOW status exists longer than the UOW itself (max. 2147483647). nM Number of minutes (max. 35791394). nH Number of hours (max. 596523). nD Number of days (max. 24855). This attribute is ignored if PSTORE=NO is defined. The lifetime determines how much additional time the UOW status is retained in the persistent store and is calculated from the time at which the associated UOW enters any of the following statuses: PROCESSED, TIMEOUT, BACKEDOUT, CANCELLED, DISCARDED. The additional lifetime of the UOW status is calculated only when broker is executing. Value in UOW‑STATUS‑LIFETIME supersedes the value (if specified) in attribute UWSTATP. Note: If no unit is specified, the default unit is seconds. The unit does not have to be identical to the unit specified for UOW‑DATA‑LIFETIME.
UWSTAT-LIFETIME	Alias for UOW‑STATUS‑LIFETIME.
UWSTATP	0 \| `n`	O	z	u	w
UWSTATP	Contains a multiplier used to compute the lifetime of a persistent status for the service. The UWSTATP value is multiplied by the UOW‑DATA‑LIFETIME value (the lifetime of the associated UOW) to determine the length of time the status will be retained in the persistent store. 0 The status is not persistent. 1-254 Multiplied by the value of UOW-DATA-LIFETIME to determine how long a persistent status will be retained. Note: This attribute has not been supported since EntireX version 7.3. Use UOW‑STATUS‑LIFETIME instead.
UWTIME	Alias for UOW‑DATA‑LIFETIME.
WAIT-FOR-ACTIVE-PSTORE	NO \| YES	O	z	u	w
WAIT-FOR-ACTIVE-PSTORE	Determines whether broker should wait for the Adabas Persistent Store to become active, or until c-tree PSTORE files become available. NO If broker should start with a PSTORE-TYPE=ADABAS and the database is not active or is not accessible, broker will stop. If broker should start with a PSTORE-TYPE=CTREE and the c-tree files are still in use, broker will stop. YES If broker should start with a PSTORE-TYPE=ADABAS and the database is not active or is not accessible, broker will retry every 10 seconds to initiate communications with the PSTORE. Broker will reject any user requests until it is able to contact the Adabas database. If broker should start with a PSTORE-TYPE=CTREE and the c-tree files are still in use, broker will retry every 10 seconds to rebuild the persistent data. Broker will reject any user requests until it is able to rebuild the persistent data.
WORKER-MAX	64 \| `n` (min. 1, max. 64)	O	z	u	w
WORKER-MAX	Maximum number of worker tasks the broker can use.
WORKER-MIN	1 \| `n` (min. 1, max. 64)	O	z	u	w
WORKER-MIN	Minimum number of worker tasks the broker can use.
WORKER-NONACT	70S \| `n` \| `n`S \| `n`M \| `n`H	O	z	u	w
WORKER-NONACT	Non-activity time to elapse before a worker tasks is stopped. n Same as nS. nS Non-activity time in seconds (default 70, max. 2147483647). nM Non-activity time in minutes (max. 35791394). nH Non-activity time in hours (max. 596523). CAUTION: A value of 0 (zero) is invalid. If you set this value too low, additional overhead is required for starting and stopping worker tasks. The default and recommended value is 70S.
WORKER-QUEUE-DEPTH	1 \| `n` (min. 1)	O	z	u	w
WORKER-QUEUE-DEPTH	Number of unassigned user requests in the input queue before another worker task gets started. The default and recommended value is 1. A higher value will result in longer broker response times.
WORKER-START-DELAY	`internal-value` \| `n`	O	z	u	w
WORKER-START-DELAY	n Delay is extended by `n` seconds. Delay after a successful worker task invocation before another worker task can be started to handle current incoming workload. This attribute is used to avoid the risk of recursive invocation of worker tasks, because starting a worker task itself causes workload increase. If no value is specified, an internal value calculated by the broker is used to optimize dynamic worker management. This calculated value is the maximum time required to start a worker task.

Service-specific Attributes

Each section begins with the keyword DEFAULTS=SERVICE. Services with common attribute values can be grouped together. The attributes defined in the grouping apply to all services specified within it. However, if a different attribute value is defined immediately following the service definition, that new value applies. See also the sections Wildcard service definitions and Service update modes after the table.

Table 3. Service-specific attributes
Attribute	Values	Opt/Req	Operating System
Attribute	Values	Opt/Req	z/OS	Linux	Windows
APPLICATION-MONITORING or APPMON	YES \| NO	O	z	u	w
APPLICATION-MONITORING or APPMON	YES Enable application monitoring for the specified services. NO Disable application monitoring for the specified services. For more information, see Application monitoring.
APPLICATION-MONITORING-NAMEorAPPMON-NAME	A100	O	z	u	w
APPLICATION-MONITORING-NAMEorAPPMON-NAME	Specifies the application monitoring name. Used to set the value of the ApplicationName KPI. If omitted, the default value from the `APPLICATION-MONITORING` section is used. If this value is also not specified, the corresponding `CLASS`/`SERVER`/`SERVICE` names are used. For more information, see Application monitoring.
CLASS	A32 (case-sensitive)	R	z	u	w
CLASS	Part of the name that identifies the service together with the SERVER and SERVICE attributes. CLASS must be specified first, followed immediately by SERVER and SERVICE. The following rules apply: Classes starting with any of the following are reserved for use by Software AG. Do not use these in applications you write: BROKER, SAG, ENTIRE, ETB, RPC, ADABAS, NATURAL. Valid characters for class name are letters a-z, A-Z, numbers 0-9, hyphen and underscore. Do not use dollar, percent, period or comma. For more information, see the restriction for SERVICE attribute names.
CONV-LIMIT	UNLIM \| `n`	O	z	u	w
CONV-LIMIT	Allocates a number of conversations especially for this service. UNLIM The number of conversations is restricted only by the number of conversations globally available. Precludes the use of NUM-CONVERSATION=AUTO in the Broker section of the attribute file. n Number of conversations. A value of 0 (zero) is invalid. If NUM-CONVERSATION=AUTO is specified in the Broker section of the attribute file, CONV-LIMIT=UNLIM is not allowed in the service section. A value must be specified or the CONV-LIMIT attribute must be suppressed entirely for the service so that the default (CONV-DEFAULT) becomes active.
CONV-NONACT	5M \| `n` \| `n`S \| `n`M \| `n`H	R	z	u	w
CONV-NONACT	n Same as nS. nS Non-activity time in seconds (max. 2147483647). nM Non-activity time in minutes (max. 35791394). nH Non-activity time in hours (max. 596523). A value of 0 (zero) is invalid. If a connection is not used for the specified time, that is, a server or a client does not issue a broker request that references the connection in any way, the connection is treated as inactive and the allocated resources are freed.
CONVERSION	A255 ( SAGTCHA [, TRACE=`n`] [, OPTION=`s`] \| SAGTRPC [, TRACE=`n`] [, OPTION=`s`] \| `name` [, TRACE=`n`] \| NO )	O	z	u	w
CONVERSION	Defines ICU conversion or SAGTRPC user exit for character conversion. See Internationalization. SAGTCHA ⁽¹⁾ Conversion using ICU Conversion for ACI-based programming. SAGTRPC ⁽²⁾ Conversion using ICU Conversion for RPC-based components and Reliable RPC. `name` ⁽³⁾ Name of the SAGTRPC user exit for RPC-based components and Reliable RPC. For more information, see Configuring SAGTRPC user exits under z/OS \| Linux \| Windows and Writing SAGTRPC user exits under z/OS \| Linux \| Windows. NO If conversion is not to be used, either omit the CONVERSION attribute or specify CONVERSION=NO, for example for binary payload. The CONVERSION attribute overrides the TRANSLATION attribute when defined for a service. That is, when TRANSLATION and CONVERSION are both defined, TRANSLATION will be ignored. For more information, see Configuring ICU Conversion under z/OS \| Linux \| Windows. TRACE If tracing is switched on, the trace output is written to the broker log file. The following trace levels are available: 0 No tracing 1 STANDARD This level is an `on-error` trace. It provides information on conversion errors only. For RPC calls this includes the IDL library, IDL program and the data. Note that if OPTION values for conversion are set, errors are ignored. 2 ADVANCED Tracing of incoming, outgoing parameters and the payload. 3 SUPPORT This trace level is for support diagnostics. Use only when requested by IBM Support. OPTION For more information, see table of possible values under OPTION values for conversion.
DEFERRED	NO \| YES	O	z	u	w
DEFERRED	NO Units of work cannot be sent to the service until it is available. YES Units of work can be sent to a service that is not up and registered. The units of work will be processed when the service becomes available.
LOAD-BALANCING	YES \| NO	O	z	u	w
LOAD-BALANCING	YES When servers that offer a particular service are started, new conversations will be assigned to these servers in a round-robin fashion. The first waiting server will get the first new conversation, the second waiting server will get the second new conversation, and so on. NO A new conversation is always assigned to the first server in the queue.
LONG-BUFFER-LIMIT	UNLIM \| `n`	O	z	u	w
LONG-BUFFER-LIMIT	Allocates a number of long message buffers for the service. UNLIM The number of long message buffers is restricted only by the number of buffers globally available. Precludes the use of NUM-LONG-BUFFER=AUTO in the Broker section of the attribute file. n Number of long message buffers. A value of 0 (zero) is invalid. If NUM-LONG-BUFFER=AUTO is specified in the Broker section of the attribute file, LONG-BUFFER-LIMIT=UNLIM is not allowed in the service section. A value must be specified or the LONG-BUFFER-LIMIT attribute must be suppressed entirely for the service so that the default (LONG-BUFFER-DEFAULT) becomes active.
MAX-MESSAGES-IN-UOW	16 \| `n`	O	z	u	w
MAX-MESSAGES-IN-UOW	Maximum number of messages in a UOW.
MAX-MESSAGE-LENGTH	2147483647 \| `n`	O	z	u	w
MAX-MESSAGE-LENGTH	Maximum message size that can be sent to a service. This is transport-dependent. The default value represents the highest positive number that can be stored in a four-byte integer.
MAX-MSG	See MAX‑MESSAGE‑LENGTH.
MAX-UOW-MESSAGE-LENGTH	See MAX‑MESSAGE‑LENGTH.
MAX-UOWS	0 \| `n`	O	z	u	w
MAX-UOWS	0 The service does not accept units of work, that is, it processes only messages that are not part of a UOW. Using zero prevents the sending of UOWs to services that are not intended to process them. n Maximum number of UOWs that can be active concurrently for the service. If you do not provide a MAX-UOWS value for the service, it defaults to the MAX-UOWS setting for the broker. If you provide a value that exceeds that of the broker, the service MAX-UOWS is set to the broker's MAX-UOWS value and a warning message is issued. Specify MAX-UOWS=0 for Natural RPC Servers. This restriction will be removed with a later release.
MUOW	See MAX‑UOWS.
NOTIFY-EOC	NO \| YES	O	z	u	w
NOTIFY-EOC	Specifies whether timed-out conversations are to be stored or discarded. NO Discard the EOC notifications if the server is not ready to receive. YES Store the EOC notifications if the server is not ready to receive and then notify the server if possible. If a server is not ready to receive an EOC notification, it can be stored or discarded. If it is stored, the server is notified, if possible, when it is ready to receive. CAUTION: The behavior activated by this parameter can be relied upon only during a single lifetime of the broker kernel. Specifically, conversations containing units of work, whose lifetime can span multiple broker kernel sessions, cannot be assumed to show this behavior, even with NOTIFY-EOC=YES.
NUM-UOW	Alias for MAX‑UOWS.
POSTPONE-ATTEMPTS	0 \| `n`	O	z	u	w
POSTPONE-ATTEMPTS	Defines the number of attempts putting a received unit of work (UOW) due to SYNCPOINT option CANCEL on the postponed queue for later processing. 0 All UOWs rejected by the receiver (SYNCPOINT option CANCEL) will be cancelled immediately. Attribute POSTPONE‑DELAY is ignored. n Defines the number of postpone attempts that are performed instead of considering the UOW finished due to SYNCPOINT option CANCEL; the UOW will be moved to the postponed queue and the UOW status will be changed to POSTPONED. These UOWs will be delivered to the receiver when the time specified with POSTPONE‑DELAY has elapsed. Note: Broker-specific attribute POSTPONED‑QUEUE must be enabled (default) for this attribute to take effect. The default value is 0. For more information, see Postponing units of work.
POSTPONE-DELAY	0 \| `n` \| `n`S \| `n`M \| `n`H	O	z	u	w
POSTPONE-DELAY	The length of time a UOW is kept in status POSTPONED. 0 No postponed queue is created and attribute POSTPONE‑ATTEMPTS is ignored. nS Number of seconds the UOW stays unreadable in the postponed queue with status POSTPONED (max. 2147483647). nM Number of minutes the UOW stays unreadable in the postponed queue with status POSTPONED (max. 35791394). nH Number of hours the UOW stays unreadable in the postponed queue with status POSTPONED (max. 596523). nD Number of days the UOW stays unreadable in the postponed queue with status POSTPONED (max. 24855). The status of the UOW will be changed from POSTPONED to ACCEPTED after elapsed POSTPONE-DELAY. This delay time does not affect the UOW‑DATA‑LIFETIME. The POSTPONE-DELAY must be less than UOW-STATUS-LIFETIME in order to make the UOW receivable again. Note: Broker-specific attribute POSTPONED‑QUEUE must be enabled (default) for this attribute to take effect. The default is 0, that is, no postponed queue is created, but if a value is entered, the minimum delay is 30 seconds. Any value entered that is less than 30 seconds will be increased to this value. For more information, see Postponing units of work.
SERVER	A32 (case-sensitive)	R	z	u	w
SERVER	Part of the name that identifies the service together with the CLASS and SERVICE attributes. CLASS must be specified first, followed immediately by SERVER and SERVICE. Valid characters for server name are letters a-z, A-Z, numbers 0-9, hyphen and underscore. Do not use dollar, percent, period or comma.
SERVER-DEFAULT	`n` \| UNLIM	O	z	u	w
SERVER-DEFAULT	Default number of servers that are allowed for every service. n Number of servers. UNLIM The number of servers is restricted only by the number of servers globally available. Precludes the use of NUM-SERVER=AUTO. A value of 0 (zero) is invalid. This value can be overridden by specifying a SERVER-LIMIT for the service.
SERVER-LIMIT	`n` \| UNLIM	O	z	u	w
SERVER-LIMIT	Allows a number of servers especially for this service. n Number of servers. UNLIM The number of servers is restricted only by the number of servers globally available. Precludes the use of NUM-SERVER=AUTO in the Broker section of the attribute file. A value of 0 (zero) is invalid. If NUM-SERVER=AUTO is specified in the Broker section of the attribute file, SERVER-LIMIT=UNLIM is not allowed in the service section. A value must be specified or the SERVER-LIMIT attribute must be suppressed entirely for the service so that the default (SERVER-DEFAULT) becomes active. Note: Linux and Windows: This limit also includes any attach server you are using. Make sure you increase the number by one for each attach server you use.
SERVER-NONACT	5M \| `n` \| `n`S \| `n`M \| `n`H	R	z	u	w
SERVER-NONACT	Non-activity time for servers. A server that does not issue a broker request within the specified time limit is treated as inactive and all resources for the server are freed. n Same as nS. nS Non-activity time in seconds (max. 2147483647). nM Non-activity time in minutes (max. 35791394). nH Non-activity time in hours (max. 596523). If a server registers multiple services, the highest value of all the services registered is taken as non-activity time for the server.
SERVICE	A32 (case-sensitive)	R	z	u	w
SERVICE	Part of the name that identifies the service together with the CLASS and SERVER attributes. CLASS must be specified first, followed immediately by SERVER and SERVICE. The SERVICE attribute names EXTRACTOR and DEPLOYMENT are reserved for IBM EntireX internal use and should not be used in customer-written applications. Valid characters for service name are letters a-z, A-Z, numbers 0-9, hyphen and underscore. Do not use dollar, percent, period or comma. See also the restriction for CLASS attribute names.
SHORT-BUFFER-LIMIT	UNLIM \| `n`	O	z	u	w
SHORT-BUFFER-LIMIT	Allocates a number of short message buffers for the service. UNLIM The number of short message buffers is restricted only by the number of buffers globally available. Precludes the use of NUM-SHORT-BUFFER=AUTO in the Broker section of the attribute file. n Number of short message buffers. If NUM-SHORT-BUFFER=AUTO is specified in the Broker section of the attribute file, SHORT-BUFFER-LIMIT=UNLIM is not allowed in the service section. A value must be specified or the SHORT-BUFFER-LIMIT attribute must be suppressed entirely for the service so that the default (SHORT-BUFFER-DEFAULT) becomes active.
STORE	OFF \| BROKER	O	z	u	w
STORE	Sets the default STORE attribute for all units of work sent to the service. OFF Units of work are not persistent. BROKER Units of work are persistent. This attribute can be overridden by the STORE field in the Broker ACI control block.
TRANSLATION	NO \| `name` (A255)	O	z	u	w
TRANSLATION	Activates translation user exit for character conversion. NO If translation is not to be used - for example for binary payload (broker messages) - either omit the TRANSLATION attribute or specify TRANSLATION=NO. name Name of Translation User Exit. For more information, see Configuring translation user exits under z/OS \| Linux \| Windows or Writing translation user exits under z/OS \| Linux \| Windows. The CONVERSION attribute overrides the TRANSLATION attribute when defined for a service; that is, when TRANSLATION and CONVERSION are both defined, TRANSLATION will be ignored.
UMSG	Alias for MAX‑MESSAGES‑IN‑UOW.
UOW-DATA-LIFETIME	1D \| `n`S \| `n`M \| `n`H \| `n`D	O	z	u	w
UOW-DATA-LIFETIME	Defines the default lifetime for units of work for the service. nS Number of seconds the UOW can exist (max. 2147483647). nM Number of minutes the UOW can exist (max. 35791394). nH Number of hours the UOW can exist (max. 596523). nD Number of days the UOW can exist (max. 24855). This attribute is ignored if PSTORE=NO is defined. If the unit of work (UOW) is inactive, that is, not processed within the time limit, it is deleted and given a status of TIMEOUT. This attribute can be overridden by the UWTIME field in the Broker ACI control block.
UOW-MSGS	Alias for MAX‑MESSAGES‑IN‑UOW.
UOW-STATUS-LIFETIME	no value \| `n`[S] \| `n`M \| `n`H \| `n`D	O	z	u	w
UOW-STATUS-LIFETIME	The value to be added to the UOW‑DATA‑LIFETIME lifetime of associated UOW). If a value is entered, it must be 1 or greater; a value of 0 will result in an error. If no value is entered, the lifetime of the UOW status information will be the same as the lifetime of the UOW itself. nS Number of seconds the UOW status exists longer than the UOW itself (max. 2147483647). nM Number of minutes (max. 35791394). nH Number of hours (max. 596523). nD Number of days (max. 24855). The lifetime determines how much additional time the UOW status is retained in the persistent store and is calculated from the time at which the associated UOW enters any of the following statuses: PROCESSED, TIMEOUT, BACKEDOUT, CANCELLED, DISCARDED. The additional lifetime of the UOW status is calculated only when broker is executing. Value in UOW-STATUS-LIFETIME supersedes the value (if specified) in attribute UWSTATP. Note: If no unit is specified, the default unit is seconds. The unit does not have to be identical to the unit specified for UOW-DATA-LIFETIME.
UWSTATP	0 \| `n`	O	z	u	w
UWSTATP	Contains a multiplier used to compute the lifetime of a persistent status for the service. The UWSTATP value is multiplied by the UOW‑STATUS‑LIFETIME value (the lifetime of the associated UOW) to determine the length of time the status will be retained in the persistent store. 0 The status is not persistent. 1 - 254 Multiplied by the value of UOW‑DATA‑LIFETIME to determine how long a persistent status will be retained. This attribute is ignored if PSTORE=NO is defined. Note: This attribute has not been supported since EntireX version 7.3. Use UOW‑STATUS‑LIFETIME
UWSTAT-LIFETIME	Alias for UOW‑STATUS‑LIFETIME.
UWTIME	Alias for UOW‑DATA‑LIFETIME.

Wildcard service definitions

The special names of CLASS = *, SERVER = * and SERVICE = * are allowed in the service-specific and authorization rule-specific sections of the broker attribute file. These are known as wildcard service definitions. If this name is present in the attribute file, any service that registers with the broker and does not have its own entry in the attribute file will inherit the attributes that apply to the first wildcard service definition found.

For example, a server that registers with CLASS=ACLASS, SERVER=ASERVER and SERVICE=ASERVICE can inherit attributes from any of the following entries in the attribute file (this list is not necessarily complete):

CLASS = *, SERVER = ASERVER, SERVICE = ASERVICE
CLASS = ACLASS, SERVER = *, SERVICE = *
CLASS = *, SERVER = *, SERVICE = *

Of course, if there is a set of attributes that are specifically defined for CLASS=ACLASS, SERVER=ASERVER, SERVICE=ASERVICE, then all of the wildcard service definitions will be ignored in favor of the exact matching definition.

Service update modes

EntireX has two modes for handling service-specific attributes. See broker-specific attribute SERVICE‑UPDATES.

In service update mode (SERVICE-UPDATES=YES), the service configuration sections of the attribute file are read whenever the first replica of a particular service registers.
In non-update mode (SERVICE-UPDATES=NO), the attribute file is not reread. All attributes are read during startup and the broker does not honor any changes in the attribute file. This mode is useful if
- there is a high frequency of REGISTER operations, or
- the attribute file is rather large and results in a high I/O rate for the broker.
The disadvantage to using non-update mode is that if specific attributes are modified, the broker must be restarted to effect the changes. Generally, this mode should be used only if the I/O rate of the broker is considerably high, and if the environment seldom changes.

OPTION values for conversion

The different option values allow you to either handle character conversion deficiencies as errors, or to ignore them:

Do not ignore any character conversion errors and force an error always (value STOP). This is the default behavior.
Ignore if characters cannot be converted into the receiver's codepage, but force an error if sender characters do not match the sender's codepage (value SUBSTITUTE-NONCONV).
Ignore any character conversion errors (values SUBSTITUTE and BLANKOUT).

Situations 1 and 2 are reported to the broker log file if the TRACE option for CONVERSION is set to level 1.

Table 4. Option values for conversion
Value	Description	Options Supported for		Report Situation in Broker Log File if TRACE Option for CONVERSION is set to 1
Value	Description	SAGTCHA	SAGTRPC	Bad Input Characters (Sender's Codepage)	Non-convertible Characters (Receiver's Codepage)
SUBSTITUTE	Substitutes both non-convertible characters (receiver's codepage) and bad input characters (sender's codepage) with a codepage-dependent default replacement character.	YES	YES	No message.	No message
SUBSTITUTE-NONCONV	If a corresponding code point is not available in the receiver's codepage, the character cannot be converted and is substituted with a codepage-dependent default replacement character. Bad input characters in sender's codepage are not substituted and result in an error.	YES	YES	Write detailed conversion error message.	No message.
BLANKOUT	Substitutes non-convertible characters with a codepage-dependent default replacement; blanks out the complete RPC IDL field containing one or more bad input characters.	NO	YES	No message.	No message.
STOP	Signals an error on detecting a non-convertible or bad input character. This is the default behavior if no option is specified.	YES	YES	Write detailed conversion error message.	Write detailed conversion error message.

Codepage-specific attributes

The codepage-specific attribute section begins with the keyword DEFAULTS=CODEPAGE as shown in the sample attribute file. You can use the attributes in this section to customize the broker's locale string defaults and customize the mapping of locale strings to codepages for character conversion with ICU conversion and SAGTRPC user exit. For more information, see Internationalization.

Table 5. Codepage-specific attributes
Attribute	Values	Opt/Req	Operating System
Attribute	Values	Opt/Req	z/OS	Linux	Windows
DEFAULT_ASCII	Any ICU converter name or alias. See also Additional notes.	O	z	u	w
DEFAULT_ASCII	Customize the broker's locale string defaults by assigning the default codepage for EntireX components (client or server). See Broker's locale string defaults. This value is used instead of the broker's locale string defaults if the calling component does not send a locale string itself, and the calling component is running on an ASCII platform (Linux, Windows, etc.) Example: `DEFAULTS=CODEPAGE * Broker Locale String Defaults DEFAULT_ASCII=windows-950` For more examples, see Configuring Broker's locale string defaults in the Internationalization documentation and also Additional notes.
DEFAULT_EBCDIC_IBM	Any ICU converter name or alias	O	z	u	w
DEFAULT_EBCDIC_IBM	Customize the broker's locale string defaults by assigning the default codepage for EntireX components (client or server). See Broker's locale string defaults. This value is used instead of the broker's locale string defaults if the calling component does not send a locale string itself and the calling component is running on an IBM mainframe platform Example: `DEFAULT=CODEPAGE DEFAULT_EBCDIC_IBM=ibm-937` For more examples, see Configuring Broker's locale string defaults in the Internationalization documentation and also Additional notes.
DEFAULT_EBCDIC_SNI	Any ICU converter name or alias.	O	z	u	w
DEFAULT_EBCDIC_SNI	Customize the broker's locale string defaults by assigning the default codepage for EntireX components (client or server). See Broker's locale string defaults. This value is used instead of the locale string defaults if the calling component does not send a locale string itself. For more examples, see Configuring Broker's locale string defaults in the Internationalization documentation and also Additional notes.
locale-string	Any ICU converter name or alias. See also Additional Notes .	O	z	u	w
locale-string	Customize the mapping of locale strings to codepages and bypass the broker's locale string processing mechanism. See Broker's locale string processing. This is useful: if the broker's locale string processing fails - that is, it leads to no codepage or to the wrong codepage - you can explicitly assign the codepage which meets your requirements. if you want to install user-written ICU converters (codepages) into the broker, see Building and Installing ICU Custom Converters z/OS \| Linux \| Windows. The attribute (locale string) is the locale string sent by your EntireX component (client or server) and the value is the codepage that you want to use in place of that locale string. In the first line of the following example, the client or server application sends ASCII as a locale string; the broker maps this to the codepage ISO 8859_1. In the same way EUC_JP_LINUX is mapped to ibm-33722_P12A-1999. All other locale strings are mapped by the broker's mapping mechanism, see Broker's built-in locale string mapping. Example: `DEFAULTS=CODEPAGE * Broker Locale String Codepage Assignments ASCII=ISO8859 EUC_JP_LINUX=ibm-33722_P12A-1999 * Customer-written ICU converters CP1140=myebcdic CP0819=myascii` For more examples, see Bypassing broker's built-in locale string mapping and also Additional notes.

Additional Notes

Locale string matching is case insensitive when bypassing the broker's built-in mechanism, that is, when the broker examines the codepages section in the attribute file.
If ICU is used for character conversion and the style in not known by ICU, e.g. <ll>_<cc> etc., the name will be mapped to a suitable ICU alias. For more details on the mapping mechanism, see Broker's built-in locale string mapping. For more details on ICU and ICU converter name standards, see ICU Resources.
If SAGTRPC user exit is used for the character conversion, we recommend assigning the codepage in the form CP<nnnnn>. To determine the number given to SAGTRPC user exit, see Broker's built-in locale string mapping.
See CONVERSION on this page for the character conversion in use.

Adabas SVC/entire net-work-specific attributes

The Adabas SVC/Entire Net-Work-specific attribute section begins with the keyword DEFAULTS=NET as shown in the sample attribute file. The attributes in this section are needed to execute the Adabas SVC/Entire Net-Work communicator of the EntireX Broker kernel.

Note: This section applies to mainframe platforms only. It does not apply to Linux and Windows.

Table 6. Adabas SVC/entire net-work-specific attributes
Attribute	Values	Opt/Req	Operating System
Attribute	Values	Opt/Req	z/OS	Linux	Windows
MAX-MESSAGE-LENGTH	2147483647 \| `n`	O	z	u	w
MAX-MESSAGE-LENGTH	Maximum message size that the broker kernel can process using transport method NET. The default value represents the highest positive number that can be stored in a four-byte integer.

Security-specific attributes

The security-specific attribute section begins with the keyword DEFAULTS=SECURITY as shown in the sample attribute file. This section applies only if broker-specific attribute SECURITY=YES is specified.

Table 7. Security-specific attributes
Attribute	Values	Opt/Req	Operating System
Attribute	Values	Opt/Req	z/OS	Linux	Windows
AUTHORIZATION-DEFAULT	YES \| NO	O		u	w
AUTHORIZATION-DEFAULT	Determines whether access is granted to a specified service if the specified service could not be found listed in the repository of authorization rules or in section DEFAULTS=AUTHORIZATION-RULES of the attribute file. YES Grant access. NO Deny access. Applies only when using EntireX Security under Linux and Windows. Authorization rules can be stored within a repository. When an authorization call occurs, EntireX Security uses the values of this parameter to perform an access check for a particular broker instance against an (authenticated) user ID and list of rules. See also Authorization rules.
IGNORE-STOKEN	NO \| YES	O	z	u	w
IGNORE-STOKEN	Determines whether the value of the ACI field SECURITY-TOKEN is verified on each call.
LDAP-AUTHENTICATION-URL	`ldapUrl`	O		u	w
LDAP-AUTHENTICATION-URL	Authentication is performed against the LDAP repository specified under `ldapUrl`. TCP Specify repository URL: `LDAP-AUTHENTICATION-URL="ldap://HostName[:PortNumber]"` SSL/TLS Specify repository URL with ldaps: `LDAP-AUTHENTICATION-URL="ldaps://HostName[:PortNumber]"` If no port number is specified, the default is the standard LDAP port number 389 for TCP transport. Examples for TCP and SSL/TLS: `LDAP-AUTHENTICATION-URL="ldap://myhost.mydomain.com" LDAP-AUTHENTICATION-URL="ldaps://myhost.mydomain.com:636"`
LDAP-AUTHORIZATION-URL	`ldapUrl`	O		u	w
LDAP-AUTHORIZATION-URL	Authorization is performed against the LDAP repository specified under `ldapUrl`. TCP Specify repository URL: `LDAP-AUTHORIZATION-URL="ldap://HostName[:PortNumber]"` If no port number is specified, the default is the standard LDAP port number 389 for TCP transport. Example for TCP: `LDAP-AUTHORIZATION-URL="ldap://myhost.mydomain.com:389"` This attribute replaces the parameters host, port and protocol in the xds.ini file of EntireX version 9.10 and earlier.
LDAP-AUTH-DN	`authDN`	O		u	w
LDAP-AUTH-DN	For authenticated access to the LDAP server. Specifies the DN of the user. Default value: `cn=admin,dc=software-ag,dc=de` This attribute replaces parameter authDN in the xds.ini file of EntireX version 9.10 and earlier.
LDAP-AUTH-PASSWD-ENCRYPTED	`authPass`	O		u	w
LDAP-AUTH-PASSWD-ENCRYPTED	For authenticated access to the LDAP server. Specifies the encrypted value of the user password. Use program `etbnattr` to get the encrypted password: `etbnattr –x clear_text_password –echo_password_only` This writes the encrypted password to standard output. This attribute replaces parameter authPass in the xds.ini file of EntireX version 9.10 and earlier.
LDAP-AUTHORIZATION-RULE	A32	O		u	w
LDAP-AUTHORIZATION-RULE	List of authorization rules. Multiple sets of rules can be defined, each set is limited to 32 chars. The maximum number of LDAP-AUTHORIZATION-RULE entries in the attribute file is 16. Applies only when using EntireX Security under Linux or Windows and SECURITY-SYSTEM=`ldapUrl` . Authorization rules can be stored in an LDAP repository. When an authorization call occurs, EntireX Security uses the values of this parameter and AUTHORIZATION‑DEFAULT to perform an access check for a particular broker instance against an (authenticated) user ID and list of rules. For more information, see Authorization rules.
LDAP-BASE-DN	`baseDN`	O		u	w
LDAP-BASE-DN	Specifies the base distinguished name of the directory object that is the root of all objects for authorization rules. Default value: `dc=software-ag,dc=de` This attribute replaces parameter baseDN in the xds.ini file of EntireX version 9.10 and earlier.
LDAP-PERSON-BASE-BINDDN	`ldapDn`	O		u	w
LDAP-PERSON-BASE-BINDDN	Used with LDAP authentication to specify the distinguished name where authentication information is stored. This value is prefixed with the user ID field name. Example: `LDAP-PERSON-BASE-BINDDN="cn=users,dc=mydomain,dc=com"`
LDAP-REPOSITORY-TYPE	OpenLDAP \| ActiveDirectory \| SunOneDirectory \| Tivoli® \| Novell \| ApacheDS	O		u	w
LDAP-REPOSITORY-TYPE	Use predefined known fields for the respective repository type. Specify the repository type that most closely matches your actual repository. In the case of Windows Active Directory, the user ID is typically in the form `domainName`\`userId`.
LDAP-SASL-AUTHENTICATION	NO \| YES	O			w
LDAP-SASL-AUTHENTICATION	Specifies whether or not Simple Authentication and Security Layer (SASL) is to perform the authentication check. In practice, this determines whether or not the password supplied by the user is passed in plain text between the broker kernel and the LDAP server. If SASL is activated, this implies that the password is encrypted. NO Password is sent to LDAP server in plain text. YES Password is sent to LDAP server encrypted.
LDAP-USERID-FIELD	cn \| `uidFieldName`	O		u	w
LDAP-USERID-FIELD	Used with LDAP authentication to specify the first field name of a user in the Distinguished Name, for example: LDAP-USERID-FIELD=`uid`
SECURITY-LEVEL	AUTHORIZATION \| AUTHENTICATION	O	z	u	w
SECURITY-LEVEL	Specifies the mode of operation. AUTHORIZATION Authorization and authentication. AUTHENTICATION Authentication. Note: In version 8.0, the default value for this parameter was AUTHORIZATION.
SECURITY-SYSTEM	OS \| LDAP	O	z	u	w
SECURITY-SYSTEM	Authentication and authorization are performed against the LDAP repository specified under LDAP‑AUTHENTICATION‑URL and LDAP‑AUTHORIZATION‑URL.
TRACE-LEVEL	0-4	O	z	u	w
TRACE-LEVEL	Trace level for EntireX Security. It overrides the global value of trace level in the attribute file. 0 No tracing. Default value. 1 Log security violations and access denied/permitted. 2 All of trace level 1, plus internal errors. 3 All of trace level 2, plus function entered/exit messages with argument values and some progress messages. 4 All of trace level 3, plus some selected data areas for problem analysis. Trace levels 2, 3 and 4 should be used only when requested by IBM Support. If you modify the TRACE-LEVEL attribute, you must restart the broker for the change to take effect. For temporary changes to TRACE-LEVEL without a broker restart, use the EntireX Broker command-line utility ETBCMD. Note: Setting this value also affects tracing for authorization rules.

TCP/IP-specific attributes

The TCP/IP-specific attribute section begins with the keyword DEFAULTS=TCP as shown in the sample attribute file. It contains attributes that apply to the TCP/IP transport communicator. The transport is activated by TRANSPORT=TCP in the Broker-specific section of the attribute file. A maximum of five TCP/IP communicators can be activated by specifying up to five HOST/PORT pairs.

Table 8. TCP/IP-specific attributes
Attribute	Values	Opt/Req	Operating System
Attribute	Values	Opt/Req	z/OS	Linux	Windows
CONNECTION-NONACT	`n` \| `n`S \| `n`M \| `n`H	O	z	u	w
CONNECTION-NONACT	Non-activity of the TCP/IP connection, after which a close is performed and the connection resources are freed. If this parameter is not specified here, broker will close the connection only when the application (or the network itself) terminates the connection. n Same as nS. nS Non-activity time in seconds (min. 600, max. 2147483647). nM Non-activity time in minutes (min. 10, max. 35791394). nH Non-activity time in hours (max. 596523). If not specified, the connection non-activity is not monitored by the broker. On the stub side, non-activity can be set with the environment variable ETB_NONACT. For more information, see Limiting the TCP/IP connection lifetime under z/OS \| Linux \| Windows \| z/VSE®. Both sides (the stub side and the broker kernel side) act independently of each other.
HOST	0.0.0.0 \| `hostname` \| `IP address`	O	z	u	w
HOST	The address of the network interface on which broker will listen for connection requests. If HOST is not specified, broker will listen on any attached interface adapter of the system (or stack). A maximum of five HOST/PORT pairs can be specified to start multiple instances of broker's TCP/IP transport communicator.
MAX-MESSAGE-LENGTH	2147483647 \| `n`	O	z	u	w
MAX-MESSAGE-LENGTH	Maximum message size that the broker kernel can process using transport method TCP/IP. The default value represents the highest positive number that can be stored in a four-byte integer.
PORT	1025-65535	O	z	u	w
PORT	The TCP/IP port number on which the broker will listen for connection requests. If not specified, the broker will attempt to find its TCP/IP port number from the TCP/IP services file, using `getservbyname`. If it cannot find the number here, the default value of 1971 is used. A maximum of five HOST/PORT pairs can be specified to start multiple instances of broker's TCP/IP transport communicator. Example for multiple ports on z/OS: `HOST=localhost,PORT=3930 HOST=0.0.0.0,PORT=3931` Port 3930 is used for local TCP/IP communication only and is not visible outside the z/OS host. Port 3931 is used for global TCP/IP communication. With IBM's AT-TLS this port is turned into a TLS port, see Running Broker with SSL/TLS transport in the z/OS Administration documentation. With this configuration you can reach the broker from outside the z/OS host via the secure TLS connection only (port 3931). The TCP connection (port 3930) can only be used from inside the z/OS host.
RESTART	YES \| NO	O	z	u	w
RESTART	YES The broker kernel will attempt to restart the TCP/IP communicator. NO The broker kernel will not try to restart the TCP/IP communicator. This setting applies to all TCP/IP communicators.
RETRY-LIMIT	20 \| `n` \| UNLIM	O	z	u	w
RETRY-LIMIT	Maximum number of attempts to restart the TCP/IP communicator. This setting applies to all TCP/IP communicators.
RETRY-TIME	3M \| `n` \| `n`S \| `n`M \| `n`H	O	z	u	w
RETRY-TIME	Wait time between stopping the TCP/IP communicator due to an unrecoverable error and the next attempt to restart it. n Same as nS. nS Wait time in seconds (max. 2147483647). nM Wait time in minutes (max. 35791394). nH Wait time in hours (max. 596523). Minimum wait time is 1S. This setting applies to all TCP/IP communicators.
REUSE-ADDRESS	YES \| NO	O	z	u
	YES \| NO	O			w
	YES The TCP port assigned to the broker can be taken over and assigned to other applications (this is the default value on all non-Windows platforms). NO The TCP port assigned to the broker cannot be taken over and assigned to other applications. This is the default setting on Windows, and we strongly advise you do not change this value on this platform. Note: This setting might be required at your site when restarting broker immediately after stopping it. This is due to the inherent latency of the TCP/IP stack when closing connections.
TRACE-LEVEL	0-4	O	z	u	w
TRACE-LEVEL	The level of tracing to be performed while the broker is running with transport method TCP/IP. It overrides the global value of trace level for all TCP/IP routines. 0 No tracing. Default value. 1 Display IP address of incoming request, display error number of outgoing error responses. 2 All of trace level 1, plus errors if request entries could not be allocated. 3 All of trace level 2, plus all routines executed. 4 All of trace level 3, plus function arguments and return values. Trace levels 2, 3 and 4 should be used only when requested by IBM Support. If you modify the TRACE-LEVEL attribute, you must restart the broker for the change to take effect. For temporary changes to TRACE-LEVEL without a broker restart, use the EntireX Broker command-line utility ETBCMD.

FILESYSTEM-specific attributes

The FILESYSTEM-specific attribute section begins with the keyword DEFAULTS = FILESYSTEM. The attributes in this section are optional. This section applies only if PSTORE-TYPE = FILESYSTEM is specified.

Table 9. FILESYSTEM-specific attributes
Attribute	Values	Opt/Req	Operating System
Attribute	Values	Opt/Req	z/OS	Linux	Windows
PATH	A255	O		u	w
PATH	Path name of the target directory for persistent files.
TRACE-LEVEL	0-4	O		u	w
TRACE-LEVEL	Trace level for FILESYSTEM persistent store. It overrides the global value of trace level in the attribute file. 0 No tracing. Default value. 1 Log memory allocation failures and errors during close of files. 2 N/A 3 All of trace level 1, plus `UOWID` in use for the various requests and function entered/exit messages. 4 All of trace level 3, plus returned function values. If you modify the `TRACE-LEVEL` attribute, you must restart the broker for the change to take effect. For temporary changes to `TRACE-LEVEL` without a broker restart, use the EntireX Broker command-line utility `ETBCMD`.

SSL/TLS-specific attributes

The Broker can use Secure Sockets Layer/Transport Layer Security (SSL/TLS) as the transport medium. The term SSL here refers to both SSL and TLS. RPC-based clients and servers, as well as ACI clients and servers, are always SSL clients. The broker is always the SSL server. For an introduction, see SSL/TLS, HTTP(S), and certificates with EntireX. Your operating system determines whether this section of the attribute file is required:

z/OS: The SSL-specific attribute section is not used. You can use IBM's Application Transparent Transport Layer Security (AT-TLS). For more information, see Running Broker with SSL/TLS Transport in the z/OS Administration documentation.
Linux and Windows: The SSL-specific attribute section is required, and begins with the keyword DEFAULTS=SSL as shown in the sample attribute file. The attributes in this section are needed to execute the SSL communicator of the EntireX Broker kernel. For more information, see Running Broker with SSL/TLS Transport under Linux | Windows.

Table 10. SSL/TLS-specific attributes
Attribute	Values	Opt/Req	Operating System
Attribute	Values	Opt/Req	z/OS	Linux	Windows
CIPHER-SUITE	`string`	O		u	w
CIPHER-SUITE	String that is passed to the underlying SSL/TLS implementation. SSL/TLS is a standardized protocol that uses different cryptographic functions (hash functions, symmetric and asymmetric encryption etc.). Some of these must be implemented in the SSL/TLS stack; others are optional. When an SSL/TLS connection is created, both parties agree by `handshake` on the cipher suite, that is, the algorithms and key lengths used. In a default scenario, this information depends on what both sides are capable of. It can be influenced by setting the attribute CIPHER-SUITE for the SSL/TLS server side (the broker always implements the server side). Thus stubs connect to the broker and thereby become the SSL/TLS clients. Under Linux and Windows, the OpenSSL implementation is used. The SSL protocol is obsolete. It is no longer available. The TLS protocol is the successor of SSL and is readily available in OpenSSL. The default OpenSSL configuration uses FIPS 140-2 approved cipher suites, eligible for TLS v1.2, but without anonymous Diffie-Hellman (ADH) and pre-shared key (PSK) algorithms. The resulting set of cipher suites provides for authentication and strong encryption: `CIPHER-SUITE=FIPS+TLSv1.2:!ADH:!PSK:@STRENGTH` For more information, see https://www.openssl.org/docs/man1.1.1/man1/ciphers.
CONNECTION-NONACT	`n` \| `n`S \| `n`M \| `n`H	O		u	w
CONNECTION-NONACT	Non-activity of the SSL connection, after which a close is performed and the connection resources are freed. If this parameter is not specified here, broker will close the connection only when the application (or the network itself) terminates the connection. n Same as nS. nS Non-activity time in seconds (min. 600, max. 2147483647). nM Non-activity time in minutes (min. 10, max. 35791394). nH Non-activity time in hours (max. 596523). If not specified, the connection non-activity is not monitored by the broker. On the stub side, non-activity can be set with the environment variable `ETB_NONACT`. For more information, see Limiting the TCP/IP connection lifetime under z/OS \| Linux \| Windows \| z/VSE. Both sides (the stub side and the broker kernel side) act independently of each other.
HOST	0.0.0.0 \| `hostname` \| `IP address`	O		u	w
HOST	The address of the network interface on which broker will listen for connection requests. If HOST is not specified, broker will listen on any attached interface adapter of the system (or stack). A maximum of five HOST/PORT pairs can be specified to start multiple instances of EntireX Broker's TCP/IP transport communicator.
KEY-FILE	`filename`	R		u	w
KEY-FILE	File that contains the broker's private key (if not contained in KEY-STORE). For test purposes, EntireX delivers certificates for use on various platforms. For more information, see SSL/TLS, HTTP(S), and certificates with EntireX. Example for Linux and Windows: MyAppKey.pem. Note: EntireX Broker does not support certificates of type .jks or .p12.
KEY-PASSWD	`password` (A32)	R		u	w
KEY-PASSWD	Password used to protect the private key. Unlocks the KEY-FILE, for example MyAppKey.pem. Deprecated. See KEY-PASSWD-ENCRYTPED below.
KEY-PASSWD-ENCRYPTED	`encrypted value` (A64)	R		u	w
KEY-PASSWD-ENCRYPTED	Password used to protect the private key. Unlocks the KEY-FILE, for example MyAppKey.pem. This attribute replaces KEY-PASSWD to avoid a clear-text password as attribute value. If KEY-PASSWD and KEY-PASSWD-ENCRYTPED are both supplied, KEY-PASSWD-ENCRYTPED takes precedence. Use program etbnattr to get the encrypted password: `etbnattr -w ssl_key_password --echo_password_only` This writes the encrypted password to standard output.
KEY-STORE	`filename`	R		u	w
KEY-STORE	SSL certificate; may contain the private key. For test purposes, EntireX delivers certificates for use on various platforms. For more information, see SSL/TLS, HTTP(S), and certificates with EntireX. Example for Linux and Windows: ExxAppCert.pem. Note: EntireX Broker does not support certificates of type .jks or .p12.
MAX-MESSAGE-LENGTH	2147483647 \| `n`	O		u	w
MAX-MESSAGE-LENGTH	Maximum message size that the broker kernel can process using transport method SSL. The default value represents the highest positive number that can be stored in a four-byte integer.
PORT	1025-65535	O		u	w
PORT	The SSL port number on which the broker will listen for connection requests. If not changed, this parameter takes the standard value as specified in the sample attribute file. If the port number is not specified, the broker will use the default value of 1958. A maximum of five HOST/PORT pairs can be specified to start multiple instances of broker's TCP/IP transport communicator.
RESTART	YES \| NO	O		u	w
RESTART	YES The broker kernel will attempt to restart the SSL communicator (this is the default value). NO The broker kernel will not attempt to restart the SSL communicator.
RETRY-LIMIT	20 \| `n` \| UNLIM	O		u	w
RETRY-LIMIT	Maximum number of attempts to restart the SSL communicator.
RETRY-TIME	3M \| `n` \| `n`S \| `n`M \| `n`H	O		u	w
RETRY-TIME	Wait time between suspending SSL communication due to unrecoverable error and the next attempt to restart it. n Same as nS. nS Wait time in seconds (max.2147483647). nM Wait time in minutes (max. 35791394). nH Wait time in hours (max. 596523). Minimum: 1S
REUSE-ADDRESS	YES \| NO	O		u	w
REUSE-ADDRESS	YES The SSL port assigned to the broker can be taken over and assigned to other applications (this is the default value). NO The SSL port assigned to the broker cannot be taken over and assigned to other applications. Note: This setting might be required at your site when restarting broker immediately after stopping it. This is due to the inherent latency of the TCP/IP stack when closing connections.
STACK-NAME	`name`	O		u	w
STACK-NAME	Name of the TCP/IP stack that the broker is using. If not specified, broker will connect to the default TCP/IP stack running on the machine.
TRACE-LEVEL	0-4	O		u	w
TRACE-LEVEL	The level of tracing to be performed while the broker is running with transport method SSL/TLS. It overrides the global value of trace level for all SSL/TLS routines. 0 No tracing. Default value. 1 Display IP address of incoming request, display error number of outgoing error responses. 2 All of trace level 1, plus errors if request entries could not be allocated. 3 All of trace level 2, plus all routines executed. 4 All of trace level 3, plus function arguments and return values. Trace levels 2, 3 and 4 should be used only when requested by IBM Support. If you modify the TRACE-LEVEL attribute, you must restart the broker for the change to take effect. For temporary changes to TRACE-LEVEL without a broker restart, use the EntireX Broker command-line utility ETBCMD.
TRUST-STORE	`filename \| keyring`	R		u	w
TRUST-STORE	Location of the store containing certificates of trust Certificate Authorities (or CAs). Specify the file name of the CA certificate store. Examples: EXXCACERT.PEM, C:\Certs\ExxCACert.pem
VERIFY-CLIENT	NO \| YES	O		u	w
VERIFY-CLIENT	YES Additional client certificate required. NO No client certificate required (default). For more information see SSL/TLS, HTTP(S), and certificates with EntireX.

Adabas-specific attributes

The Adabas-specific attribute section begins with the keyword DEFAULTS = ADABAS. The attributes in this section are required if PSTORE-TYPE = ADABAS is specified. In previous versions of EntireX, these Adabas-specific attributes and values were specified in the broker-specific PSTORE‑TYPE attribute.

Table 11. Adabas-specific attributes
Attribute	Values	Opt/Req	Operating System
Attribute	Values	Opt/Req	z/OS	Linux	Windows
BLKSIZE	126-20000	O	z	u	w
BLKSIZE	Optional blocking factor used for message data. If not specified, broker will split the message data into 2 KB blocks to be stored in Adabas records. The maximum value depends on the physical device assigned to data storage. For more information, see the Adabas documentation. For reasons of efficiency, do not specify a BLKSIZE much larger than the actual total size of the UOW data to be written. The total UOW size is the sum of all messages in the UOW plus 41 bytes of header information. This takes effect only after COLD start. The BLKSIZE parameter applies only for a cold start of broker; subsequently the value of BLKSIZE is taken from the last cold start. Default value is 2000.
DBID	1-32535	R	z	u	w
DBID	Database ID of Adabas database where the persistent store resides.
FNR	1-32535	R	z	u	w
FNR	File number of broker persistent store file.
FORCE-COLD	N \| Y	O	z	u	w
FORCE-COLD	Determines whether a broker cold start is permitted to overwrite a persistent store file that has been used by another broker ID and/or platform. Specify Y to allow existing information to be overwritten.
MAXSCAN	UNLIM \| `n`	O	z	u	w
MAXSCAN	If a numeric value is given, this limits the display of persistent UOW information in the persistent store through Broker Command and Information Services. The default and recommended value is UNLIM.
OPENRQ	N \| Y	O	z	u	w
OPENRQ	Determines whether driver for Adabas persistent store is to issue an `OPEN` command to Adabas.
TRACE-LEVEL	0-4	O	z	u	w
TRACE-LEVEL	Trace level for Adabas persistent store. It overrides the global value of trace level in the attribute file. 0 No tracing. Default value. 1 Log selected Adabas CB fields (command code, response code, subcode, ISN, additions). 2 n/a 3 All of trace level 1, plus UOWID in use for the various Adabas requests and function entered/exit messages. 4 All of trace level 3, plus more Adabas CB fields for successful requests and returned function values. Trace levels 2, 3 and 4 should be used only when requested by IBM Support. If you modify the TRACE-LEVEL attribute, you must restart the broker for the change to take effect. For temporary changes to TRACE-LEVEL without a broker restart, use the EntireX Broker command-line utility ETBCMD.

Application monitoring-specific attributes

The application monitoring-specific attribute section begins with the keyword DEFAULTS=APPLICATION-MONITORING. It contains attributes that apply to the application monitoring functionality. At startup time, the attributes are read if the Broker-specific attribute APPLICATION-MONITORING=YES is specified. Duplicate or missing values are treated as errors. When an error occurs, application monitoring is turned off and EntireX Broker continues execution. For more information, see Application monitoring.

Table 12. Application monitoring-specific attributes
Attribute	Values	Opt/Req	Operating System
Attribute	Values	Opt/Req	z/OS	Linux	Windows
APPLICATION-MONITORING-NAME or APPMON-NAME	A100	O	z	u	w
APPLICATION-MONITORING-NAME or APPMON-NAME	Specifies a default application monitoring name. Used to set the value of the ApplicationName KPI.
COLLECTOR-BROKER-ID	A64	R	z	u	w
COLLECTOR-BROKER-ID	Identifies the Application Monitoring Data Collector. Has the format `host_name`:`port_number`. where, `host_name` is the host where the Application Monitoring Data Collector is running, and `port_number` is the port number of the Application Monitoring Data Collector. The default port is 57900.
TRACE-LEVEL	0-4	O	z	u	w
TRACE-LEVEL	The level of tracing to be performed while the broker is running with application monitoring. 0 No tracing. Default value. 1 Display application monitoring errors. 2 All of trace level 1, plus measuring points for application monitoring. 3 All of trace level 2, plus function entered/exit messages with argument values and monitoring buffers. 4 All of trace level 3, plus returned function values. Trace levels 2, 3 and 4 should be used only when requested by IBM Support. If you modify the TRACE-LEVEL attribute, you must restart the broker for the change to take effect. TRACE-LEVEL cannot be changed dynamically for application monitoring.

Authorization rule-specific attributes

The authorization rule-specific attribute section begins with the keyword DEFAULTS=AUTHORIZATION-RULES. It contains attributes that enhance security-related definitions. At startup time, the attributes are read if the following conditions are met:

Broker-specific attribute SECURITY=YES
Security-specific attributes SECURITY-SYSTEM=OS and SECURITY-LEVEL=AUTHORIZATION

When an error occurs, the EntireX Broker stops. For more information, see Authorization rules.

Table 13. Authorization rule-specific attributes
Attribute	Values	Opt/Req	Operating System
Attribute	Values	Opt/Req	z/OS	Linux	Windows
RULE-NAME	A32	R		u	w
RULE-NAME	Specifies a rule name. A rule is a container for a list of services and a list of client and server user IDs. All users defined in a rule are authorized to use all services defined in this rule. See example under Rules stored in Broker attribute file.
CLASS SERVER SERVICE	A32	R		u	w
CLASS SERVER SERVICE	These three attributes together identify the service. CLASS must be specified first, followed immediately by SERVER and SERVICE. Wildcard service definitions are allowed.
CLIENT-USER-ID	A32	R		u	w
CLIENT-USER-ID	Defines an authorized client user ID.
SERVER-USER-ID	A32	R		u	w
SERVER-USER-ID	Defines an authorized server user ID.

Variable definition file

The broker attribute file contains the configuration of one EntireX Broker instance. In order to share attribute files between different brokers, you identify the attributes that are unique and move them to a variable definition file. This file enables you to share one attribute file among different brokers. Each broker in such a scenario requires its own variable definition file.

The following attributes are considered unique for each machine:

BROKER-ID (in Broker-specific attributes)
PORT (in SSL/TLS-specific attributes and TCP/IP-specific attributes)

How you use the variable definition file will depend upon your particular needs. For instance, some optional attributes may require uniqueness - for example, DBID and FNR in DEFAULTS=ADABAS - so that you may specify the persistent store.