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

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

Overview of Messages

00210013 | 00210014 | 00210015 | 00210016 | 00210017 | 00210018 | 00210023 | 00210024 | 00210025 | 00210026 | 00210027 | 00210028 | 00210029 | 00210030 | 00210032 | 00210033 | 00210034 | 00210035 | 00210036 | 00210037 | 00210038 | 00210040 | 00210043 | 00210045 | 00210059 | 00210080 | 00210096 | 00210269 | 00210368 | 00210402 | 00210423 | 00210431 | 00210446 | 00210447 | 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:

  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.

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 NUM-CLIENT (or if CLIENT-NONACT has too high a value, decrease it) in the Broker attribute file.


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 NUM-SERVER (or if SERVER-NONACT has too high a value for some services, decrease it) in the Broker attribute file.


00210023 Unknown Keyword
Explanation

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.

Action

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


00210024 CONV-LIMIT may not be UNLIM
Explanation

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.

Action

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


00210025 CONV-DEFAULT not spec or UNLIM
Explanation

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.

Action

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.


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:

  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.

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:

  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.

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:

  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.

Action

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


00210029 SHORT-BUFF-LIMIT may not be UNLIM
Explanation

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.

Action

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


00210030 SHORT-BUFF-DEF not spec or UNLIM
Explanation

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.

Action

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.


00210032 LONG-BUFF-LIMIT may not be UNLIM
Explanation

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.

Action

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


00210033 LONG-BUFF-DEF not spec or UNLIM
Explanation

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

Action

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.


00210034 SERVICE Section missing
Explanation

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

Action

Correct the attribute file and provide a valid DEFAULTS=SERVICE section. See Service-specific Attributes.


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:

  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.

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

  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.

Action

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.


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:

  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.

Action

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.


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 CLASS, SERVER and SERVICE fields in the API, or make sure the service definition in the Broker attribute file is valid.


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:

  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.

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 NUM-SERVICE attribute in the section DEFAULTS=BROKER in the Broker attribute file.


00210269 PSTORE required
Explanation

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

Action

Contact your Broker Administrator.


00210368 No host:port value specified
Explanation

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

Action

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


00210402 SECURITY/ENCRYPTION-LEVEL mismatch
Explanation

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

Action

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.

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 (CLASS= *, SERVER= *, SERVICE = *) then the value of AUTO is not allowed for the NUM-CONVERSATION, NUM-LONG-BUFFER or NUM-SHORT-BUFFER attributes.

Action

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


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

Action

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


00210447 ATTR: SERVER-DEFAULT not spec or UNLIM
Explanation

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.

Action

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.


00210501 TCP-PORT numbers not unique
Explanation

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

Action

Specify a different PORT number.


00210547 Max num AUTHORIZATION-RULE reached
Explanation

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

Action

Reduce the number of AUTHORIZATION-RULE entries.


00210548 Max num HOST entries reached
Explanation

You cannot specify more than five HOST entries per section.

Action

Reduce number of HOST entries.


00210549 Max num PORT entries reached
Explanation

You cannot specify more than five PORT entries per section.

Action

Reduce number of PORT entries.


00210559 ATTR: TRANSPORT = NET and NUM-CCOM = 0
Explanation

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

Action

Set NUM-CCOM=1, or higher.


00210564 SSL-PORT numbers not unique
Explanation

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

Action

Specify a different PORT number.


00210568 Max num STACK-NAME entries reached
Explanation

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

Action

Reduce number of STACK-NAME entries.


00210591 DEFAULTS section missing
Explanation

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

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 PARTNER-CLUSTER-ADDRESS.

Action

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


00210628 Expect PSTORE=HOT in STANDBY mode
Explanation

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

Action

Define PSTORE=HOT for your Standby Broker.


00210629 Expect PSTORE=COLD in LOAD mode
Explanation

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

Note:
RUN-MODE options PSTORE-LOAD and PSTORE-UNLOAD are deprecated and will not be supported in the next version of EntireX.

Action

Define PSTORE=COLD for your Load Broker.


00210630 Expect PSTORE=HOT in UNLOAD mode
Explanation

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

Action

Define PSTORE=HOT for your Unload Broker.


00210652 Invalid keyword in TRANSLATION parms
Explanation

The attribute TRANSLATION contains an invalid parameter.

Action

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


00210703 Missing attribute TRUST-STORE
Explanation

Attribute TRUST-STORE in the SSL section is missing.

Action

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


00210704 TRUST-STORE does not exist
Explanation

The specified file for TRUST-STORE does not exist.

Action

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


00210705 Missing attribute KEY-STORE
Explanation

Attribute KEY-STORE in the SSL section is missing.

Action

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


00210706 KEY-STORE does not exist
Explanation

The specified file for KEY-STORE does not exist.

Action

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


00210707 Missing attribute KEY-FILE
Explanation

Attribute KEY-FILE in the SSL section is missing.

Action

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


00210708 KEY-FILE does not exist
Explanation

The specified file for KEY-FILE does not exist.

Action

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


00210709 KEY-FILE specified but no KEY-PASSWD
Explanation

No KEY-PASSWD has been specified.

Action

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

Note:
KEY-PASSWD is deprecated. We recommend using KEY-PASSWD-ENCRYPTED instead. See KEY-PASSWD-ENCRYPTED under SSL-specific Broker Attributes.


00210710 VERIFY-CLIENT=YES but no TRUST-STORE
Explanation

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

Action

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


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 DYNAMIC-WORKER-MANAGEMENT=YES and restart Broker. See DYNAMIC-WORKER-MANAGEMENT under Broker-specific Broker Attributes.


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 STORE in section DEFAULTS=DIV was not specified.

Action

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


00210723 DIV: DDNAME not specified
Explanation

Attribute DDNAME in section DEFAULTS=DIV was not specified.

Action

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


00210727 c-tree PATH does not exist
Explanation

The directory specified as value of PATH does not exist.

Action

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


00210740 PSTORE requires higher PSTORE-VERSION
Explanation

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

Action

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.


00210741 PSTORE requires lower PSTORE-VERSION
Explanation

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

Action

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.


00210760 PARTNER-CLUSTER-ADDRESS mismatch
Explanation

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.

Action

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


00210761 PARTNER-CLUSTER-ADDRESS missing
Explanation

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

Action

Define PARTNER-CLUSTER-ADDRESS in the Standard Broker to allow running a Standby Broker. See PARTNER-CLUSTER-ADDRESS under Broker-specific Broker Attributes.


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 PSTORE-TYPE and the PSTORE specific sections in each Broker attribute file so both Broker instances match. See PSTORE-TYPE under Broker-specific Broker Attributes.


00210763 PSTORE-TYPE missing
Explanation

There is no PSTORE defined in the partner Broker instance. See PSTORE-TYPE under Broker-specific Broker Attributes.

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 PSTORE-TYPE and the PSTORE specific sections for both Broker instances. Make sure the Load Broker is assigned to a new persistent store, and our Unload Broker is assigned to the persistent store you wish to unload.


00210796 Adabas SVC number must be supplied
Explanation

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

Action

Specify SVC=svc_number used by the Adabas PSTORE database.


00210797 ADABAS DBID and FNR must be supplied
Explanation

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

Action

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


00210798 Invalid BLKSIZE (range 126-20000 bytes)
Explanation

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

Action

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


00210827 LDAP: Missing LDAP-AUTHORIZATION-URL
Explanation

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

Action

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


00210829 PSTORE: Max MU 191 exceeded
Explanation

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

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 MAXSCAN exceeded.

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 ACI-CONVERSION=YES requires attribute ICU-CONVERSION=YES.

Action

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


00210838 ACI-CONVERSION invalid CODEPAGE section
Explanation

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

Action

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


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:

PSTORE=COLD
PSTORE-TYPE=DIV
PSTORE-VERSION=5


00210843 PSTORE: No records. Restart HOT failed
Explanation

No records in Adabas PSTORE.

Action

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


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 DEFAULTS=ADABAS settings.


00210846 PSTORE: Mismatching BROKER-ID in PSTORE
Explanation

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.

Action

Check the DEFAULTS=ADABAS settings.


00210847 PSTORE: Invalid BLKSIZE
Explanation

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

Action

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