This message class is given in case of invalid or missing information in the Broker attribute file. This is mostly a configuration error. The situation can be examined using the error number returned and after correction, the applications can be restarted. The messages have the format:
0021nnnn
where | 0021 | is the message class, and |
nnnn | is the message number in the range 0000 - 9999 |
00210013 | 00210014 | 00210015 | 00210016 | 00210017 | 00210018 | 00210019 | 00210023 | 00210024 | 00210025 | 00210026 | 00210027 | 00210028 | 00210029 | 00210030 | 00210032 | 00210033 | 00210034 | 00210035 | 00210036 | 00210037 | 00210038 | 00210040 | 00210043 | 00210045 | 00210059 | 00210080 | 00210096 | 00210097 | 00210112 | 00210269 | 00210368 | 00210385 | 00210402 | 00210414 | 00210415 | 00210416 | 00210423 | 00210431 | 00210446 | 00210447 | 00210459 | 00210460 | 00210461 | 00210462 | 00210463 | 00210470 | 00210474 | 00210490 | 00210491 | 00210501 | 00210547 | 00210548 | 00210549 | 00210559 | 00210564 | 00210568 | 00210591 | 00210594 | 00210622 | 00210628 | 00210629 | 00210630 | 00210652 | 00210703 | 00210704 | 00210705 | 00210706 | 00210707 | 00210708 | 00210709 | 00210710 | 00210713 | 00210714 | 00210715 | 00210722 | 00210723 | 00210727 | 00210740 | 00210741 | 00210760 | 00210761 | 00210762 | 00210763 | 00210764 | 00210796 | 00210797 | 00210798 | 00210827 | 00210829 | 00210832 | 00210834 | 00210835 | 00210837 | 00210838 | 00210839 | 00210840 | 00210843 | 00210845 | 00210846 | 00210847
00210013 | Value For Keyword Too Long |
Explanation |
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:
|
Action |
Correct the value assigned to the keyword in the configuration file. |
00210014 | Class def missing or invalid |
Explanation |
The definition of a server class is either missing or invalid. |
Action |
Either specify a class definition or use the correct values to specify one. |
00210015 | Max Possible NUM-CLIENT Reached |
Explanation |
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. |
Action |
Increase |
00210016 | Signed number as value not supported |
Explanation |
Value in attribute file with leading '-' or '+' character. This syntax is not supported. |
Action |
Enter a correct value. |
00210017 | Value is not an integral number |
Explanation |
Wrong numeric value in attribute file detected. Value contains comma or decimal point. |
Action |
Enter a correct value. |
00210018 | Max Possible NUM-SERVER Reached |
Explanation |
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. |
Action |
Try to register the server to EntireX Broker later. If the error occurs
frequently, increase |
00210019 | TRANSLATION Not Specified |
00210023 | Unknown attribute: |
Explanation |
Unknown keyword in attribute file detected. |
Action |
Enter a correct keyword. |
00210024 | CONV-LIMIT may not be UNLIM |
Explanation |
The service-specific |
Action |
Either change the global |
00210025 | CONV-DEFAULT not spec or UNLIM |
Explanation |
The global
|
Action |
Correct the error in the attribute file. Define
|
00210026 | Zero Value For Keyword Not Allowed |
Explanation |
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:
|
Action |
Correct the value assigned to the keyword in the configuration file. |
00210027 | Value For Keyword Out Of Range |
Explanation |
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:
|
Action |
Correct the value assigned to the keyword in the configuration file. |
00210028 | Invalid Value For Keyword |
Explanation |
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:
|
Action |
Correct the value assigned to the keyword in the configuration file. |
00210029 | SHORT-BUFF-LIMIT may not be UNLIM |
Explanation |
The service-specific |
Action |
Either change the global |
00210030 | SHORT-BUFF-DEF not spec or UNLIM |
Explanation |
The global
|
Action |
Correct the error in the attribute file. Define
|
00210032 | LONG-BUFF-LIMIT may not be UNLIM |
Explanation |
The service-specific |
Action |
Either change the global |
00210033 | LONG-BUFF-DEF not spec or UNLIM |
Explanation |
The global
|
Action |
Correct the error in the attribute file. Define
|
00210034 | SERVICE Section missing |
Explanation |
The |
Action |
Correct the attribute file and provide a valid |
00210035 | Duplicate Value Found |
Explanation |
A duplicate keyword has been detected in a configuration file (for example the broker attribute file). This response arises in the following situations:
|
Action |
Eliminate the duplicate keyword in the broker attribute file. |
00210036 | Unknown service attribute |
Explanation |
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. |
Action |
Correct the broker attribute file and provide valid attribute definitions. See Service-specific Attributes. |
00210037 | Value must be YES or NO |
Explanation |
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. |
Action |
Correct the attribute file and select either YES or NO for the attribute where the error happened |
00210038 | Error During Open Of File |
Explanation |
A configuration file (for instance the Broker attribute file) cannot be accessed. This response arises in the following situations:
|
Action |
Contact administrator or check for the following causes:
|
00210040 | Error During Close Of File |
Explanation |
A configuration file (for instance the Broker attribute file) cannot be accessed. This response arises in the following situations:
|
Action |
Check all causes listed under error 0038, and then the following: |
00210043 | Service Definition Not Found |
Explanation |
EntireX Broker did not find the service definition within the attribute file when a service attempted to register. |
Action |
Check the service specified in the |
00210045 | Value for %s must be numeric |
Explanation |
The specified value for this keyword in the Broker attribute file is wrong, that is, not numeric. This response arises in the following situations:
|
Action |
Correct the value assigned to the keyword in the Broker attribute file. |
00210059 | Maximum of 16 rules exceeded |
Explanation |
More than 16 occurrences of this attribute were detected. |
Action |
Reduce number of occurrences to 16. |
00210080 | Invalid port number |
Explanation |
The specified port is not a numeric or outside of range 1-65535. |
Action |
Enter a valid port number. |
00210096 | Max Possible NUM-SERVICE Reached |
Explanation |
The maximum number of EntireX Broker services that can be active at one time is reached. A subsequent service register request is not accepted. |
Action |
Try again later. If this error occurs frequently, increase the
|
00210097 | Max possible NUM-TOPIC reached |
Explanation |
The maximum number of EntireX Broker topics that can be active at one time is reached. |
Action |
Try again later. If this error occurs frequently, increase the |
00210112 | No SUBSCRIBER-STORE assigned |
Explanation |
A topic is defined as |
Action |
Either change the topic attributes to
Note: |
00210269 | PSTORE required |
Explanation |
An EntireX Broker call involving |
Action |
Contact your Broker Administrator. |
00210368 | No host:port value specified |
Explanation |
The value for the |
Action |
Enter correct value host:port for |
00210385 | Topic definition not found |
Explanation |
EntireX Broker did not find the topic definition within the attribute file when a topic attempted to subscribe. |
Action |
Check the topic specified in the |
00210402 | SECURITY/ENCRYPTION-LEVEL mismatch |
Explanation |
A mismatch in the Broker attribute file has been detected: If an
|
Action |
Verify that the security exit is present and set Notes:
|
00210414 | SUBSCRIBER-STORE needs PSTORE |
Explanation |
|
Action |
Set |
00210415 | NUM-SUBSCRIBER-TOTAL too small |
Explanation |
|
Action |
Set |
00210416 | NUM-TOPIC-TOTAL too small |
Explanation |
|
Action |
Set |
00210423 | AUTO/Catch-All Service mismatch |
Explanation |
A mismatch in the broker attribute file has been detected: if the
catch-all service has been defined ( |
Action |
If the catch-all service is defined, make sure the attributes
|
00210431 | Error during read of file |
Explanation |
A configuration file (for instance the Broker attribute file) cannot be read. |
Action |
Make sure that the configuration file is readable and not corrupt. |
00210446 | ATTR: SERVER-LIMIT may not be UNLIM |
Explanation |
The service-specific |
Action |
Either change the global |
00210447 | ATTR: SERVER-DEFAULT not spec or UNLIM |
Explanation |
The global
|
Action |
Correct the error in the attribute file. Define
|
00210459 | PUBLICATION-DEFAULT not spec/UNLIM |
Explanation |
The global
|
Action |
Correct the error in the attribute file. Define
|
00210460 | PUBLICATION-LIMIT may not be UNLIM |
Explanation |
The topic-specific |
Action |
Either change the global |
00210461 | SUBSCRIBER-DEFAULT not spec/UNLIM |
Explanation |
The global
|
Action |
Correct the error in the attribute file. Define
|
00210462 | SUBSCRIBER-LIMIT may not be UNLIM |
Explanation |
The topic-specific |
Action |
Either change the global |
00210463 | TOPIC Section missing |
Explanation |
The |
Action |
Correct the attribute file and provide a valid
|
00210470 | AUTO/Catch-All Topic mismatch |
Explanation |
A mismatch in the broker attribute file has been detected: if a catch-all
topic has been defined (example: |
Action |
If a catch-all topic is defined, make sure the attributes
|
00210474 | Durable SUBSCRIBE not allowed |
Explanation |
TOPIC attribute specifies |
Action |
Ensure broker attribute file is consistent with the intention of the application. |
00210490 | Max possible NUM-PUBLISHER reached |
Explanation |
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. |
Action |
Increase |
00210491 | Max possible NUM-SUBSCRIBER reached |
Explanation |
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. |
Action |
Increase |
00210501 | TCP-PORT numbers not unique |
Explanation |
You cannot specify the same |
Action |
Specify a different |
00210547 | Max num AUTHORIZATION-RULE reached |
Explanation |
The maximum number of |
Action |
Reduce the number of |
00210548 | Max num HOST entries reached |
Explanation |
You cannot specify more than five |
Action |
Reduce number of |
00210549 | Max num PORT entries reached |
Explanation |
You cannot specify more than five |
Action |
Reduce number of |
00210559 | ATTR: TRANSPORT = NET and NUM-CCOM = 0 |
Explanation |
The minimum value |
Action |
Set |
00210564 | SSL-PORT numbers not unique |
Explanation |
You cannot specify the same |
Action |
Specify a different |
00210568 | Max num STACK-NAME entries reached |
Explanation |
You cannot specify more than five
|
Action |
Reduce number of |
00210591 | DEFAULTS section missing |
Explanation |
The broker attribute file is missing a |
Action |
Consult the additional error text and take appropriate action. |
00210594 | ATTR: Variable not expanded |
Explanation |
A variable in a configuration file (for instance the Broker attribute file) could not be expanded. Additional error information will display the variable name. |
Action |
Consult the additional error text and take appropriate action. |
00210622 | Transport type not supported |
Explanation |
Transport types SSL or TCP are supported for Broker attribute
|
Action |
Adjust the |
00210628 | Expect PSTORE=HOT in STANDBY mode |
Explanation |
The Standby Broker instance must use
|
Action |
Define |
00210629 | Expect PSTORE=COLD in LOAD mode |
Explanation |
The Load Broker ( |
Action |
Define |
00210630 | Expect PSTORE=HOT in UNLOAD mode |
Explanation |
The Unload Broker must use |
Action |
Define |
00210652 | Invalid keyword in TRANSLATION parms |
Explanation |
The attribute |
Action |
Correct the attribute file. See |
00210703 | Missing attribute TRUST-STORE |
Explanation |
Attribute |
Action |
Define attribute |
00210704 | TRUST-STORE does not exist |
Explanation |
The specified file for TRUST-STORE does not exist. |
Action |
Correct the file name. |
00210705 | Missing attribute KEY-STORE |
Explanation |
Attribute KEY-STORE in the SSL section is missing. |
Action |
Define attribute |
00210706 | KEY-STORE does not exist |
Explanation |
The specified file for |
Action |
Correct the file name. |
00210707 | Missing attribute KEY-FILE |
Explanation |
Attribute |
Action |
Define attribute |
00210708 | KEY-FILE does not exist |
Explanation |
The specified file for |
Action |
Correct the file name. |
00210709 | KEY-FILE specified but no KEY-PASSWD |
Explanation |
No |
Action |
Define attribute |
00210710 | VERIFY-CLIENT=YES but no TRUST-STORE |
Explanation |
|
Action |
Define attribute |
00210713 | Dynamic Worker Management not runnung |
Explanation |
An operator command was issued to turn on/off the Dynamic Worker Management, but it was not enabled in the attribute file. |
Action |
Specify attribute |
00210714 | Dynamic Worker Mgmt already enabled |
Explanation |
An Operator command was issued to turn on the Dynamic Worker Management but it was already enabled. |
Action |
None. |
00210715 | Dynamic Worker Mgmt already disabled |
Explanation |
An Operator command was issued to turn off the Dynamic Worker Management but it was already disabled. |
Action |
None. |
00210722 | DIV: STORE not specified |
Explanation |
Attribute |
Action |
Enter attribute |
00210723 | DIV: DDNAME not specified |
Explanation |
Attribute |
Action |
Enter attribute |
00210727 | c-tree PATH does not exist |
Explanation |
The directory specified as value of |
Action |
Enter a valid directory. See |
00210740 | PSTORE requires higher PSTORE-VERSION |
Explanation |
The value of |
Action |
Change the value of |
00210741 | PSTORE requires lower PSTORE-VERSION |
Explanation |
The value of |
Action |
Change the value of |
00210760 | PARTNER-CLUSTER-ADDRESS mismatch |
Explanation |
The |
Action |
Either adjust |
00210761 | PARTNER-CLUSTER-ADDRESS missing |
Explanation |
There is no |
Action |
Define |
00210762 | PSTORE-TYPE mismatch |
Explanation |
The persistent store defined in Standard Broker and Standby Broker must be exactly the same. |
Action |
Adjust the attributes for |
00210763 | PSTORE-TYPE missing |
Explanation |
There is no |
Action |
Run the partner Broker with matching persistent store attributes. |
00210764 | Same PSTORE for UNLOAD and LOAD |
Explanation |
The persistent stores defined in Load Broker and Unload Broker must be different. |
Action |
Adjust the attributes for |
00210796 | Adabas SVC number must be supplied |
Explanation |
Attribute |
Action |
Specify |
00210797 | ADABAS DBID and FNR must be supplied |
Explanation |
Attributes |
Action |
Enter attributes |
00210798 | Invalid BLKSIZE (range 126-20000 bytes) |
Explanation |
The value of attribute |
Action |
Enter valid value (range 126-20000 bytes) for attribute |
00210827 | LDAP: Missing LDAP-AUTHORIZATION-URL |
Explanation |
Security attributes |
Action |
Enter attribute |
00210829 | PSTORE: Max MU 191 exceeded |
Explanation |
For |
Action |
Allocate the Adabas PSTORE file with the delivered JCL member. |
00210832 | PSTORE: Cannot load ADABAS link module |
Explanation |
The Adabas PSTORE handler was unable to load the Adabas link routine. |
Action |
Assign the Adabas load library. |
00210834 | PSTORE: MAXSCAN value exceeded |
Explanation |
The value for Adabas PSTORE attribute |
Action |
Increase attribute MAXSCAN. |
00210835 | PSTORE: Mismatching ADABAS FDT |
Explanation |
The Adabas PSTORE handler detected a mismatch between required and effective field descriptor table (FDT). |
Action |
Recreate the Adabas PSTORE file. |
00210837 | ACI-CONVERSION requires ICU |
Explanation |
Attribute |
Action |
Correct the Broker attribute file. See |
00210838 | ACI-CONVERSION invalid CODEPAGE section |
Explanation |
Attribute |
Action |
Correct the Broker attribute file. See |
00210839 | ACI-CONVERSION failed, using translation |
Explanation |
The conversion failed due to an error. The translation is used to convert the data. |
Action |
Check the subsequent error messages and correct the error. |
00210840 | PSTORE-VERSION 4 or above required |
Explanation |
The DIV PSTORE requires PSTORE-VERSION 4 or above. |
Action |
Allocate a DIV PSTORE with following attributes:
|
00210843 | PSTORE: No records. Restart HOT failed |
Explanation |
No records in Adabas PSTORE. |
Action |
Define |
00210845 | PSTORE: Wrong platform detected |
Explanation |
The platform ID in the master record is wrong. This is probably a wrong database or the PSTORE of a different Broker. |
Action |
Check the |
00210846 | PSTORE: Mismatching BROKER-ID in PSTORE |
Explanation |
The |
Action |
Check the |
00210847 | PSTORE: Invalid BLKSIZE |
Explanation |
Attribute |
Action |
Enter the correct |