HPlogo ALLBASE/SQL Message Manual: HP 3000 MPE/iX Computer Systems

Chapter 10 ALLBASE/SQL Error Messages: 22800-

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

22800
MESSAGE

DBEnvironment has already been started (DBERR 22800)

CAUSE

A REPAIR command was in progress when this message was issued. Another user is currently accessing the DBEnvironment. The REPAIR command may only be issued when the database is idle.

ACTION

Please try again later.

23005
MESSAGE

START DBE NEWLOG disallowed. Need rollforward recovery. (DBERR 23005)

CAUSE

SQLMIG cannot be used on a DBEnvironment that has incomplete transactions in its log. You probably did not follow the steps required for forward migration, which are documented in the "DBA Tasks and Tools" chapter of the ALLBASE/SQL Database Administration Guide.

ACTION

Restore the old version of the operating system and the old version of ISQL onto your machine. Run the old version of ISQL and issue a START DBE statement to resolve the incomplete transactions in the log.

26002
MESSAGE

No matching profile found in the NETUsers file. (DBERR 26002)

CAUSE

ALLBASE/SQL attempted to connect to a remote DBEnvironment. Two error messages may be displayed. This is the second message and indicates that the NETUser profile either does not exist or was entered incorrectly in the NETUsers file.

ACTION

Add the NETUser name to the NETUsers file or use the SHOW USER command to check for correct spelling of NETUser names in the NETUsers file.

26003
MESSAGE

New value(s) already exists in NETUsers file, operation not performed. (DBERR 26003)

CAUSE

The NETUser name you specified is already in the NETUsers file.

ACTION

Enter a unique NETUser name.

26004
MESSAGE

``Lock on NETUsers file failed. (! !) (DBERR 26004)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

26005
MESSAGE

``Unlock on NETUsers file failed. (! !) (DBERR 26005)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

26006
MESSAGE

``Read failed on NETUsers file. (! !) (DBERR 26006)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

26007
MESSAGE

``Write failed on NETUsers file. (! !) (DBERR 26007)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

26008
MESSAGE

File system error on NETUsers file. (! !) (DBERR 26008)

CAUSE

ALLBASE/SQL attempted to connect to a remote DBEnvironment. Two error messages may be displayed. This is the second message and indicates that there is no NETUsers file or that the permissions are not set correctly.

ACTION

If the DBEnvironment you want to connect to is on the local node, check the spelling of the DBEnvironment name. If the DBEnvironment you want to connect to is on a remote node, have the system administrator set up the NETUsers file.

26009
MESSAGE

The NETUsers file is empty. (DBERR 26009)

CAUSE

You tried to "show" profiles in an empty NETUsers file. Profiles in the NETUsers file have been deleted.

ACTION

Contact the system administrator to add profiles to the NETUsers file.

26010
MESSAGE

``Open failed on temporary NETUsers file. (! !) (DBERR 26010)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

26011
MESSAGE

``Write failed on temporary NETUsers file. (! !) (DBERR 26011)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

26012
MESSAGE

Insufficient memory to allocate buffer. (DBERR 26012)

CAUSE

There is not enough memory to allocate buffer space for a new profile.

ACTION

Do not complete the operation. Record as much information as possible and contact your HP Service Representative or Response Center.

26013
MESSAGE

The NETUsers file is being accessed. Operation could not be performed. (DBERR 26013)

CAUSE

The NETUsers file is currently open by someone else and cannot be deleted.

ACTION

Try again later.

27002
MESSAGE

No matching profile found in the AliasDB file. (DBERR 27002)

CAUSE

ALLBASE/SQL attempted to connect to a remote DBEnvironment. Two error messages may be displayed. This is the second message and indicates that the alias profile either does not exist or was entered incorrectly in the AliasDB file. If this is the only error message returned, you are using a diskless machine to access a DBEnvironment on another machine.

ACTION

Ask the system administrator to enter an alias profile in the AliasDB file or check the spelling of the DBEnvironment name in the AliasDB file. For more information on configuring ALLBASE/NET in order to access a remote DBEnvironment, refer to the ALLBASE/NET User's Guide

27003
MESSAGE

New value(s) already exists in AliasDB file, operation not performed. (DBERR 27003)

CAUSE

The alias name which you are trying to add or change already exists in the AliasDB file.

ACTION

Enter a unique alias name.

27004
MESSAGE

Lock on AliasDB file failed. (! !) (DBERR 27004)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

27005
MESSAGE

Unlock on AliasDB file failed. (! !) (DBERR 27005)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

27006
MESSAGE

Read failed on AliasDB file. (! !) (DBERR 27006)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

27007
MESSAGE

Write failed on AliasDB file. (! !) (DBERR 27007)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

27008
MESSAGE

File system error on AliasDB file. (! !) (DBERR 27008)

CAUSE

ALLBASE/SQL attempted to connect to a remote DBEnvironment. Two error messages may be displayed. This is the second message and indicates that there is no AliasDB file or that the permissions are not set correctly.

ACTION

If the DBEnvironment you want to connect to is on the local node, check the spelling of the DBEnvironment name. If the DBEnvironment you want to connect to is on a remote node, have the system administrator set up the AliasDB file.

27009
MESSAGE

The AliasDB file is empty. (DBERR 27009)

CAUSE

You tried to "show" profiles from an empty AliasDB file. Profiles in the AliasDB file have been deleted.

ACTION

Contact the system administrator.

27010
MESSAGE

Open failed on temporary AliasDB file. (! !) (DBERR 27010)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

27011
MESSAGE

Write failed on temporary AliasDB file. (! !) (DBERR 27011)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

28001
MESSAGE

Invalid NETUtil command. (DBERR 28001)

CAUSE

An invalid command was entered.

ACTION

Type HELP for a list of valid NETUtil commands.

28002
MESSAGE

Insufficient capability, command disallowed. (DBERR 28002)

CAUSE

You must be MANAGER.SYS or have SM capability to execute this command. Users with AM capability can execute ADD ALIAS, CHANGE ALIAS, DELETE ALIAS, ADD USER, CHANGE USER, DELETE USER, and SHOW USER commands on user and alias profiles within their accounts. Users without SM or AM capability, or who are not MANAGER.SYS can use only the EXIT, HELP, QUIT, SHOW ALIAS, and SYSTEM commands.

ACTION

Ask the system administrator to execute the command.

28003
MESSAGE

Open failed on NETUsers file. (! !) (DBERR 28003)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

28004
MESSAGE

Open failed on AliasDB file. (! !) (DBERR 28004)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

28005
MESSAGE

Backup failed on NETUsers file. (! !) (DBERR 28005)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

28006
MESSAGE

Backup failed on AliasDB file. (! !) (DBERR 28006)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

28007
MESSAGE

Read failed on message catalog. (! !) (DBERR 28007)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1 for an error description.

28008
MESSAGE

Invalid Machine Type. (! !) (DBERR 28008)

CAUSE

An invalid machine type was entered. Valid machine types are HP 3000 S900, HP 9000 S800, or HP 9000 S300.

ACTION

Re-enter the machine type.

28009
MESSAGE

Invalid Datacom Type. (DBERR 28009)

CAUSE

You entered an invalid data communication type. The data communication type must be NS or ARPA.

ACTION

Re-enter the data communication type.

28010
MESSAGE

Invalid Database Server Type. (DBERR 28010)

CAUSE

You entered an invalid database management system type. Currently, the only valid database management system is ALLBASE/SQL.

ACTION

Re-enter the database management system type.

28011
MESSAGE

The AliasDB file has not been created. (DBERR 28011)

CAUSE

The AliasDB file does not exist.

ACTION

Ask the system administrator to use the ADD ALIAS command to create the AliasDB file.

28012
MESSAGE

Name cannot start with the wildcard character. (DBERR 28012)

CAUSE

You tried to add a name to the AliasDB file or NETUsers file beginning with an '*'.

ACTION

Re-enter the AliasName or NETUser name without the wildcard character.

28013
MESSAGE

DB2 Connection Type must be G. (DBERR 28013)

CAUSE

You attempted to enter a DB2 Connection Type in the AliasDB file that is not supported.

ACTION

Enter the DB2 connection type again. The valid DB2 connection type at this time is LU6.2.

28014
MESSAGE

Invalid CICS Transaction Type. (DBERR 28014)

CAUSE

You attempted to enter a CICS Transaction Type in the AliasDB file that does not conform to the edit specifications for this field.

ACTION

Enter the CICS Transaction Type again. Valid CICS transaction types start with a letter and are 4 characters long.

28015
MESSAGE

Invalid LU6.2 Time Out Value. (DBERR 28015)

CAUSE

You attempted to enter an LU6.2 time out value that is not in the range.

ACTION

Enter the LU6.2 Time Out Value again. Valid LU6.2 time out values are in the range 0 to 28800. 0 implies no time outs.

28016
MESSAGE

Invalid HP Session Type. (DBERR 28016)

CAUSE

You entered an HP LU6.2 API Session Type in the AliasDB file entry that does not conform to the edit specifications for this field.

ACTION

Enter the HP Session Type again. Valid HP Session Types are up to 8 characters long.

28017
MESSAGE

Invalid Length. (DBERR 28017)

CAUSE

You entered data in the AliasDB file entry that does not conform to the edit specifications for this field.

ACTION

Enter the length specification again. Valid lengths are integers greater than zero.

28018
MESSAGE

LU6.2 Trace Flag must be 0, 1, 2, or 3. (DBERR 28018)

CAUSE

You entered an HP LU6.2 API trace flag value that is not supported.

ACTION

Enter the LU6.2 Trace Flag again. Valid values for this flag are 0, 1, 2, or 3.

28019
MESSAGE

Name is too long. (DBERR 28019)

CAUSE

You entered a DBEnvironment name, node name or login name in the AliasDB or NETUsers file which was too long.

ACTION

Enter the name again. The maximum length for a DBEnvironment name is 128 bytes; the maximum length for a node name is 256 bytes; and the maximum length for a login name is 56 bytes.

28021
MESSAGE

Database server type must be ALLBASE/SQL or DB2. (DBERR 28021)

CAUSE

You entered an invalid database server type.

ACTION

Re-enter a valid database server type.

28022
MESSAGE

Machine type must be HP9000 {S300, S400, S700 or S800} or HP3000 S9000. S900. (DBERR 28022)

CAUSE

You entered an invalid machine type.

ACTION

Re-enter a valid machine type.

28023
MESSAGE

Machine type must be IBM. (DBERR 28023)

CAUSE

You entered an invalid machine type.

ACTION

Re-enter a valid machine type.

28024
MESSAGE

Datacomm type must be ARPA or NS. (DBERR 28024)

CAUSE

You entered an invalid datacomm type.

ACTION

Re-enter a valid datacomm type.

28025
MESSAGE

Datacomm type must be LU6.2. (DBERR 28025)

CAUSE

You entered an invalid datacomm type.

ACTION

Re-enter a valid datacomm type.

28030
MESSAGE

Cannot migrate NETUsers file backward. (DBERR 28030)

CAUSE

No previous migration of NETUsers file has occurred.

ACTION

No action is necessary.

28031
MESSAGE

Cannot migrate AliasDB file backward. (DBERR 28031)

CAUSE

No previous migration of AliasDB file has occurred.

ACTION

No action is necessary.

28032
MESSAGE

Cannot migrate client login (!) for client node name (!). (DBERR 28032)

CAUSE

An error occurred attempting to migrate client profile.

ACTION

Check previous error message, which indicates where error occurred during migration.

28033
MESSAGE

Open failed on log file. (! !) (DBERR 28033)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

28034
MESSAGE

Lock failed on log file. (! !) (DBERR 28034)

CAUSE

An MPE iX file system error occurred.

ACTION

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

28035
MESSAGE

Unlock failed on log file. (! !) (DBERR 28035)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

28036
MESSAGE

Write failed on log file. (! !) (DBERR 28036)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

28037
MESSAGE

Open failed on server list file. (! !) (DBERR 28037)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

28038
MESSAGE

Lock failed on server list file. (! !) (DBERR 28038)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

28039
MESSAGE

Unlock failed on server list file. (! !) (DBERR 28039)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

28040
MESSAGE

Write failed on server list file. (! !) (DBERR 28040)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

28041
MESSAGE

Backup failed (! !) on file !. (DBERR 28041)

CAUSE

An MPE/iX file system error occurred.

ACTION

Refer to the MPE/iX Error Messages Manual, Volume I for an error description.

29001
MESSAGE

Invalid message type received. (DBERR 29001)

CAUSE

An internal error occurred. The client node or the server node received an invalid message type.

ACTION

Contact your HP Service Representative or Response Center.

29002
MESSAGE

Insufficient memory to allocate buffer for message. (DBERR 29002)

CAUSE

There is not enough memory to allocate a buffer for the outgoing message.

ACTION

Try again later.

29003
MESSAGE

CONNECT or START DBE command expected. (DBERR 29003)

CAUSE

A CONNECT or START DBE statement is expected.

ACTION

Add the appropriate statement to the application.

29004
MESSAGE

The ALLBASE/SQL and ALLBASE/NET software on the server machine are older than the ALLBASE/SQL and ALLBASE/NET software on the client machine. (DBERR 29004)

CAUSE

You are running incompatible releases of ALLBASE/SQL and ALLBASE/NET on the client and server machines.

ACTION

Ensure that the release of ALLBASE/NET and ALLBASE/SQL on your client node is not more recent than the software on the server node.

29010
MESSAGE

Invalid SQLX message buffer pointer. (DBERR 29010)

CAUSE

An ALLBASE/SQL internal error was encountered.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

29011
MESSAGE

Unsupported remote command. (DBERR 29011)

CAUSE

The command is not supported by ALLBASE/NET.

ACTION

Refer to the ALLBASE/NET User's Guide for a list of supported commands.

29440
MESSAGE

Incorrect machine type in AliasDB file. (DBERR 29440)

CAUSE

You are trying to access an HP3000 system but your AliasDB file specified an HP 9000 system.

ACTION

Change the machine type field of the AliasDB file profile to "HP 3000 S900."

30000
MESSAGE

Datacommunication NS failure. NetIPC Error Code (!). (DBERR 30000)

CAUSE

NetIPC returned an error. Some NetIPC errors which have been mapped to DBERRs are listed here:

30004 NetIPC Error:  Network transport not initialized.  (DBERR 30004)
 
30009 NetIPC Error:  Protocol is not active.  (DBERR 30009)
 
30015 NetIPC Error:  Attempt to exceed limit of sockets per process. (DBERR 30015)
 
30016 NetIPC Error:  Out of path descriptors or extensions.  (DBERR 30016)
 
30031 NetIPC Error:  Duplicate socket name.  (DBERR 30031)
 
30036 NetIPC Error:  Table of names is full.  (DBERR 30036)
 
30037 NetIPC Error:  Socket name not found.  (DBERR 30037)
 
30040 NetIPC Error:  Unknown node.  (DBERR 30040)
 
30043 NetIPC Error:  Unable to contact remote registry server.  (DBERR 30043)
 
30044 NetIPC Error:  No response from remote registry server.  (DBERR 30044)
 
30055 NetIPC Error:  Exceeded socket limit.  (DBERR 30055)
 
30059 NetIPC Error:  Socket timeout.  (DBERR 30059)
 
30064 NetIPC Error:  Remote protocol module aborted connection.  (DBERR 30064)
 
30065 NetIPC Error:  Local protocol module aborted connection.  (DBERR 30065)
 
30067 NetIPC Error:  Connection failure detected.  (DBERR 30067)
 
30068 NetIPC Error:  Received graceful release of connection.  (DBERR 30068)
 
30110 NetIPC Error:  Unanticipated protocol error.  (DBERR 30110)
 
30116 NetIPC Error:  Destination unreachable.  (DBERR 30116)
 
30117 NetIPC Error:  Attempt to establish connection failed.  (DBERR 30117)
 
30118 NetIPC Error:  Incompatible version.  (DBERR 30118)
 
30131 NetIPC Error:  Protocol module does not have sufficient resources. (DBERR 30131)
 
30158 NetIPC Error:  Connection request rejected by remote.  (DBERR 30158)
ACTION

Refer to the NetIPC Error Codes in the HP 9000 NetIPC Programmer's Guide.

31000
MESSAGE

Datacommunication BSD failure. (DBERR 31000)

CAUSE

A data communication error occurred.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31004
MESSAGE

The connect sequence was interrupted before completion. (DBERR 31004)

CAUSE

The connect sequence could not be completed.

ACTION

Restart the application.

31009
MESSAGE

Invalid virtual circuit descriptor. (DBERR 31009)

CAUSE

An internal error occurred. The internal virtual circuit descriptor is not the one from the successful connect call.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31014
MESSAGE

Invalid data pointer specified in ARPA sockets call. (DBERR 31014)

CAUSE

An internal error occurred.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31022
MESSAGE

Invalid parameter specified in ARPA sockets call. (DBERR 31022)

CAUSE

An internal error occurred.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31023
MESSAGE

The system's table of open files is full. (DBERR 31023)

CAUSE

The socket call cannot be accepted because the system's table is full.

ACTION

Try to connect again later.

31024
MESSAGE

The peer-process descriptor table is full. (DBERR 31024)

CAUSE

The socket call cannot be accepted because the application's open file exceeds the per-process limit.

ACTION

Close some files, then try to connect again.

31032
MESSAGE

The send cannot be completed, because the connection has been shutdown either by the remote peer or by the client process. (DBERR 31032)

CAUSE

A data communication error occurred or the peer process does not exist.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31216
MESSAGE

The virtual circuit descriptor is a file, not a socket. (DBERR 31216)

CAUSE

An internal error occurred.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31219
MESSAGE

The type of socket and protocol do not match. (DBERR 31219)

CAUSE

An internal error occurred.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31221
MESSAGE

The specified protocol is not supported. (DBERR 31221)

CAUSE

An internal error occurred.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31222
MESSAGE

The specified socket type is not supported. (DBERR 31222)

CAUSE

An internal error occurred.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31223
MESSAGE

ARPA network services have not been installed on this system. (DBERR 31223)

CAUSE

An attempt has been made to access a remote database from a system where networking services have not been installed.

ACTION

Install networking services on the system.

31225
MESSAGE

The specified address family is not supported. (DBERR 31225)

CAUSE

An internal error occurred.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31226
MESSAGE

The address is already in use. (DBERR 31226)

CAUSE

You tried to start the listener daemon, but it has already been started.

ACTION

No action necessary.

31227
MESSAGE

The specified address is not available. (DBERR 31227)

CAUSE

The HOSTS.NET.SYS file is not set up correctly or there is a datacomm error.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31229
MESSAGE

The network cannot be reached from this host. (DBERR 31229)

CAUSE

The network has not been set up.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31232
MESSAGE

The connection was reset by peer process. (DBERR 31232)

CAUSE

A data communication error occurred or the peer process was terminated.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31233
MESSAGE

Insufficient resources available to complete socket operation. (DBERR 31233)

CAUSE

The cause depends on which ARPA sockets function called failed. However, this error is an indication that there are not enough system resources available to complete the system call.

ACTION

Try again later.

31235
MESSAGE

The socket is not connected or the socket has not completed the connect sequence with its peer. (DBERR 31235)

CAUSE

The application ignored the error message from the connect call and continued to run the application which caused the internal usage of the descriptor from the failed call.

ACTION

Check the application error messages. Try to connect after correcting the error.

31238
MESSAGE

The connection timed out due to a transmission timeout. (DBERR 31238)

CAUSE

Internal timeout reached.

ACTION

Try to connect again.

31239
MESSAGE

The attempt to connect to a remote system was rejected. (DBERR 31239)

CAUSE

An internal error occurred. The listener daemon is down.

ACTION

Remove the tmp/hpdaARPA.log or the tmp/hpdaNS.log file and restart the listener daemon. Verify that the ARPA listener is running. Refer to the ALLBASE/NET User's Guide for more information. If this does not solve the problem, record as much information as possible and contact your HP Service Representative or Response Center.

31241
MESSAGE

The server node is down. (DBERR 31241)

CAUSE

Unable to communicate with the server.

ACTION

Reboot the system. If this does not solve the problem record as much information as possible and contact your HP Service Representative or Response Center.

31243
MESSAGE

Hardware error on interface card. (DBERR 31243)

CAUSE

There is a hardware error on the interface card.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31244
MESSAGE

Local node's hostname cannot be determined. (DBERR 31244)

CAUSE

Local domain name was not set.

ACTION

Set the local domain name in NMMGR.

31900
MESSAGE

Invalid login in NETUsers file. (DBERR 31900)

CAUSE

Incorrect syntax for server login in NetUsers file.

ACTION

Check 'Idtfy_clnt INVALID LOGIN' message in server log file hpdanslg.pub.sys for server login used. Run NETUtil to correct server login.

31901
MESSAGE

Error obtaining passwords for server login. (DBERR 31901)

CAUSE

Internal error. Errors could be in obtaining server process id, building or accessing temporary file or executing MPE/iX commands: LISTUSER, LISTACCT. LISTGROUP.

ACTION

Check 'Get xxx Passwd' message in server log file hpdanslg.pub.sys (where xxx = user, account or group) for more specific information.

31902
MESSAGE

Server login does not exist on server node. (DBERR 31902)

CAUSE

Specified user, account or group does not exist on server.

ACTION

Check 'Get xxx Passwd - No such login' message in server log file hpdanslg.pub.sys (where xxx = user, account or group) to determine which part of login failed. Have system or account manager create account, user or group or use NETUtil to change server login.

31903
MESSAGE

Error streaming server job. (DBERR 31903)

CAUSE

Internal error. Errors could be in obtaining process id, building or accessing temporary file or streaming temporary job.

ACTION

Check 'Server' message in server log file hpdanslg.pub.sys for more specific information.

31904
MESSAGE

Error obtaining home group for server login. (DBERR 31904)

CAUSE

Internal error. Errors could be in obtaining server process id, building or accessing temporary file or executing MPE/iX commands: LISTUSER, LISTACCT. LISTGROUP.

ACTION

Check 'Get xxx Passwd' message in server log file hpdanslg.pub.sys (where xxx = user, account or group) for more specific information.

31905
MESSAGE

No home group specified for server login. (DBERR 31905)

CAUSE

You did not specify a group in the NETUsers file for the mapped server login, and no home group was set up for the server login either.

ACTION

Use the MPE/iX ALTUSER command to add a home group for the server login, or specify a login group for the server login in the NETUsers file. for more specific information.

31992
MESSAGE

Corresponding ALLBASE/NET error not found for error (!) (DBERR 31992)

CAUSE

An error number has been generated that cannot be handled by the client.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

31994
MESSAGE

No entry found in password file on server node. (DBERR 31994)

CAUSE

The user name you specified by the PC API logon is not defined on this server.

ACTION

Verify that the user name sent by the PC is the correct user name. If it is the correct user name, add it to the server's password file.

31995
MESSAGE

Hostname not found or the hosts file cannot be opened. (DBERR 31995)

CAUSE

The hostname cannot be found in the HOSTS.NET.SYS file or the HOSTS.NET.SYS file does not exist.

31996
MESSAGE

The protocol file cannot be opened or the protocol name 'tcp' is not found. (DBERR 31996)

CAUSE

The PROTOCOL.NET.SYS file does exist or 'tcp' is not in the PROTOCOL.NET.SYS file.

ACTION

Ask the system administrator to set up the file or to correct the file. Refer to the LAN installation manual for information on this file.

31997
MESSAGE

The services file cannot be opened or the profile for 'DAServer' is not in the services file. (DBERR 31997)

CAUSE

The SERVICES.NET.SYS file does not exist or the definition of the ALLBASE/SQL RDA server is not in the SERVICES.NET.SYS file.

ACTION

Ask the system administrator to set up the services file or to correct the file. Refer to the LAN installation manual for information on this file.

31998
MESSAGE

Remote hpsqlproc process terminated prematurely. (DBERR 31998)

CAUSE

The server process terminated before the application finished.

ACTION

Restart the application.

31999
MESSAGE

The data communication service is undefined. (DBERR 31999)

CAUSE

The data communication type you specified in the AliasDB file is undefined

or

an abnormal situation occurred.

ACTION

Correct the profile in the AliasDB file

or

contact your HP Service Representative or Response Center.

33001
MESSAGE

LU 6.2 Security Error. (DBERR 33001)

CAUSE

The IBM system has rejected the LU 6.2 connection attempt.

ACTION

Correct the security parameters specified in the NETUtil AliasDB file entry.

33003
MESSAGE

LU 6.2 Send not allowed, partner LU has send. (DBERR 33003)

CAUSE

The HP side of the LU 6.2 connection has attempted a send when a send is disallowed by the protocol.

ACTION

This error should not occur. In the event that it does, transmission errors may have occurred. Contact your HP service representative or Response Center.

33004
MESSAGE

LU 6.2 Communications connection error. ! ! . (DBERR 33004)

CAUSE

The APPC LU 6.2 routines have detected a communications error.

ACTION

Follow the action described for this code in the HP LU 6.2 API Reference manual. A brief summary of the error codes may be obtained by issuing the command "print catappc.pub.sys." Certain LU 6.2 codes may indicate problems with the connection layers. For example

2

APPC does not have a NAU available for this connection request. The APPCCONTROL SESSIONS can be used to dynamically increase the number of sessions that APPC attempts to start, but VTAM must be configured to allow the increase.

19

APPC is not active

-9117

the connect between CICS and DB2 may not be active.

33121
MESSAGE

Invalid function for foreign access. (DBERR 33121)

CAUSE

The function is not available for foreign access. There are two possible cases for this situation to occur: 1) An attempt has been made to call a Switch routine that is not valid for foreign access

or

2) FDA cannot identify the SQL function in the statement being compiled.

ACTION

If connected to a foreign DBE, use only those commands that are valid for foreign access.

33123
MESSAGE

No DBEnvironment connected. (DBERR 33123)

CAUSE

Connection to a foreign DBE is expected but not found.

ACTION

Establish the connection to a foreign DBE.

33124
MESSAGE

Already connected to a DBE. (DBERR 33124)

CAUSE

An attempt has been made to connect to a DBE while already connected to a foreign DBE.

ACTION

Release the current DBE connection before connecting to a DBE.

33350
MESSAGE

Database server error !. (DBERR 33350)

CAUSE

Database server has detected an error.

ACTION

Record the database server error number and refer to the list of database server errors,

or

contact your HP Service Representative or Response Center.

33351
MESSAGE

Receiving message length is not long enough. (DBERR 33351)

CAUSE

The size of the message buffer is not large enough to receive the message from the database server.

ACTION

Increase the LU6.2 Input Buffer Length value of the alias definition in the AliasDB file.

33352
MESSAGE

The send message length is not long enough. (DBERR 33352)

CAUSE

The size of the message buffer is not large enough to send the message to the database server.

ACTION

Increase the LU6.2 Output Buffer Length of the alias definition in the AliasDB file.

34004
MESSAGE

Cannot start session. (RC !, !, !, !) (DBERR 34004)

CAUSE

An unexpected error was encountered when trying to connect to the DBEnvironment.

ACTION

Look for an additional message that provides more information.

34005
MESSAGE

Cannot terminate session. (RC !, !, !, !) (DBERR 34005)

CAUSE

An unexpected error was encountered when trying to release from the DBEnvironment.

ACTION

Look for an additional message that provides more information.

34006
MESSAGE

DBCORE error. (FNC !, RC !, !, ! !) (DBERR 34006)

CAUSE

An unexpected internal error was encountered.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

34008
MESSAGE

Unexpected INTERNAL error. (!, !, !, !) (DBERR 34008)

CAUSE

An unexpected internal error was encountered.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

34009
MESSAGE

Cannot attach to shared memory (RC !, !) (DBERR 34009)

CAUSE

An unexpected error was encountered.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

34010
MESSAGE

Cannot detach from shared memory (!) (DBERR 34010)

CAUSE

An unexpected error was encountered.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

34011
MESSAGE

Cannot fcontrol $STDINX. (! !) (DBERR 34011)

CAUSE

An MPE/iX file system error was encountered.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1.

34013
MESSAGE

Unexpected PROCINFO error. (PIN=!, !, !) (DBERR 34013)

CAUSE

An unexpected error was encountered while trying to get the name of the program that the user is running.

ACTION

Contact your system administrator.

34020
MESSAGE

Cannot allocate memory for data buffer structure (! !, !) (DBERR 34020)

CAUSE

An unexpected error was encountered.

ACTION

Contact your system administrator.

34021
MESSAGE

Cannot get data buffer pool head! (DBERR 34021)

CAUSE

An unexpected error was encountered while trying to find the data buffer pool in memory.

ACTION

The database administrator might have issued a STOP DBE statement. If not, record as much information as possible and contact your HP Service Representative or Response Center.

34022
MESSAGE

Number of data buffers not equal to DBECON value! (!, !, !) (DBERR 34022)

CAUSE

The size of the data buffer pool in memory does not match the size that is recorded in the DBECON file.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

34023
MESSAGE

Cannot get current buffer information! (DBERR 34023)

CAUSE

An unexpected error was encountered while sampling the data buffer pool.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

34030
MESSAGE

Could not find DBEFILE statistics in JMACRE buffer (DBERR 34030)

CAUSE

An unexpected error was encountered.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

34031
MESSAGE

Could not find INDEX statistics in JMACRE buffer (DBERR 34031)

CAUSE

An unexpected error was encountered.

ACTION

Record as much information as possible and contact your HP Service Representative or Response Center.

34071
MESSAGE

Number of sessions exceeds internal maximum (max=!) (DBERR 34071)

CAUSE

A limit has been reached.

ACTION

If you need the limit increased, please contact your HP Service Representative or Response Center.

34072
MESSAGE

Number of latches exceeds internal maximum (max=!) (DBERR 34072)

CAUSE

A limit has been reached.

ACTION

If you need the limit increased, please contact your HP Service Representative or Response Center.

34076
MESSAGE

Number of data buffers exceeds internal maximum (max=!) (DBERR 34076)

CAUSE

A limit has been reached.

ACTION

If you need the limit increased, please contact your HP Service Representative or Response Center.

34077
MESSAGE

Number of qualifying locks exceeds internal maximum (max=!) (DBERR 34077)

CAUSE

A limit has been reached.

ACTION

Use the SET LOCKFILTER or SET LOCKTABFILTER commands to reduce the number of locks that qualify. If you need the limit increased, please contact your HP Service Representative or Response Center.

34100
MESSAGE

Input too long. Maximum length is !. (DBERR 34100)

CAUSE

The total length of the input line exceeded the allowed limit.

ACTION

Issue the command again.

34102
MESSAGE

Unexpected end of input. (DBERR 34102)

CAUSE

An error was encountered trying to retrieve the next command.

ACTION

Check the output and input to see if all commands executed properly.

34103
MESSAGE

Illegal syntax. (DBERR 34103)

CAUSE

Command was entered incorrectly.

ACTION

Issue the command again. You can use the help facility to verify your syntax.

34104
MESSAGE

Illegal integer. (DBERR 34104)

CAUSE

Numeric value was entered incorrectly.

ACTION

Issue the command again.

34105
MESSAGE

Integer value out of range. (min=!,max=!) (DBERR 34105)

CAUSE

The number specified was not between the min and max values listed in the message.

ACTION

Issue the command again.

34106
MESSAGE

Illegal OWNER.TABLE value. (DBERR 34106)

CAUSE

You did not specify a valid table name.

ACTION

Issue the command again.

34107
MESSAGE

Illegal PAGE/ROW ID value. (DBERR 34107)

CAUSE

You did not specify a valid value.

ACTION

Issue the command again.

34120
MESSAGE

SystemFileName name is too long. Maximum length is !. (DBERR 34120)

CAUSE

The allowable length for the SystemFileName was exceeded.

ACTION

Issue the command again.

34121
MESSAGE

DBEFile name is not valid for this DBEnvironment. (DBERR 34121)

CAUSE

You did not specify a valid DBEFile name.

ACTION

Issue the command again.

34122
MESSAGE

DBEFileSet name is not valid, or has no DBEFiles. (DBERR 34122)

CAUSE

You did not specify a valid DBEFileSet name.

ACTION

Issue the command again.

34501
MESSAGE

DBEnvironmentName is too long. Maximum length is !. (DBERR 34501)

CAUSE

The allowable length for the DBEnvironmentName was exceeded.

ACTION

Issue the command again.

34502
MESSAGE

MAINT is too long. Maximum length is !. (DBERR 34502)

CAUSE

The allowable length for the maintenance word was exceeded.

ACTION

Issue the command again.

34503
MESSAGE

Incompatible DBEnvironment version (!). (DBERR 34503)

CAUSE

The version of the DBEnvironment is incompatible with the version of the program.

ACTION

Contact your database administrator, who probably needs to use SQLMigrate.

34504
MESSAGE

Not authorized to use SQLMONITOR on this DBEnvironment. (DBERR 34504)

CAUSE

You are not the DBECreator or a user having SM capability.

ACTION

Sign on as a user who does have the required authority.

34507
MESSAGE

Database in SINGLE-USER MODE. Cannot use SQLMONITOR. (DBERR 34507)

CAUSE

The DBEnvironment must be started in multi-user mode in order for SQLMonitor to connect to it.

ACTION

Try again later.

34530
MESSAGE

DBEFileSetName is too long. Maximum length is !. (DBERR 34530)

CAUSE

The allowable length for the DBEFileSetName was exceeded.

ACTION

Issue the command again.

34531
MESSAGE

DBEFileName is too long. Maximum length is !. (DBERR 34531)

CAUSE

The allowable length for the DBEFileName was exceeded.

ACTION

Issue the command again.

34540
MESSAGE

OWNER.TABLE is too long. Maximum length is !. (DBERR 34540)

CAUSE

The allowable length for the OWNER.TABLE was exceeded.

ACTION

Issue the command again.

34541
MESSAGE

PAGE/ROW ID is too long. Maximum length is !. (DBERR 34541)

CAUSE

The allowable length for the PAGE/ROW ID was exceeded.

ACTION

Issue the command again.

34550
MESSAGE

SystemFileName is too long. Maximum length is !. (DBERR 34550)

CAUSE

The allowable length for the SystemFileName was exceeded.

ACTION

Issue the command again.

34551
MESSAGE

SystemFileName could not be opened. (! !, !, !, !) (DBERR 34551)

CAUSE

A file system error was encountered.

ACTION

Refer to the system administration manual.

34552
MESSAGE

SystemFileName could not be created. (! !, !, !, !) (DBERR 34552)

CAUSE

A file system error was encountered.

ACTION

Refer to the system administration manual.

34553
MESSAGE

SystemFileName could not be rewritten. (DBERR 34553)

CAUSE

A file system error was encountered.

ACTION

Refer to the system administration manual.

34554
MESSAGE

SystemFileName could not be opened. (HPFOPEN !, !, !, !) (DBERR 34554)

CAUSE

A file system error was encountered.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1.

34555
MESSAGE

SystemFileName could not be created. (HPFOPEN !, !, !, !) (DBERR 34555)

CAUSE

A file system error was encountered.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1.

34556
MESSAGE

SystemFileName could not be rewritten. (HPFOPEN !, !, !, !) (DBERR 34556)

CAUSE

A file system error was encountered.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1.

34557
MESSAGE

SystemFileName could not be closed. (! !, !, !, !) (DBERR 34557)

CAUSE

A file system error was encountered.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1.

34560
MESSAGE

Could not write to SystemFileName. (FSERR !, !, !, !) (DBERR 34560)

CAUSE

A file system error was encountered.

ACTION

Refer to the MPE/iX Error Message Manual, Volume 1.

34585
MESSAGE

Timeout expired (! seconds, FNC !) (DBERR 34585)

CAUSE

SQLMON was not able to obtain some internal resource that was needed to complete the last command (for example, perhaps another session had obtained an X (exclusive) or an IX (intent exclusive) lock on a table that SQLMON was trying to read from).

ACTION

You may wish to use the SET USERTIMEOUT command to set a higher timeout value and issue your original command once again.

34610
MESSAGE

The timeout expired during an attempt to "Get Statistics" on table !.!, which exists within DBEFileset ! (DBERR 34610).

CAUSE

SQLMON was not able to obtain some internal resource that was needed to complete the last command (for example, perhaps another session had obtained an X (exclusive) or an IX (intent exclusive) lock on the table that SQLMON was trying to read from).

ACTION

You may wish to use the SET DBEFILESET command to specify another DBEFileset, and issue your original command once again. You can visit the STATIC screen to determine the DBEFileSets that exist within your DBEnvironment, and the tables that exist within them.

34630
MESSAGE

The timeout expired during an attempt to "Get Statistics" on a temporary table within DBEFileset ! (DBERR 34630).

CAUSE

SQLMON was not able to obtain some internal resource that was needed to complete the last command.

ACTION

You may wish to use the SET DBEFILESET command to specify another DBEFileset, and issue your original command once again. You can visit the STATIC screen to determine the DBEFileSets that exist within your DBEnvironment, and the tables that exist within them.

35000
MESSAGE

NETWARE LISTENER NOT RUNNABLE ON THIS BUILD. (DBERR 35000)

CAUSE

The ALLBASE/SQL PC API NetWare listener is not available on this version.

ACTION

Install a version of ALLBASE/SQL that supports NetWare access from ALLBASE/SQL PC API.

35400
MESSAGE

Invalid syntax for identifier. (DBERR 35400)

CAUSE

The session name specified in the login string for remote logon is not valid.

ACTION

Check the session name used for remote logon.

35401
MESSAGE

Unidentified user specified in logon. (DBERR 35401)

CAUSE

The user name specified in the login string for remote logon is not valid.

ACTION

Check the user name used for remote logon.

35402
MESSAGE

Unidentified account specified in logon. (DBERR 35402)

CAUSE

The account name specified in the login string for remote logon is not valid.

ACTION

Check the account name used for remote logon.

35404
MESSAGE

Incorrect user password. (DBERR 35404)

CAUSE

The user password you specified for the user.account logon is not valid.

ACTION

Determine what the correct password is.

35405
MESSAGE

Incorrect account password. (DBERR 35405)

CAUSE

The account password specified for logon is not valid.

ACTION

Determine the correct password.

35406
MESSAGE

Incorrect group password. (DBERR 35406)

CAUSE

The group password specified for logon is not valid.

ACTION

Determine the correct password.

35407
MESSAGE

Missing user password. (DBERR 35407)

CAUSE

A user password is required, but was not specified.

ACTION

Supply the password for the remote logon.

35408
MESSAGE

Missing account password. (DBERR 35408)

CAUSE

An account password is required, but was not specified.

ACTION

Supply the password for the remote logon.

35409
MESSAGE

Missing group password. (DBERR 35409)

CAUSE

An group password is required, but was not specified.

ACTION

Supply the password for the remote logon.

35410
MESSAGE

MPE user and account must be supplied. (DBERR 35410)

CAUSE

An incorrectly constructed logon string was given to the server for remote logon.

ACTION

Supply a correct logon string.

35411
MESSAGE

No home group for specified user. (DBERR 35411)

CAUSE

The login user specified does not have a home group and a login group was not specified.

ACTION

Either specify a login group or assign a home group to the user.

35414
MESSAGE

Invalid function code, !, received. (DBERR 35414)

CAUSE

The server received a function code from the PC that it was not expecting.

ACTION

Record all error information and call your HP representative.

140336
MESSAGE

Out of system resources. (DBERR 140336)

CAUSE

The system is overloaded and new processes cannot be created.

ACTION

Check for hung processes

or

run the process when fewer processes are running.

140337
MESSAGE

Formal designator does not exist. (DBERR 140337)

CAUSE

Your version of STORE.PUB.SYS does not have the enhancements required for online backup.

ACTION

Contact your HP Service Representative to obtain a version of STORE.PUB.SYS that supports online backup

or

perform a static store of the DBEnvironment using the procedures described in the "Backup and Recovery" chapter of the ALLBASE/SQL Database Administration Guide.

140338
MESSAGE

Formal designator is invalid. (DBERR 140338)

CAUSE

The version of STORE.PUB.SYS that you are attempting to use during an online backup is not valid.

ACTION

Check to make sure that your version of STORE.PUB.SYS matches the operating system version and has the enhancements required for online backup. For more information about these enhancements, contact your HP Service Representative.

Feedback to webmaster