HP Archive Backup System for OpenVMS Guide to Operations

Troubleshooting
12.4 ABS Catalogs
12.3.5 MDMS$LOGFILE_*.LOG
12.4ABS Catalogs
12.4.1 Staging Unpack
The MDMSView GUI is generating requests to the MDMS server, so any problems may be logging
errors into the MDMS$LOG:MDMS$LOGFILE_.LOG or
MDMS$LOG:MDMS$LOGFILE_DBSERVER.LOG files. If you receive an MDMS error window
when executing an action, check these files for errors.
If you receive an error MDMS$ERROR, this means that the MDMS server did not respond correctly
to the request. This error may need to be reported to HP.
If you are using ABS catalogs which are set to use staging, the save/restore request logs will contain
information about the staging files, the command procedure used to unpack the file, and the
log file generated by the unpack process. The log file is generated in the ABS$LOG directory
and contains information about the unpack process. If there were errors during the unpack mail
will be sent to the person(s) named as the MAIL recipient(s) in the MDMS domain.
If errors occur, the ABS$CATALOG:*.STG and ABS$CATALOG:*.COM files are not deleted.
You may run the *.com file as a batch job with ABS as the user. This allows you to unpack the
files once you have determined the reason that they failed. Some reasons may be that the catalog
disk is full, the system went down, etc.
If there are errors in the unpack logs which indicate an error with the
ABS$CATALOG_UNPACK_STG program, you should report this problem to HP.
12.4.2 Volume_Set Catalog Cleanup
To perform the cleanup on the VAOE file for the Volume_Set type of catalog, ensure that the logical
ABS_CATALOG_VAOE_CLEANUP is defined. Also, the VAOE, VAOEI and the VTLE
files corresponding to the catalog must be present in the same location. This is because, before
the actual cleanup of the VAOE file, the Cleanup process compares the entries against the
VAOEI file to check if the entries are valid. If the entries are found valid, only then the Cleanup
process proceeds further.
For example, assuming that the VAOEI files are moved to a directory other than the directory
having the VAOE files. In such cases, when the catalog Cleanup process is executed, it deletes
all the records in the VAOE file as it does not find the corresponding VAOEI file.
Also, the following must be verified before executing the cleanup process:
• Sufficient File Limit (FILLM) Quota and Main Memory is available. The suggested FILLM
quota is 500.
• Parallel Save and Restore requests are not executed. If they are executed, then the catalog
will have dangling VAOEI entries.
Note
This user defined logical is specific to ABS version 4.4 and will be automatically removed
when ABS is uninstalled. In case you want to downgrade ABS, you need to manually deassign
this logical to free the space that it has occupied in the System table.
If there is insufficient FILLM quota, ABS displays an OPCOM once, then logs an error in the
Cleanup log file and aborts the Cleanup process.
• OPCOM message:
The OPCOM message displayed informs you that the FILLM quota is less and also provides
the exact number by which the FILLM quota must be incremented:
12-6 Troubleshooting