Backup Manager's routines employ a special error-handling mechanism to handle problems. When a routine encounters an error, it stores a special value into the system errornum variable and passes the error using the PassErr command. Programs which call these routines can trap the error using the standard Try...Else...EndTry construction.
An error-handling routine named errh is supplied for generating text error messages for each of the special error codes. Ordinarily, AMS will refer to all Backup Manager-generated errors as an Unknown Error, since these codes do not correspond to AMS's built-in error codes. The special values stored to errornum and their meanings are described below.
errornum value | errh message | Cause |
---|---|---|
10000 | Please enter full path incl. folder. | A full path (a folder name, a backslash (\), then a file name) to a backup or file is not passed to a routine. Backup Manager routines require a full path to operate. |
10001 | Folder 'ωbman3' cannot be used. | An attempt is made to back up or restore a file that is located in the ωbman3 folder. This is disallowed to prevent critical Backup Manager files from being overwritten and therefore damaged. |
10002 | File <filename> already backed up | An attempt is made to back up a file with newbu that has already been backed up. To update a backup, the updbu routine should be used. |
10003 | File <filename> not found | A file passed to a routine does not exist. |
10004 | Stored-away files cannot be updated. | A backup cannot be updated if it is stored away, because the original file for a stored-away backup is not expected to still exist. The backup's type must be returned to a normal backup before it can be updated. |
10005 | File <filename> not backed up | The specified file passed to a routine is not backed up. Routines that generate this error expect a file that has a backup. |
10006 | File already exists | A routine tried to write a file, but a file with the same folder and file name already exists there. Some routines can be instructed (via an input parameter) to ignore the error and overwrite a file in this situation. Otherwise, the existing file will need to be renamed, moved, or deleted in order for the operation to succeed. |
10007 | Skipping stored bkup <filename> | The delbu routine has a parameter that can be set to generate this error if it tries to delete a stored-away backup. This error indicates that the operation was therefore not carried out on the stored-away backup. |
10008 | Invalid database type | An unrecognized backup database type was passed to the getbd, regbd, or unregbd routines. The two recognized types are "d" (for the backup information database) and "g" (for the group information database). |
10009 | Duplicate field ID | An attempt was made to register a new database field with regbd, but a field with the ID used already exists in the database. Either the new field will have to be created with a different ID, or the existing field will have to be deleted first. |
10010 | System database fields cannot be deleted. | An attempt was made to delete a field with unregbd that is required for Backup Manager to function properly. Only fields created with regbd can be deleted. |
10011 | Backup database error | One or more files making up the backup database were deleted, or are no longer of type LIST. closebd will detect this, automatically restore the database to the state it was in the last time it was opened with openbd, and then generate this error. |
10012 | Backup database field not found | getbd or unregbd was called to find or delete a field that does not exist in the given database type. |
10013 | A group with this name already exists. | grpadd was called to create a group whose name is the same as an already defined group. Try creating a group with a different name or deleting the existing group first. |
10014 | No such group exists. | No group by the name passed to grpdel, grpren, grpaddbu, or grprembu exists. |
10015 | Bkup <filename> already in group | grpaddbu was called to add a backup to a group, but the backup already belongs to that group. |
10016 | Backup <filename> not in group | grprembu was called to remove a backup from a group, but the backup doesn't exist in the given group. |
10017 | Invalid version index | The version index given for version operations is not valid. That is, it is less than one, or it is higher than the number of versions defined for the given backup. |
10018 | Stored-away backups cannot be restored. | restbu was called to restore a backup that is stored away. Instead of being restored, stored-away backups must be made normal backups with storebu, which will return the stored-away files to their original locations. |