HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Error Messages (Cont.)
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.
----------------------------------------------------------------------------