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.

Value in attribute file with leading '-' or '+' character. This syntax is not supported.

Enter a correct value.

Wrong numeric value in attribute file detected. Value contains comma or decimal point.

Enter a correct value.

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 frequently, 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 the 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 attribute file and provide a valid DEFAULTS=SERVICE section. See Service-specific Attributes.

A duplicate keyword has been detected in a configuration file (for example the broker attribute file). This response arises in the following situations:

1. During broker startup, when the global resources defined in the section DEFAULTS=BROKER are read, duplicate keywords are 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, duplicate keywords are detected within this service definition. The REGISTER request is refused.

Eliminate the duplicate keyword in the broker attribute file.

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.

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

Correct the attribute file 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 this keyword in the Broker attribute file is wrong, that is, not numeric. 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 Broker attribute file.

More than 16 occurrences of this attribute were detected.

Reduce number of occurrences to 16.

The specified port is not a numeric or outside of range 1-65535.

Enter a valid port number.

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.

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.

The value for the COLLECTOR-BROKER-ID value was not correctly specified.

Enter correct value host:port for COLLECTOR-BROKER-ID. See COLLECTOR-BROKER-ID under Application Monitoring-specific Broker Attributes.

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.

Notes:

1. 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.
2. For encrypted transport we strongly recommend using the Secure Sockets Layer/Transport Layer Security protocol. See SSL/TLS, HTTP(S), and Certificates with EntireX.

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.

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

Specify a different PORT number.

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

Reduce the number of AUTHORIZATION-RULE 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 Linux.

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 expanded. 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 attribute TRANSLATION contains an invalid parameter.

Correct the attribute file. See TRANSLATION under Service-specific Broker Attributes.

Attribute TRUST-STORE in the SSL section is missing.

Define attribute TRUST-STORE. See TRUST-STORE under SSL-specific Broker Attributes.

The specified file for TRUST-STORE does not exist.

Correct the file name. See TRUST-STORE under SSL-specific Broker Attributes.

Attribute KEY-STORE in the SSL section is missing.

Define attribute KEY-STORE. See KEY-STORE under SSL-specific Broker Attributes.

The specified file for KEY-STORE does not exist.

Correct the file name. See KEY-STORE under SSL-specific Broker Attributes.

Attribute KEY-FILE in the SSL section is missing.

Define attribute KEY-FILE. See KEY-FILE under SSL-specific Broker Attributes.

The specified file for KEY-FILE does not exist.

Correct the file name. See KEY-FILE under SSL-specific Broker Attributes.

No KEY-PASSWD has been specified.

Define attribute KEY-PASSWD with the password used for the KEY-FILE.

VERIFY-CLIENT=YES was specified but TRUST-STORE was not defined in the SSL section of the attribute file.

Define attribute TRUST-STORE. See TRUST-STORE under SSL-specific Broker Attributes.

An operator command was issued to turn on/off the Dynamic Worker Management, but it was not enabled in the attribute file.

Specify attribute DYNAMIC-WORKER-MANAGEMENT=YES and restart Broker. See DYNAMIC-WORKER-MANAGEMENT under Broker-specific Broker Attributes.

An operator command was issued to turn on the Dynamic Worker Management but it was already enabled.

None.

An operator command was issued to turn off the Dynamic Worker Management but it was already disabled.

None.

Attribute STORE in section DEFAULTS=DIV was not specified.

Enter attribute STORE. See STORE under DIV-specific Broker Attributes.

Attribute DDNAME in section DEFAULTS=DIV was not specified.

Enter attribute DDNAME and add the corresponding DD statement to the JCL of Broker. See DDNAME under DIV-specific Broker Attributes.

The directory specified as value of PATH does not exist.

Enter a valid directory. See PATH under c-tree-specific Attributes.

The value of PSTORE-VERSION does not match the version of PSTORE.

Change the value of PSTORE-VERSION to the effective version or rerun Broker with PSTORE=COLD. See PSTORE-VERSION and PSTORE-TYPE under Broker-specific Broker Attributes.

The value of PSTORE-VERSION does not match the version of PSTORE.

Change the value of PSTORE-VERSION to the effective version or rerun Broker with PSTORE=COLD. See PSTORE-VERSION and PSTORE-TYPE under Broker-specific Broker Attributes.

Attribute SVC was not specified in the DEFAULTS=ADABAS section. Adabas PSTORE cannot be reached.

Specify SVC=svc_number used by the Adabas PSTORE database.

Attributes DBID and FNR in section DEFAULTS=ADABAS are not supplied.

Enter attributes DBID and FNR. See DBID and FNR under Adabas-specific Broker Attributes.

The value of attribute BLKSIZE in section DEFAULTS=ADABAS is invalid.

Enter valid value (range 126-20000 bytes) for attribute BLKSIZE. See BLKSIZE under Adabas-specific Broker Attributes.

Security attributes SECURITY-SYSTEM=LDAP and SECURITY-LEVEL=AUTHORIZATION have been defined but no URL was specified to access the LDAP server.

Enter attribute LDAP-AUTHORIZATION-URL. See LDAP-AUTHORIZATION-URL under Security-specific Broker Attributes.

For PSTORE-TYPE=ADABAS and PSTORE-VERSION 4 or below: Limit of 191 multiple fields was exceeded.

Allocate the Adabas PSTORE file with the delivered JCL member.

The Adabas PSTORE handler was unable to load the Adabas link routine.

Assign the Adabas load library.

The value for Adabas PSTORE attribute MAXSCAN exceeded.

Increase attribute MAXSCAN.

The Adabas PSTORE handler detected a mismatch between required and effective field descriptor table (FDT).

Recreate the Adabas PSTORE file.

Attribute ACI-CONVERSION=YES requires attribute ICU-CONVERSION=YES.

Correct the Broker attribute file. See ACI-CONVERSION and ICU-CONVERSION under Broker-specific Broker Attributes.

Attribute ACI-CONVERSION=YES requires a section DEFAULTS=CODEPAGE.

Correct the Broker attribute file. See ACI-CONVERSION under Broker-specific Broker Attributes and DEFAULTS=CODEPAGE.

The conversion failed due to an error. The translation is used to convert the data.

Check the subsequent error messages and correct the error.

The PSTORE requires PSTORE-VERSION 5 or above.

A cold start is required when changing to a higher PSTORE-VERSION. See PSTORE=COLD under Broker-specific Broker Attributes.

Allocate a PSTORE with following attributes:

PSTORE=COLD
PSTORE-VERSION=5

No records in Adabas PSTORE.

Define PSTORE=COLD instead of PSTORE=HOT if this is the correct Adabas database and file.

The platform ID in the master record is wrong. This is probably a wrong database or the PSTORE of a different Broker.

Check the DEFAULTS=ADABAS settings.

The BROKER-ID in the master record does not match the BROKER-ID. This is probably a wrong database or the PSTORE of a different Broker.

Check the DEFAULTS=ADABAS settings.

Attribute BLKSIZE does not match the Adabas file BLKSIZE of the cold start.

Enter the correct BLKSIZE attribute value or rerun a cold start.