Message Class 0021 - EntireX ACI - Configuration Error in the Attribute File

The specified value for a correct keyword in a configuration file (for instance the Broker attribute file) has too many characters. This response arises in the following situations:

1. During broker startup when the global resources defined in the section DEFAULTS=BROKER are read, a wrong value length is detected within this section. The Broker cannot be started.

2. When a server tries to register with EntireX Broker and the service definition from the DEFAULTS=SERVICE section is read, a wrong value length is detected within this service definition. The service cannot be registered.

Correct the value assigned to the keyword in the configuration file.

The definition of a server class is either missing or invalid.

Either specify a class definition or use the correct values to specify one.

This is a temporary resource shortage. The maximum number of EntireX Broker clients that can be active at one time is reached. A new client cannot be handled until client resources are available again by user timeouts.

Increase NUM-CLIENT (or if CLIENT-NONACT has too high a value, decrease it) in the Broker attribute file.

This is a temporary resource shortage. The maximum number of EntireX Broker servers that can be active at one time is reached. New servers are not accepted until server resources are available again, either by deregistrations or user timeouts.

Try to register the server to EntireX Broker later. If the error occurs freqently, increase NUM-SERVER (or if SERVER-NONACT has too high a value for some services, decrease it) in the Broker attribute file.

A given keyword in a configuration file (for instance the Broker attribute file) is not known by the Broker. This response arises in the following situations:

1. During broker startup, when the global resources defined in the section DEFAULTS=BROKER are read, a wrong keyword is detected within this section. The Broker cannot be started.

2. When a server tries to register with EntireX Broker and the service definition from the DEFAULTS=SERVICE section is read, a wrong keyword is detected within this service definition. The service cannot be registered.

Correct or remove the keyword in the configuration file as appropriate.

The service-specific CONV-LIMIT value is specified with UNLIM. In this special configuration, this is not allowed because the global NUM-CONVERSATION attribute is set to AUTO. See also Broker Resource Allocation.

Either change the global NUM-CONVERSATION parameter to a defined value, or change the specific CONV-LIMIT value to a particular value.

The global CONV_DEFAULT attribute is either specified as UNLIMIT or not specified at all. The error occurs in situations where EntireX Broker cannot calculate the number of conversations needed. This situation occurs if

• NUM-CONVERSATION=AUTO and CONV-DEFAULT=UNLIM and there is at least one service that does not assign CONV-LIMIT, or

• NUM-CONVERSATION=AUTO and CONV-DEFAULT is undefined and there is at least one service that does not assign CONV-LIMIT.

Correct the error in the attribute file. Define NUM-CONVERSATION with a particular value or define CONV-DEFAULT with a particular value or use the CONV-LIMIT attribute for every single service definition.

The specified value for a correct keyword a configuration file (for instance the Broker attribute file) must not be zero or null value. This response arises in the following situations:

1. During broker startup, when the global resources defined in the section DEFAULTS=BROKER are read, a value of zero or null is detected for a value within this section. The Broker cannot be started.

2. When a server tries to register with EntireX Broker and the service definition from the DEFAULTS=SERVICE section is read, a value of zero or null is detected within this service definition. The service cannot be registered.

Correct the value assigned to the keyword in the configuration file.

The specified value for a correct keyword in a configuration file (for instance the Broker attribute file) is out of range. This response arises in the following situations:

1. During broker startup when the global resources defined in the section DEFAULTS=BROKER are read, the wrong value is detected for a value within this section. The Broker cannot be started.

2. When a server tries to register with EntireX Broker and the service definition from the DEFAULTS=SERVICE section is read, a wrong value is detected within this service definition. The service cannot be registered.

Correct the value assigned to the keyword in the configuration file.

The specified value for a correct keyword in a configuration file (for instance the Broker attribute file) is wrong. This response arises in the following situations:

1. During broker startup, when the global resources defined in the section DEFAULTS=BROKER are read, a wrong value is detected for a value within this section. The Broker cannot be started.

2. When a server tries to register with EntireX Broker and the service definition from the DEFAULTS=SERVICE section is read, a wrong value is detected within this service definition. The service cannot be registered.

Correct the value assigned to the keyword in the configuration file.

The service-specific SHORT-BUFF-LIMIT value is specified with UNLIM. In this special configuration this is not allowed because the global NUM-SHORT-BUFFER attribute is set to AUTO. See also Broker Resource Allocation.

Either change the global NUM-SHORT-BUFFER parameter to a defined value, or change the specific SHORT-BUFF-LIMIT value to a particular value.

The global SHORT-BUFF-DEF attribute is either specified as UNLIMIT or not specified at all. The error occurs in situation where EntireX Broker cannot calculate the number of short buffers needed. This situation occurs if:

• NUM-SHORT-BUFFER=AUTO and NUM-SHORT-DEF=UNLIM and there is at least one service that does not assign SHORT-BUFF-LIMIT, or

• NUM-SHORT-BUFFER=AUTO and NUM-SHORT-DEF is undefined and there is at least one service that does not assign SHORT-BUFF-LIMIT.

Correct the error in the attribute file. Define NUM-SHORT-BUFFER with a particular value or define NUM-SHORT-DEF with a particular value or use the SHORT-BUFF-LIMIT attribute for every single service definition.

The service-specific LONG-BUFF-LIMIT value is specified with UNLIM. In this special configuration, this is not allowed because the global NUM-LONG-BUFFER attribute is set to AUTO.

Either change the global NUM-LONG-BUFFER parameter to a defined value, or change the specific SHORT-LONG-LIMIT value to a particular value.

The global LONG-BUFF-DEF attribute is either specified as UNLIM or not specified at all. The error occurs in situation where EntireX Broker cannot calculate the number of long buffers needed. This situation occurs if:

• NUM-LONG-BUFFER=AUTO and NUM-LONG-DEF=UNLIM and there is at least one service that does not assign LONG-BUFF-LIMIT, or

• NUM-LONG-BUFFER=AUTO and NUM-LONG-DEF is undefined and there is at least one service that does not assign LONG-BUFF-LIMIT

Correct the error in the attribute file. Define NUM-LONG-BUFFER with a particular value or define NUM-LONG-DEF with a particular value or use the LONG-BUFF-LIMIT attribute for every single service definition.

The DEFAULTS=SERVICE section in the attribute file could not be found.

Correct the etbfile and provide a valid DEFAULTS=SERVICE section. See Service-specific Attributes under Broker Attributes.

An unknown attribute definition was found. Please refer to the entry in a configuration file (for instance the Broker attribute file) in order to find the line and the column where this error occurred.

Correct the broker attribute file and provide valid attribute definitions. See Service-specific Attributes under Broker Attributes.

The valid values for this attribute are YES or NO only. Please refer to the entry in the log file to find the line and the column where the error happened.

Correct the etbfile and select either YES or NO for the attribute where the error happened

A configuration file (for instance the Broker attribute file) cannot be accessed. This response arises in the following situations:

1. During broker startup, when the global resources defined in the section DEFAULTS=BROKER are read, the Broker cannot be started.

2. When a server tries to register with EntireX Broker and the service definition from the DEFAULTS=SERVICE section is read, this service cannot be used.

Contact administrator or check for the following causes:

1. No configuration file is allocated to the Broker.

2. The specified configuration file does not exist.

3. EntireX Broker has no access to the configuration file, for example for security reasons, or the configuration file is enqueued by another process.

4. The configuration file has an invalid format for the platform used. Refer to the appropriate Installation documentation.

A configuration file (for instance the Broker attribute file) cannot be accessed. This response arises in the following situations:

1. During broker startup, when the global resources defined in the section DEFAULTS=BROKER are read, the Broker cannot be started.

2. When a server tries to register with EntireX Broker and the service definition from the DEFAULTS=SERVICE section is read, this service cannot be used.

Check all causes listed under error 0038, and then the following:
Ensure that no other process has changed the file characteristics of the configuration file.

EntireX Broker did not find the service definition within the attribute file when a service attempted to register.

Check the service specified in the CLASS, SERVER and SERVICE fields in the API, or make sure the service definition in the Broker attribute file is valid.

The specified value for a correct keyword in a configuration file (for instance the Broker attribute file) is wrong, that is, not alphanumeric. This response arises in the following situations:

1. During broker startup, when the global resources defined in the section DEFAULTS=BROKER are read, a wrong value is detected for a value within this section. The Broker cannot be started.

2. When a server tries to register with EntireX Broker and the service definition from the DEFAULTS=SERVICE section is read, a wrong value is detected within this service definition. The service cannot be registered.

Correct the value assigned to the keyword in the configuration file.

The maximum number of EntireX Broker services that can be active at one time is reached. A subsequent service register request is not accepted.

Try again later. If this error occurs frequently, increase the NUM-SERVICE attribute in the section DEFAULTS=BROKER in the Broker attribute file.

The maximum number of EntireX Broker topics that can be active at one time is reached.

Try again later. If this error occurs frequently, increase the NUM-TOPIC attribute in the section DEFAULTS=BROKER in the Broker attribute file.

A topic is defined as ALLOW-DURABLE=YES but there is no subscriber store defined to save the subscriber data on any store.

Either change the topic attributes to ALLOW-DURABLE=NO, which makes it impossible to make a durable subscription, or set the value of global attribute SUBSCRIBER-STORE to PSTORE. A valid SUBSCRIBER-STORE requires additional attributes for the persistent store type etc.

Note:
The secondary persistent store (SSTORE) feature is no longer available. We recommend you use the PSTORE persistent store to store your subscriber data, by setting Broker-specific parameter SUBSCRIBER-STORE=PSTORE.

An EntireX Broker call involving PSTORE is requested but EntireX Broker runs with setting PSTORE=NO. Any PSTORE operation is prohibited.

Contact your Broker Administrator.

EntireX Broker did not find the topic definition within the attribute file when a topic attempted to subscribe.

Check the topic specified in the TOPIC field in the API, or make sure the topic definition in the Broker attribute file is valid.

A mismatch in the Broker attribute file has been detected: If an ENCRYPTION-LEVEL is specified, then SECURITY must be set to YES.

Verify that the security exit is present and set SECURITY=YES to enable ENCRYPTION-LEVEL processing.

Note:
The Broker attribute setting SECURITY=NO cannot be used with any encryption level not equal to 0 (= zero); otherwise the 00210402 error condition will occur when application issues registration command.

SUBSCRIBER-STORE=PSTORE is defined in Broker attribute file, but PSTORE is set to NO in order to disable the persistent store for this Broker run.

Set PSTORE=COLD or PSTORE=HOT to run Broker with enabled PSTORE.

NUM-SUBSCRIBER-TOTAL must be greater than or equal to NUM-SUBSCRIBER. This parameter is required if SUBSCRIBER-STORE=PSTORE is defined.

Set NUM-SUBSCRIBER-TOTAL to AUTO or use a value greater than or equal to NUM-SUBSCRIBER.

NUM-TOPIC-TOTAL must be greater than or equal to NUM-TOPIC. This parameter is required if SUBSCRIBER-STORE=PSTORE is defined.

Set NUM-TOPIC-TOTAL to AUTO or use a value greater than or equal to NUM-TOPIC.

A mismatch in the broker attribute file has been detected: if the catch-all service has been defined (CLASS= *, SERVER= *, SERVICE = *) then the value of AUTO is not allowed for the NUM-CONVERSATION, NUM-LONG-BUFFER or NUM-SHORT-BUFFER attributes.

If the catch-all service is defined, make sure the attributes NUM-CONVERSATION, NUM-LONG-BUFFER and NUM-SHORT-BUFFER all have specified values.

A configuration file (for instance the Broker attribute file) cannot be read.

Make sure that the configuration file is readable and not corrupt.

The service-specific SERVER-LIMIT value is specified with UNLIM. In this special configuration, this is not allowed because the global NUM-SERVER attribute is set to AUTO. See also Broker Resource Allocation.

Either change the global NUM-SERVER parameter to a defined value, or change the specific SERVER-LIMIT value to a particular value.

The global SERVER-DEFAULT attribute is either specified as UNLIM or not specified at all. The error occurs in situations where EntireX Broker cannot calculate the number of servers needed. This situation occurs if

• NUM-SERVER=AUTO and SERVER-DEFAULT=UNLIM and there is at least one service that does not assign SERVER-LIMIT, or

• NUM-SERVER=AUTO and SERVER-DEFAULT is undefined and there is at least one service that does not assign SERVER-LIMIT.

Correct the error in the attribute file. Define NUM-SERVER with a particular value or define SERVER-DEFAULT with a particular value or use the SERVER-LIMIT attribute for every single service definition.

The global PUBLICATION-DEFAULT attribute is either specified as UNLIM or not specified at all. The error occurs in situations where EntireX Broker cannot calculate the number of publications needed. This situation occurs if

• NUM-PUBLICATION=AUTO and PUBLICATION-DEFAULT=UNLIM and there is at least one topic that does not assign PUBLICATION-LIMIT, or

• NUM-PUBLICATION=AUTO and PUBLICATION-DEFAULT is undefined and there is at least one topic that does not assign PUBLICATION-LIMIT.

Correct the error in the attribute file. Define NUM-PUBLICATION with a particular value or define PUBLICATION-DEFAULT with a particular value or use the PUBLICATION-LIMIT attribute for every single topic definition.

The topic-specific PUBLICATION-LIMIT value is specified with UNLIM. In this special configuration, this is not allowed because the global NUM-PUBLICATION attribute is set to AUTO. See also Broker Resource Allocation.

Either change the global NUM-PUBLICATION parameter to a defined value, or change the specific PUBLICATION-LIMIT value to a particular value.

The global SUBSCRIBER-DEFAULT attribute is either specified as UNLIM or not specified at all. The error occurs in situations where EntireX Broker cannot calculate the number of subscribers needed. This situation occurs if

• NUM-SUBSCRIBER=AUTO and SUBSCRIBER-DEFAULT=UNLIM and there is at least one topic that does not assign SUBSCRIBER-LIMIT, or

• NUM-SUBSCRIBER=AUTO and SUBSCRIBER-DEFAULT is undefined and there is at least one topic that does not assign SUBSCRIBER-LIMIT.

Correct the error in the attribute file. Define NUM-SUBSCRIBER with a particular value or define SUBSCRIBER-DEFAULT with a particular value or use the SUBSCRIBER-LIMIT attribute for every single topic definition.

The topic-specific SUBSCRIBER-LIMIT value is specified with UNLIM. In this special configuration, this is not allowed because the global NUM-SUBSCRIBER attribute is set to AUTO. See also Broker Resource Allocation.

Either change the global NUM-SUBSCRIBER parameter to a defined value, or change the specific SUBSCRIBER-LIMIT value to a particular value.

The DEFAULTS=TOPIC section in the attribute file could not be found.

Correct the etbfile and provide a valid DEFAULTS=TOPIC section. See Topic-specific Attributes under Broker Attributes.

A mismatch in the broker attribute file has been detected: if a catch-all topic has been defined (example: TOPIC= *), then the value of AUTO is not allowed for the NUM-PUBLICATION, NUM-LONG-BUFFER, NUM-SHORT-BUFFER, or NUM-SUBSCRIBER attributes.

If a catch-all topic is defined, make sure the attributes NUM-PUBLICATION, NUM-LONG-BUFFER, NUM-SHORT-BUFFER, and NUM-SUBSCRIBER all have specified values.

TOPIC attribute specifies ALLOW-DURABLE=NO, but application has requested to subscribe durably.

Ensure broker attribute file is consistent with the intention of the application.

This is a temporary resource shortage. The maximum number of EntireX Broker publishers that can be active at one time is reached. A new publisher cannot be handled until publisher resources are available again by user timeouts.

Increase NUM-PUBLISHER (or if PUBLISHER-NONACT has too high a value, decrease it) in the Broker attribute file.

This is a temporary resource shortage. The maximum number of EntireX Broker subscribers that can be active at one time is reached. A new subscriber cannot be handled until subscriber resources are available again by user timeouts.

Increase NUM-SUBSCRIBER (or if SUBSCRIBER-NONACT has too high a value, decrease it) in the Broker attribute file.

You cannot specify the same PORT number twice for the same HOST.

Specify a different PORT number.

The maximum number of AUTHORIZATIONRULE entries in the attribute file has been reached. The current maximum number is 16 authorization rules.

Reduce the number of AUTHORIZATIONRULE entries.

You cannot specify more than five HOST entries per section.

Reduce number of HOST entries.

You cannot specify more than five PORT entries per section.

Reduce number of PORT entries.

The minimum value NUM-CCOM=1 is required if you want to run the Entire Net-Work communicator on UNIX.

Set NUM-CCOM=1, or higher.

You cannot specify the same PORT number twice for the same HOST.

Specify a different PORT number.

You cannot specify more than five STACK-NAME entries per section.

Reduce number of STACK-NAME entries.

The broker attribute file is missing a DEFAULTS section. Additional error information will display the section name.

Consult the additional error text and take appropriate action.

A variable in a configuration file (for instance the Broker attribute file) could not be exanded. Additional error information will display the variable name.

Consult the additional error text and take appropriate action.

Transport types SSL or TCP are supported for Broker attribute PARTNER-CLUSTER-ADDRESS.

Adjust the PARTNER-CLUSTER-ADDRESS to use a supported transport type.

The Standby Broker instance must use PSTORE=HOT in order to perform a PSTORE takeover if necessary.

Define PSTORE=HOT for your Standby Broker.

The Load Broker (RUN-MODE=PSTORE-LOAD) must use PSTORE=COLD in order to create a new persistent store.

Define PSTORE=COLD for your Load Broker.

The Unload Broker must use PSTORE=HOT in order to migrate a persistent store.

Define PSTORE=HOT for your Unload Broker.

The PARTNER-CLUSTER-ADDRESS defined in the Standard Broker does not match any of the TCP or SSL transport entries defined in the Standby Broker.

Either adjust PARTNER-CLUSTER-ADDRESS in Standard Broker or start Standby Broker with a matching transport entry.

There is no PARTNER-CLUSTER-ADDRESS definition in the Standard Broker.

Define PARTNER-CLUSTER-ADDRESS in the Standard Broker to allow running a Standby Broker.

The persistent store defined in Standard Broker and Standby Broker must be exactly the same.

Adjust the attributes for PSTORE-TYPE and the PSTORE specific sections in each Broker attribute file so both Broker instances match.

There is no PSTORE defined in the partner Broker instance.

Run the partner Broker with matching persistent store attributes.

The persistent stores defined in Load Broker and Unload Broker must be different.

Adjust the attributes for PSTORE-TYPE and the PSTORE specific sections for both Broker instances. Make sure the Load Broker is assigned to a new persistent store, and your Unload Broker is assigned to the persistent store you wish to unload.