HP 3000 Manuals HP 3000 Manuals
DBChange Plus Messages (continued)
-------------------------------------------------------------------------------
549 MESSAGE No key item defined for master set DataSetName
(DBC 549).
MEANING A master data set was added without a key item, or
the key item was deleted.
ACTION Delete the data set; or delete the data set, and
then add the set with the key item defined.
-------------------------------------------------------------------------------
550 MESSAGE Pascal error n (DBA 550).
MEANING A Pascal library procedure did not complete.
ACTION Refer to the Pascal/3000 Reference Manual, where n
is the Pascal error number.
-------------------------------------------------------------------------------
550 MESSAGE Set DataSetName entry length n less than 2 words
(DBC 550).
MEANING The detail data set DataSetName has no paths and an
entry length less than two words (MPE/V words or
MPE/XL halfwords), which is not allowed by
DBSCHEMA.
ACTION Add more fields to the data set, or increase the
item length of the existing fields.
-------------------------------------------------------------------------------
551 MESSAGE Cannot CHECK/FIX this new set until added by
DBAlter (DBC 551).
MEANING The CHECK or FIX command cannot be issued for a
data set that is not actually in the database, that
is, not yet processed by the DBAPLUS program
(DBAlter).
ACTION Run the DBAPLUS program to actually add the data
set, then use the CHECK or FIX command.
-------------------------------------------------------------------------------
552 MESSAGE Invalid search item specified for CHECK/FIX PATH
(DBC 552).
MEANING The item name entered as a search item for the
CHECK or FIX command is not a valid search item.
ACTION Enter a correct search item name.
-------------------------------------------------------------------------------
553 MESSAGE Cannot erase automatic master data set (DBC 553).
MEANING The ERASE SET command was issued for an automatic
master data set. The data in an automatic master
data set cannot be explicitly erased.
ACTION An automatic master data set entry is erased once
the detail data set entries are erased. Use the
ERASE SET command to erase the related detail data
sets linked to the automatic master data set.
-------------------------------------------------------------------------------
554 MESSAGE Detail set DataSetName still has n entries (DBC
554).
MEANING The ERASE SET command was issued for a manual
master data set that has one or more paths linked
to detail data sets where related detail data set
entries still exist.
ACTION Issue ERASE SET for each of the detail data set
entries with paths linked to the manual master data
set, then issue ERASE SET for the manual master
data set.
-------------------------------------------------------------------------------
555 MESSAGE Cannot read the change file (DBA 555).
MEANING The MPE intrinsic FREAD or FREADDIR failed while
reading the change file. In addition to 555,
message 410 is also displayed.
ACTION Refer to the MPE Intrinsics Reference Manual, where
n is the file system error number returned from the
FCHECK intrinsic.
-------------------------------------------------------------------------------
555 MESSAGE Cannot erase manual set with existing related
detail entries (DBC 555).
MEANING The ERASE SET command was issued for a manual
master data set that has one or more paths linked
to detail data sets where related detail data
entries still exist.
ACTION Issue ERASE SET for each of the detail data set
entries with paths linked to the manual master data
set, then issue ERASE SET for the manual master
data set.
-------------------------------------------------------------------------------
556 MESSAGE Cannot erase data set until added by DBAlter (DBC
556).
MEANING ERASE SET was issued for a data set that was not
yet actually added to the database, that is,
processed by the DBAPLUS program (DBAlter).
ACTION Verify that the data set name is correct and exists
in the database.
-------------------------------------------------------------------------------
557 MESSAGE Cannot read the check file FileName (FSERR n)
(DBA 557).
MEANING The MPE intrinsic FREAD or FREADDIR failed while
rading the check file.
ACTION Refer to the MPE Intrinsics Reference Manual, where
FSERR n is the file system error number returned
from the FCHECK intrinsic.
-------------------------------------------------------------------------------
557 MESSAGE ERASE SET has already been issued for the data
set (DBC 557).
MEANING ERASE SET was issued a second time for the same
data set.
ACTION Erase the data set entries and reissue the ERASE
SET command.
-------------------------------------------------------------------------------
558 MESSAGE Data set has not been set to erase. Cannot
CANCEL ERASE (DBC 558).
MEANING CANCEL ERASE was issued for a data set that was not
flagged to be erased by ERASE SET.
ACTION No action necessary if you do not intend to erase
the data set entries.
-------------------------------------------------------------------------------
559 MESSAGE CTL_ERASE_SETS less than zero. Cannot CANCEL
ERASE (DBC 559).
MEANING CANCEL ERASE was issued for a data set.
CTL_ERASE_SETS field in the change file control
record, which reflects the number of data set
entries to be erased, has a number less than zero.
ACTION Verify that the change file has been correctly
restored from a previous DBCPLUS run. If not,
purge the change file and rerun the DBCPLUS
program.
-------------------------------------------------------------------------------
560 MESSAGE Cannot read the root file (DBA 560).
MEANING The MPE intrinsic FREADDIR failed while trying to
read the root file. In addition to 560, message
410 is also displayed.
ACTION Refer to the MPE Intrinsics Reference Manual, where
n is the file system error number returned from the
FCHECK intrinsic.
-------------------------------------------------------------------------------
560 MESSAGE Data set has not been set to repack. Cannot
CANCEL REPACK (DBC 560).
MEANING CANCEL REPACK was issued for a data set without
issuing a previous REPACK SET command.
ACTION No action necessary if you do not want to repack
the data set.
-------------------------------------------------------------------------------
561 MESSAGE CTL_REPACK_SETS less than zero. Cannot CANCEL
REPACK (DBC 561).
MEANING CANCEL REPACK was issued for a data set. The
CTL_REPACK_SETS field in the change file control
record, which reflects the number of data sets to
be repacked, has a number less than zero.
ACTION Verify that the change file has been correctly
restored from a previous DBCPLUS run. If not,
purge the change file and rerun the DBCPLUS
program.
-------------------------------------------------------------------------------
562 MESSAGE Cannot repack a master data set (DBC 562).
MEANING REPACK SET was issued for a master data set.
ACTION REPACK SET can only be issued for a detail data
set.
-------------------------------------------------------------------------------
563 MESSAGE Cannot repack data set until added by DBAlter
(DBC 563).
MEANING REPACK SET was issued for a data set that was not
yet actually added to the database, that is,
processed by the DBAPLUS program (DBAlter).
ACTION Verify that the data set name is correct and exists
in the database.
-------------------------------------------------------------------------------
564 MESSAGE REPACK SET has already been issued for the data
set (DBC 564).
MEANING REPACK SET was issued a second time for the same
data set.
ACTION If the repack option is to be changed for the data
set, use CANCEL REPACK then REPACK SET with the
correct repack option. Otherwise, no action is
necessary.
-------------------------------------------------------------------------------
565 MESSAGE REPACK SET option must be serial or chained (DBC
565).
MEANING REPACK SET was issued with the incorrect repack
option or the repack option was incorrectly placed
in the command syntax.
ACTION Verify the syntax of the REPACK SET command by
using HELP. Use serial or chained as the repack
option.
-------------------------------------------------------------------------------
566 MESSAGE Invalid search item specified for REPACK SET (DBC
566).
MEANING An incorrect or misplaced search item was used in
the REPACK SET command.
ACTION Verify that the correct search item name was used.
Verify the syntax of the REPACK SET command by
using HELP.
-------------------------------------------------------------------------------
567 MESSAGE Path search item is invalid, cannot REPACK SET
DataSetName (DBC 567).
MEANING The path specified by the search item used in the
REPACK SET command does not exist. The path may
have been deleted after the REPACK SET command was
used.
ACTION Verify that the path still exists by using the
REVIEW PATHS command. If not, use the CANCEL
REPACK and REPACK SET commands for another path.
-------------------------------------------------------------------------------
568 MESSAGE Cannot use a newly added path to REPACK SET
DataSetName (DBC 568).
MEANING A new path was added to the data set DataSetName,
and the path is being specified for a REPACK SET
command with the chained option. No chain
information exists for the new path, so it cannot
be used to repack the data set.
ACTION Use the CANCEL REPACK and REPACK SET commands for
another path.
-------------------------------------------------------------------------------
569 MESSAGE Duplicate schema file. Cannot process PRINT
SCHEMA (DBC 569).
MEANING A file with the same name already exists.
ACTION Use another unique file name, or purge the existing
file and run the DBCPLUS program again with the
PRINT SCHEMA command.
-------------------------------------------------------------------------------
570 MESSAGE Cannot read the root file label (DBA 570).
MEANING The MPE intrinsic FREADLABEL failed while trying to
read the file label of the root file. In addition
to 570, message 410 is also displayed.
ACTION Refer to the MPE Intrinsics Reference Manual, where
n is the file system error number returned from the
FCHECK intrinsic.
-------------------------------------------------------------------------------
570 MESSAGE Cannot close the schema file (FSERR n) (DBC 570).
MEANING The MPE intrinsic FCLOSE failed while closing the
schema file.
ACTION Refer to the MPE Intrinsics Reference Manual, where
FSERR n is the file system number returned from the
FCHECK intrinsic.
-------------------------------------------------------------------------------
571 MESSAGE LOGON to the account where NewBaseName will
reside (DBC 571).
MEANING When copying a database, you must be logged on to
the account where the new database copy will
reside.
ACTION Logon to the correct account.
-------------------------------------------------------------------------------
572 MESSAGE SM or (OP and PM) capabilities required to copy
across accounts (DBC 572).
MEANING You do not have the required MPE capabilities to
copy a database across accounts.
ACTION Acquire SM or (OP and PM) capabilities.
-------------------------------------------------------------------------------
573 MESSAGE AM capability or CREATOR access required to copy
within account (DBC 573).
MEANING You do not have the required MPE capabilities to
copy a database within an account.
ACTION Acquire AM capability or CREATOR access.
-------------------------------------------------------------------------------
574 MESSAGE SF (save file) capability required to copy a
database (DBC 574).
MEANING You do not have the required MPE capability to copy
a database.
ACTION Acquire SF capability.
-------------------------------------------------------------------------------
575 MESSAGE AM capability or CREATOR access required to
replace a database (DBC 575).
MEANING You do not the required MPE capability to replace a
database.
ACTION Acquire AM capability or CREATOR access.
-------------------------------------------------------------------------------
576 MESSAGE Percentfull must be 0 < MinFull < NewFull <
MaxFull < 100 (DBC 576).
MEANING The values entered for the CONTROL PERCENTFULL
command are incorrect.
ACTION Re-enter the CONTROL PERCENTFULL parameter values.
MinFull must be 0 to 100; NewFull and MaxFull must
be 1 to 100; MaxFull must be greater than NewFull;
and NewFull must be greater than MinFull.
-------------------------------------------------------------------------------
577 MESSAGE Data set DataSetName has capacity less than one
(DBC 577).
MEANING The capacity for the data set DataSetName in the
current database is less than one. CONTROL
PERCENTFULL cannot be calculated for the set.
ACTION Change the capacity using the CHANGE CAPACITY
command.
-------------------------------------------------------------------------------
578 MESSAGE Cannot calculate PERCENTFULL for a new data set
(DBC 578).
MEANING The data set specified in the CONTROL PERCENTFULL
command is not yet added to the database.
ACTION Either specify a data set that already exists, or
add the specified data set by running the DBAPLUS
program, and then entering the CONTROL PERCENTFULL
command again.
-------------------------------------------------------------------------------
579 MESSAGE MinFull percent must be 0 to 100 (DBC 579).
MEANING The MinFull parameter was incorrectly entered in
the CONTROL PERCENTFULL command.
ACTION Re-enter the MinFull parameter using a value of 0
to 100.
-------------------------------------------------------------------------------
580 MESSAGE Cannot read the data set DataSetName (DBA 580).
MEANING The MPE intrinsic FREADDIR failed while reading the
data set DataSetName. In addition to 580, message
410 is also displayed.
ACTION Refer to the MPE Intrinsics Reference Manual, where
n is the file system error number returned from the
FCHECK intrinsic.
-------------------------------------------------------------------------------
580 MESSAGE NewBaseName already exists and REPLACE not
requested (DBC 580).
MEANING Unless the REPLACE parameter is used with the COPY
command, an existing database cannot be
overwritten.
ACTION Either give the database copy a new name, or use
the REPLACE parameter.
-------------------------------------------------------------------------------
590 MESSAGE Cannot read the file label of data set
DataSetName (DBA 590).
MEANING The MPE intrinsic FREADLABEL failed while reading
the file label of data set DataSetName. In
addition to 590, message 410 is also displayed.
ACTION Refer to message 410.
-------------------------------------------------------------------------------
600 MESSAGE Cannot rename set DataSetName1 to DataSetName2
(DBA 600).
MEANING The MPE intrinsic FRENAME failed while renaming the
data set DataSetName1 to the name DataSetName2. In
addition to 600, message 410 is also displayed.
ACTION Refer to message 410.
-------------------------------------------------------------------------------
601 MESSAGE Invalid characters after delete (D) command (DBC
601).
MEANING An invalid character or too many characters were
entered when using the REDO command with the delete
option.
ACTION Only D or I (for insert) is allowed after the first
D in the REDO command. Redo the command line.
-------------------------------------------------------------------------------
602 MESSAGE More than 80 characters on the line (DBC 602).
MEANING Too many characters were inserted when using the
REDO command.
ACTION Only 80 characters are allowed on a command line.
Redo the command line using 80 or fewer characters.
-------------------------------------------------------------------------------
603 MESSAGE New command exceeds maximum 216 characters
allowed (DBC 603).
MEANING Too many characters were inserted when using the
REDO command.
ACTION Only 216 characters per command are allowed. Redo
the command using 216 or fewer characters.
-------------------------------------------------------------------------------
610 MESSAGE Cannot rename set DataSetName1 to TEMPDB
DataSetName2 (DBA 610).
MEANING The MPE intrinsic FRENAME failed while renaming the
data set DataSetName1 to DataSetName2 in the
database TEMPDB used in the conversion process. In
addition to 610, message 410 is also displayed.
ACTION Refer to the MPE Intrinsics Reference Manual, where
n is the file system error number returned from the
FCHECK intrinsic.
-------------------------------------------------------------------------------
615 MESSAGE Cannot reset condition word or root file label
(DBA 615).
MEANING The condition word in the root file label could not
be reset to a value that would allow subsequent
access to the database.
ACTION Run DBUTIL and purge the database. Restore a
backup copy.
-------------------------------------------------------------------------------
620 MESSAGE Cannot restructure database while recovery in
progress (DBA 620).
MEANING Database recovery has not been completed.
ACTION Refer to the TurboIMAGE/XL DBMS Reference Manual
for information on DBRECOV STOP-RESTART.
-------------------------------------------------------------------------------
630 MESSAGE Database is corrupt due to prior termination of
DBAlter (DBA 630).
MEANING The database is corrupted because the restructuring
process was not completed during a previous run of
the DBAPLUS program (DBAlter).
ACTION Run the DBAlter program again to finish the
restructuring process.
-------------------------------------------------------------------------------
640 MESSAGE Database is not in a consistent state (DBA 640).
MEANING A database operation was started and has not
completed. In addition to 640, message 370 is also
displayed.
ACTION Finish the database operation before running the
DBAPLUS program. Refer to message 370 for
additional instructions.
-------------------------------------------------------------------------------
645 MESSAGE Database contains errors and no "FIX" requested
(DBA 645).
MEANING The database contains errors. The DBCPLUS JCW is
set to 210 so that a batch job can detect the
damaged database.
ACTION Use the FIX command to correct errors.
-------------------------------------------------------------------------------
650 MESSAGE Security violation (DBA 650).
MEANING Either the logon user, group, or account do not
match what is in the change file or you do not have
MPE access to the change file.
ACTION Verify that you have logged on correctly and have
access to the change file.
-------------------------------------------------------------------------------
660 MESSAGE N existing records of data set M exceed the
capacity of cap (DBA 660).
MEANING The new capacity is less than the number of
existing entries in the data set.
ACTION Run the DBChange program again and specify a
capacity that is greater than the number of
existing entries. If the database is corrupt,
purge it, and restore a backup copy.
-------------------------------------------------------------------------------
663 MESSAGE Data set DataSetName is full (DBA 663).
MEANING The key value cannot be added to the master data
set DataSetName because the data set is full.
ACTION Change the data set capacity and reissue the FIX
command.
-------------------------------------------------------------------------------
670 MESSAGE Data set DataSetNum does not exist in the change
file (DBA 670).
MEANING The change file contains inconsistent data set
information. The data set number DataSetNum was
not found in the change file.
ACTION Run the DBCPLUS program again and create a new
change file. If the database is corrupt, purge it,
and restore a backup copy.
-------------------------------------------------------------------------------
675 MESSAGE Error returned from SORT subsystem (SORTERR n)
(DBA 675).
MEANING An error occurred in the SORT subsystem.
ACTION Refer to the MPE XL Utilities SORT-MERGE/3000
Reference Manual where SORTERR n is the error
number returned from the SORT ERROR messages.
-------------------------------------------------------------------------------
680 MESSAGE Not enough stack space to perform operation (DBA
680).
MEANING The stack size could not be increased to copy the
database or to create a data set. The Pascal
library procedure GETHEAP or RTNHEAP failed.
ACTION Notify the system manager.
-------------------------------------------------------------------------------
683 MESSAGE Check file full. Further events will not be
recorded (DBA 683).
MEANING All events resulting from the previously issued
CHECK command cannot be recorded and displayed.
ACTION Use CHECK PATH/FIX PATH commands instead of CHECK
BASE/FIX BASE commands.
-------------------------------------------------------------------------------
685 MESSAGE Unknown event number encountered in check file
(DBA 685).
MEANING Either the file DatabaseNameRX is damaged or a
DBChange Plus error exists.
ACTION Contact your HP representative.
-------------------------------------------------------------------------------
687 MESSAGE Cannot write to the check file FileNameRX (FSERR
n) (DBA 687).
MEANING The MPE intrinsic FWRITE failed while writing to
the check file FileNameRX.
ACTION Refer to the MPE Intrinsics Reference Manual, where
n is the file system error number returned from the
FCHECK intrinsic.
-------------------------------------------------------------------------------
690 MESSAGE Cannot write to new root file (DBA 690).
MEANING The MPE intrinsics FWRITE failed while attempting
to write to the new root file. In addition to 690,
message 410 is also displayed.
ACTION Refer to the MPE Intrinsics Reference Manual, where
n is the file system error number returned from the
FCHECK intrinsic.
-------------------------------------------------------------------------------
700 MESSAGE Cannot write to the root file label (DBA 700).
MEANING The MPE intrinsic FWRITELABEL failed while writing
to the file label of either the new or old root
file. In addition to 700, message 410 is also
displayed.
ACTION Refer to message 410.
-------------------------------------------------------------------------------
710 MESSAGE Cannot write to the data set DataSetName (DAB
710).
MEANING The MPE intrinsic FWRITE failed while writing to
the data set DataSetName. In addition to 710,
message 410 is also displayed.
ACTION Refer to the MPE Intrinsics Reference Manual, where
n is the file system error number returned from the
FCHECK intrinsic.
-------------------------------------------------------------------------------
720 MESSAGE Cannot write to file label of data set
DataSetName (DBA 720).
MEANING The MPE intrinsic FWRITELABEL failed while writing
to the file label of the data set DataSetName. In
addition to 720, message 410 is also displayed.
ACTION Refer to the MPE Intrinsics Reference Manual, where
n is the file system error number returned from the
FCHECK intrinsic.
-------------------------------------------------------------------------------
730 MESSAGE Cannot write to hashing database TEMPDB (DBA
730).
MEANING The MPE intrinsic FWRITEDIR failed while writing to
the temporary database TEMPDB during the
restructuring process. In addition to 730, message
410 is also displayed.
ACTION Refer to message 410.
-------------------------------------------------------------------------------
740 MESSAGE MPE intrinsic SWITCHDB failure (DBA 740).
MEANING The MPE intrinsic SWITCHDB failed while copying or
restructuring the database.
ACTION Notify the system manager.
-------------------------------------------------------------------------------
750 MESSAGE Cannot write to change file (DBA 750).
MEANING The MPE intrinsic FWRITEDIR failed while writing to
the change file. In addition to 750, message 410
is also displayed.
ACTION Refer to the MPE Intrinsics Reference Manual, where
n is the file system error number returned from the
FCHECK intrinsic.
-------------------------------------------------------------------------------
900 MESSAGE Data set DataSetName: expected N entries,
processed only M entries (DBA 900).
MEANING An error occurred while writing to the data set
DataSetName records. N is the number of records in
the set. M is the number of records processed
successfully.
ACTION Informational message only. No action necessary.
-------------------------------------------------------------------------------
910 MESSAGE N detail records were lost in altering
DataSetName (DBA 910).
MEANING An error occurred while writing to the data set
DataSetName records. N is the number of records
not written.
ACTION Informational message only. No action necessary.
-------------------------------------------------------------------------------
920 MESSAGE N master records were lost in altering
DataSetName (DBA 920).
MEANING An error occurred while writing to the data set
DataSetName records. N is the number of records
not written.
ACTION Informational message only. No action necessary.
-------------------------------------------------------------------------------