CMDTUX Messages 4700-4799

4700

ERROR: service-name received a badly formed message

Description

The event broker service service-name received a message that does not contain the necessary information.

Action

Contact BEA Customer Support.

See Also

TMSYSEVT, TMUSREVT

4701

ERROR: unable to decode or decrypt user data

Description

The TMUSREVT or TMSYSEVT may need to decode or decrypt messages for several reasons. If the broker does not have a proper decryption key, this message will be printed. Otherwise, there was a problem while attempting to decode the message, such as a message arriving with an unknown TYPE or SUBTYPE.

Action

The event broker can be configured to open a decryption key with the SEC_PRINCPIPAL_NAME, SEC_PRINCIPAL_LOCATION and SEC_PRINCIPAL_PASSVAR fields in the ubbconfig, or through the use of _ec_sec_pki_init plug-in.

See Also

TMSYSEVT, TMUSREVT, ubbconfig, _ec_sec_pki_init, MIB, TM_MIB

4702

WARN: Primary Event Server could not retrieve the MIB data

Description

A MIB request has been forwarded to the Primary Event Server. However, this request was encrypted, and the server does not have the proper decryption key to decrypt the message. Otherwise, there was a problem while attempting to decode the message.

Action

The event broker can be configured to open a decryption key with the SEC_PRINCPIPAL_NAME, SEC_PRINCIPAL_LOCATION and SEC_PRINCIPAL_PASSVAR fields in the ubbconfig, or through the use of _ec_sec_pki_init plug-in.

See Also

TMSYSEVT, TMUSREVT, ubbconfig, _ec_sec_pki_init, MIB, TM_MIB

4711

ERROR: Identifier for SEC_PRINCIPAL_NAME must be <= size characters in length

Description

The SEC_PRINCIPAL_NAME field in the RESOURCES section of the UBBCONFIG file must be less than or equal to size characters.

Action

Ensure that the field is less than size characters.

See Also

ubbconfig, tmloadcf, tmunloadcf

4713

ERROR: Identifier for SEC_PRINCIPAL_NAME must be <= size characters in length

Description

The SEC_PRINCIPAL_NAME field in the MACHINES section of the UBBCONFIG file must be less than or equal to size characters.

Action

Ensure that the field is less than size characters.

See Also

ubbconfig, tmloadcf, tmunloadcf

4715

ERROR: Identifier for SEC_PRINCIPAL_NAME must be <= size characters in length

Description

The SEC_PRINCIPAL_NAME field in the GROUPS section of the UBBCONFIG file must be less than or equal to size characters.

Action

Ensure that the field is less than size characters.

See Also

ubbconfig, tmloadcf, tmunloadcf

4717

ERROR: Identifier for SEC_PRINCIPAL_NAME must be <= size characters in length

Description

The SEC_PRINCIPAL_NAME field in the SERVERS section of the UBBCONFIG file must be less than or equal to size characters.

Action

Ensure that the field is less than size characters.

See Also

ubbconfig(5), tmloadcf(1), tmunloadcf(1) in BEA TUXEDO Reference.

4718

ERROR: Invalid message format

Description

The BBL received a message that does not contain the necessary information.

Action

Contact BEA Customer Support.

4719

ERROR: Invalid message format

Description

The BBL received a message that does not contain the necessary information.

Action

Contact BEA Customer Support.

4720

ERROR: Invalid message format

Description

The BBL received a message that does not contain the necessary information.

Action

Contact BEA Customer Support.

4721

ERROR: Memory allocation failure

Description

An attempt dynamically to allocate memory from the operating system using malloc() failed in buildclient on VMS while trying to allocate space to hold the compilation line.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine.

4722

ERROR: Memory allocation failure

Description

An attempt dynamically to allocate memory from the operating system using malloc() failed in buildclient on VMS while trying to allocate space to hold the COBOL compilation line.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine.

4723

ERROR: buildserver cannot open the temporary output file, srcfile.

Description

The buildserver command cannot open the temporary output file, srcfile on AS/400.

Action

Check that the directory for the file exists and has write permissions, and the file system has sufficient resources for a new file.

See Also

buildserver(1)

4724

ERROR: Could not become a background process

Description

Normally, the tlisten process starts as a background program automatically. The program could not be restarted in the background and will not run.

Action

Check for other messages in the event log. Determine if there is an OS resource that is exhausted and re-try the command when it is resolved.

See Also

tlisten(1)

4725

ERROR: Could not become a background process

Description

Normally, the tlisten process starts as a background program automatically. The program could not be restarted in the background and will not run.

Action

Check for other messages in the event log. Determine if there is an OS resource that is exhausted and re-try the command when it is resolved.

See Also

tlisten(1)

4726

ERROR: Unable to read RESOURCES section of TUXCONFIG file

Description

tmipcrm was unable to get information on the RESOURCES section from the TUXCONFIG file. Additional information from the userlog might indicate why the system was unable to do so. For example, the TUXCONFIG environment variable may not have been set.

Action

Please examine the userlog for further information. If necessary, please contact your BEA TUXEDO System Administrator.

4727

ERROR: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), val hour val minutes val seconds left before DBBL lockout occurs

Description

The system has determined that the total number of active users exceeded 110% of TUXEDO licensed users. DBBL lockout will occur in indicated time. When DBBL lockout occurs, no new clients can join the application until the overall active user count dips below 110% on a subsequent DBBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your BEA TUXEDO System Administrator.

4728

ERROR: .SysLicenseError: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), val hour val minutes val seconds left before DBBL lockout occurs

Description

The system has determined that the total number of active users exceeded 110% of TUXEDO licensed users. DBBL lockout will occur in indicated time. When DBBL lockout occurs, no new clients can join the application until the overall active user count dips below 110% on a subsequent DBBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your BEA TUXEDO System Administrator.

4729

WARN: Reached 100% of TUXEDO System Binary Licensed User Count (val/val)

Description

The system has determined that the total number of active users exceeded 100% of TUXEDO licensed users. DBBL lockout will occur if the total number of active users continues to increase.

Action

Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your BEA TUXEDO System Administrator.

4730

WARN: .SysLicenseWarn: Reached 100% of TUXEDO System Binary Licensed User Count (val/val)

Description

The system has determined that the total number of active users exceeded 100% of TUXEDO licensed users. DBBL lockout will occur if the total number of active users continues to increase.

Action

Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your BEA TUXEDO System Administrator.

4731

INFO: Reached 90% of TUXEDO System Binary Licensed User Count (val/val)

Description

The system has determined that the total number of active users exceeded 90% of TUXEDO licensed users. DBBL lockout will occur if the total number of active users continues to increase.

Action

Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your BEA TUXEDO System Administrator.

4732

INFO: .SysLicenseInfo: Reached 90% of TUXEDO System Binary Licensed User Count (val/val)

Description

The system has determined that the total number of active users exceeded 90% of TUXEDO licensed users. DBBL lockout will occur if the total number of active users continues to increase.

Action

Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your BEA TUXEDO System Administrator.

4733

ERROR: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout occurs, no new clients can join the application

Description

DBBL lockout occurs because the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users for a grace period of 24 hours. At this time, no new clients can join the application until the overall active user count dips below 110% on a subsequent DBBL scan cycle.

Action

Inform the active users to exit the application as soon as they finish to decrease the active user count, and upgrade your TUXEDO license with larger number of users to avoid future system lockouts. Please contact your BEA TUXEDO System Administrator.

4734

ERROR: .SysLicenseError: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout occurs, no new clients can join the application

Description

DBBL lockout occurs because the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users for a grace period of 24 hours. At this time, no new clients can join the application until the overall active user count dips below 110% on a subsequent DBBL scan cycle.

Action

Inform the active users to exit the application as soon as they finish to decrease the active user count, and upgrade your TUXEDO license with larger number of users to avoid future system lockouts. Please contact your BEA TUXEDO System Administrator.

4735

INFO: Reached 100% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout canceled

Description

The system has determined that the overall active user count has dipped down to 100% of TUXEDO licensed users during a DBBL lockout. The DBBL lockout is canceled on a subsequent DBBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4736

INFO: .SysLicenseInfo: Reached 100% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout canceled

Description

The system has determined that the overall active user count has dipped down to 100% of TUXEDO licensed users during a DBBL lockout. The DBBL lockout is canceled on a subsequent DBBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4737

INFO: Reached 90% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout canceled

Description

The system has determined that the overall active user count has dipped down to 90% of TUXEDO licensed users during a DBBL lockout. The DBBL lockout is canceled on a subsequent DBBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4738

INFO: .SysLicenseInfo: Reached 90% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout canceled

Description

The system has determined that the overall active user count has dipped down to 90% of TUXEDO licensed users during a DBBL lockout. The DBBL lockout is canceled on a subsequent DBBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4739

INFO: Reached below 90% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout canceled

Description

The system has determined that the overall active user count has dipped down below 90% of TUXEDO licensed users during a DBBL lockout. The DBBL lockout is canceled on a subsequent DBBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4740

INFO: .SysLicenseInfo: Reached below 90% of TUXEDO System Binary Licensed User Count (val/val), DBBL lockout canceled

Description

The system has determined that the overall active user count has dipped down below 90% of TUXEDO licensed users during a DBBL lockout. The DBBL lockout is canceled on a subsequent DBBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4741

ERROR: The DBBL could not format the O_LCKOUT message to all BBLs

Description

The DBBL lockout occurs because the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users for a grace period of 24 hours. However, the DBBL has a problem to format and broadcast a lockout message to all BBLs.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4742

ERROR: The DBBL could not format the O_UNLCKOUT message to all BBLs

Description

The DBBL lockout is canceled because the system has determined that the total number of active users dips below 110% of TUXEDO licensed users. However, the DBBL has a problem to format and broadcast a un-lockout message to all BBLs.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4743

ERROR: Exceeded 110% of TUXEDO System Binary License User Count, BBL received LOCKOUT notice, no new clients can join the application

Description

BBL received lockout notice from the DBBL because the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users for a grace period of 24 hours. At this time, no new clients can join the application until the overall active user count dips below 110% on a subsequent DBBL scan cycle.

Action

Inform the active users to exit the application as soon as they finish to decrease the active user count, and upgrade your TUXEDO license with larger number of users to avoid future system lockouts. Please contact your BEA TUXEDO System Administrator.

4744

INFO: BBL received LOCKOUT cancelation notice, new clients now can join the application

Description

The BBL received lockout cancelation notice from the DBBL because the system has determined that the total number of active users dips below 110% of TUXEDO licensed users. At this time, new clients can join the application.

Action

Upgrade your TUXEDO license with larger number of users to avoid future system lockouts. Please contact your BEA TUXEDO System Administrator.

4745

ERROR: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout occurs, no new clients can join the application

Description

The BBL lockout occurs in SHM mode because the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users for a grace period of 24 hours. At this time, no new clients can join the application until the overall active user count dips below 110% on a subsequent BBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4746

ERROR: .SysLicenseError: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout occurs, no new clients can join the application

Description

The BBL lockout occurs in SHM mode because the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users for a grace period of 24 hours. At this time, no new clients can join the application until the overall active user count dips below 110% on a subsequent BBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4747

ERROR: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), val hour val minutes val seconds left before BBL lockout occurs

Description

In SHM mode, the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users. The BBL lockout will occur in indicated time. When BBL lockout occurs, no new clients can join the application until the overall active user count dips below 110% on a subsequent BBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your BEA TUXEDO System Administrator.

4748

ERROR: .SysLicenseError: Exceeded 110% of TUXEDO System Binary Licensed User Count (val/val), val hour val minutes val seconds left before BBL lockout occurs

Description

In SHM mode, the system has determined that the total number of active users exceeded 110% of TUXEDO licensed users. The BBL lockout will occur in indicated time. When BBL lockout occurs, no new clients can join the application until the overall active user count dips below 110% on a subsequent BBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your BEA TUXEDO System Administrator.

4749

WARN: Reached 100% of TUXEDO System Binary Licensed User Count (val/val)

Description

In SHM mode, the system has determined that the total number of active users exceeded 100% of TUXEDO licensed users. The BBL lockout will occur if the total number of active users continues to increase.

Action

Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your BEA TUXEDO System Administrator.

4750

WARN: .SysLicenseWarn: Reached 100% of TUXEDO System Binary Licensed User Count (val/val)

Description

In SHM mode, the system has determined that the total number of active users exceeded 100% of TUXEDO licensed users. The BBL lockout will occur if the total number of active users continues to increase.

Action

Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your BEA TUXEDO System Administrator.

4751

INFO: Reached 100% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout canceled

Description

In SHM mode, the system has determined that the overall active user count has dipped down to 100% of TUXEDO licensed users during a BBL lockout. The BBL lockout is canceled on a subsequent BBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4752

INFO: .SysLicenseInfo: Reached 100% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout canceled

Description

In SHM mode, the system has determined that the overall active user count has dipped down to 100% of TUXEDO licensed users during a BBL lockout. The BBL lockout is canceled on a subsequent BBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4753

INFO: Reached 90% of TUXEDO System Binary Licensed User Count (val/val)

Description

In SHM mode, the system has determined that the total number of active users exceeded 90% of TUXEDO licensed users. DBBL lockout will occur if the total number of active users continues to increase.

Action

Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your BEA TUXEDO System Administrator.

4754

INFO: .SysLicenseInfo: Reached 90% of TUXEDO System Binary Licensed User Count (val/val)

Description

In SHM mode, the system has determined that the total number of active users exceeded 90% of TUXEDO licensed users. The BBL lockout will occur if the total number of active users continues to increase.

Action

Upgrade your TUXEDO license with larger number of users to avoid system lockouts. Please contact your BEA TUXEDO System Administrator.

4755

INFO: Reached 90% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout canceled

Description

In SHM mode, the system has determined that the overall active user count has dipped down to 90% of TUXEDO licensed users during a BBL lockout. The BBL lockout is canceled on a subsequent BBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4756

INFO: .SysLicenseInfo: Reached 90% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout canceled

Description

In SHM mode, the system has determined that the overall active user count has dipped down to 90% of TUXEDO licensed users during a BBL lockout. The BBL lockout is canceled on a subsequent BBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4757

INFO: Reached below 90% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout canceled

Description

In SHM mode, the system has determined that the overall active user count has dipped down below 90% of TUXEDO licensed users during a BBL lockout. The BBL lockout is canceled on a subsequent DBBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4758

INFO: .SysLicenseInfo: Reached below 90% of TUXEDO System Binary Licensed User Count (val/val), BBL lockout canceled

Description

In SHM mode, the system has determined that the overall active user count has dipped down below 90% of TUXEDO licensed users during a BBL lockout. The BBL lockout is canceled on a subsequent DBBL scan cycle.

Action

Upgrade your TUXEDO license with larger number of users to aviod future system lockouts. Please contact your BEA TUXEDO System Administrator.

4760

ERROR: -t option cannot be used on a platform which does not support threads

Description

The buildserver command was run with the -t option on a platorm that does not support threads. The -t option indicates that the servers are allowed to specify a multi-threading level and is not allowed on this platform.

Action

Re-run the command without the -t option.

See Also

buildserver(1)

4761

ERROR: the -t and -C options are mutually exclusive

Description

The buildserver command was run with both the -t (multi-threaded) and -C (COBOL) options. These options cannot be specified together (COBOL servers cannot be multi-threaded).

Action

Re-run the command without the -t or -C option.

See Also

buildserver(1)

4763

ERROR: -z (val) is larger than 56, but only the 56-bit package is installed

Description

In tlisten, an encryption level greater than 56-bit encryption was specified, but only 56-bit encryption is availble.

Action

Re-run the command with a lower encryption level or install the higher encryption level.

See Also

tlisten

4764

ERROR: Minimum encryption (val) is larger than 56, but only the 56-bit package is installed

Description

In the BRIDGE, an encryption level greater than 56-bit encryption was specified, but only 56-bit encryption is availble.

Action

Re-configure the link level encryption with a lower encryption level or install the higher encryption level. The encryption level is specified using the MINENCRYPTBITS parameter on the NETWORK entry.

See Also

ubbconfig(5)

4765

ERROR: MAXENCRYPTBITS parameter must be 0, 40, 56 or 128

Description

The MAXENCRYPTBITS parameter on the NETWORK entry must have a value of 0, 40, 56, or 128 depending on the desired number of bits encryption and the encryption level installed.

Action

Re-configure the parameter and reload the configuration.

See Also

ubbconfig(5)

4766

ERROR: Cannot open file filename for writing

Description

The event server couldn't open file filename for writing the subscription database.

Action

The event server writes a new copy of the subscription database in the temporary file file. Then, it links this file to the control file specified in the UBBCONFIG file. This message indicates that the server couldn't open the temporary file for writing. Check the file system parameters and take corrective action.

4767

ERROR: Couldn't initialize the allocated memory as a fielded buffer, Ferror32=error

Description

While processing a deletion record, the event server was unable to initialize an FML32 buffer. The Ferror32 error value is printed.

Action

Contact BEA Customer Support.

4768

ERROR: Cannot write FML32 buffer in file val, Ferror32=error

Description

While processing a deletion record, the event server was unable to write out an FML32 buffer. The Ferror32 error value is printed.

Action

Check the FML32 error. Most likely it is related to insufficient resources in the file system. Fix the problem and re-run the operation.

4769

ERROR: Invalid database version received from Secondary Server

Description

A Secondary event server sends a message to the primary requesting a event database version that is not recognized.

Action

Contact BEA Customer Support.

4770

ERROR: Could not determine size of fielded buffer, Ferror32=error

Description

The event server, while trying to expand an FML32 buffer, was unable to determine the buffer size. The Ferror32 error value is printed.

Action

Contact BEA Customer Support.

4771

ERROR: MINDISPATCHTHREADS must be <= MAXDISPATCHTHREADS

Description

SERVERS entry was read where the MINDISPATCHTHREADS parameter was greater than the MAXDISPATCHTHREADS parameter.

Action

Correct the entry and re-load the configuration.

See Also

tmloadcf(1), ubbconfig(5)

4772

WARN: MAXDISPATCHTHREADS > system max, changing to val

Description

SERVERS entry was read where the MAXDISPATCHTHREADS parameter is greater than the maximum allowed value. The value will be changed to that maximum, val.

Action

No action required.

See Also

tmloadcf(1), ubbconfig(5)

4774

ERROR: SIGNATURE_AHEAD parameter must be > 0 and < 2147483647.

Description

The SIGNATURE_AHEAD parameter in the RESOURCES section of the configuration file must be within the proper range of values.

Action

Specify a value that is between 1 and 2,147,483,646, inclusive.

See Also

tmloadcf(1), ubbconfig(5)

4776

ERROR: SIGNATURE_BEHIND parameter must be > 0 and < 2147483647.

Description

The SIGNATURE_BEHIND parameter in the RESOURCES section of the configuration file must be within the proper range of values.

Action

Specify a value that is between 1 and 2,147,483,646, inclusive.

See Also

tmloadcf(1), ubbconfig(5)

4777

ERROR: -z(val) must be 0, 40, 56 or 128

Description

The argument for the -z option of tlisten must have a value of 0, 40, 56, or 128 depending on the desired number of bits encryption and the encryption level installed.

Action

Re-configure the argument and re-run the command.

See Also

tlisten(1)

4778

ERROR: -Z(val) must be 0, 40, 56 or 128

Description

The argument for the -Z option of tlisten must have a value of 0, 40, 56, or 128 depending on the desired number of bits encryption and the encryption level installed.

Action

Re-configure the argument and re-run the command.

See Also

tlisten(1)

4780

ERROR: 56-bit package installed. val bits minimum encryption is configured

Description

In tlisten while trying to establish a connection to a remote note, an encryption level greater than 56-bit encryption was specified, but only 56-bit encryption is available.

Action

Re-configure the link level encryption with a lower encryption level for the remote node or install the higher encryption level. The encryption level is specified using the MINENCRYPTBITS parameter on the NETWORK entry.

See Also

ubbconfig(5)

4782

ERROR: MINENCRYPTBITS parameter must be 0, 40, 56 or 128

Description

The value of MINENCRYPTBITS parameter on the NETWORK entry must have a value of 0, 40, 56, or 128 depending on the desired number of bits encryption and the encryption level installed.

Action

Re-configure the parameter and re-load the configuration.

See Also

ubbconfig(5)

4784

WARN: Minimum encryption (val) is larger than 56, but only the 56-bit package is installed

Description

In the BRIDGE, an encryption level greater than 56-bit encryption was specified, but only 56-bit encryption is availble.

Action

Re-configure the link level encryption with a lower encryption level or install the higher encryption level. The encryption level is specified using the MINENCRYPTBITS parameter on the NETWORK entry.

See Also

ubbconfig(5)

4786

ERROR: Couldn't initialize the allocated memory as a fielded buffer, Ferror32=val

Description

While processing a database version record, the event server was unable to initialize an FML32 buffer. The Ferror32 error value is printed.

Action

Contact BEA Customer Support.

4788

ERROR: Cannot write FML32 buffer in file val, Ferror32=val

Description

While processing a database version record, the event server was unable to write out an FML32 buffer. The Ferror32 error value is printed.

Action

Check the FML32 error. Most likely it is related to insufficient resources in the file system. Fix the problem and re-run the operation.

4790

ERROR: Primary Server can't unload subscription database into a file

Description

The primary event server was unable to unload the subscription database into a file.

Action

Check the log for earlier messages indicating the exact nature of the problem.

4792

ERROR: Secondary Server can't set database version in the FML buffer. Ferror=val

Description

The secondary event server can't add CURSID to FML buffer.

Action

When the secondary event server polls the primary server for subscription database, it sends its version. This message states that the secondary server couldn't insert the version field to FML buffer. Contact BEA Customer Support, and provide the Ferror errno.

See Also

Fchg(3fml)

4794

ERROR: Could not realloc fielded buffer, Ferror32=val

Description

The event server, while trying to expand an FML32 buffer, was unable to determine the buffer size. The Ferror32 error value is printed.

Action

Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine.

4795

WARN: Job Description not found. Using default job attributes

Description

The AS/400 Job Description for the BBL could not be found in the Job Description file AS400_JD. The default job attributes will be used.

Action

Check for the presence of the AS400_JD file in the udataobj directory. If present, check to see that the AS400_JD file contains an entry for the BBL.

4796

WARN: Failure changing job attributes. Using default attributes

Description

The job attributes for the BBL could not be set according to the Job Description in the AS400_JD file. The default job attributes will be used.

Action

Check the job log for the BBL to determine the cause of the failure.

4797

WARN: Job Description not found. Using default job attributes

Description

The AS/400 Job Description for the DBBL could not be found in the Job Description file AS400_JD. The default job attributes will be used.

Action

Check for the presence of the AS400_JD file in the udataobj directory. If present, check to see that the AS400_JD file contains an entry for the DBBL.

4798

WARN: Failure changing job attributes. Using default attributes

Description

The job attributes for the DBBL could not be set according to the Job Description in the AS400_JD file. The default job attributes will be used.

Action

Check the job log for the BBL to determine the cause of the failure.

4799

WARN: Job Description not found. Using default job attributes

Description

The AS/400 Job Description for the BRIDGE could not be found in the Job Description file AS400_JD. The default job attributes will be used.

Action

Check for the presence of the AS400_JD file in the udataobj directory. If present, check to see that the AS400_JD file contains an entry for the BRIDGE.