| I did some checking in the code. This error can be returned when the value
we pass to sys$bintim is invalid and therefore can't be converted. We use
this routine (and would return the error mentioned in .0) when we are converting
the dates pertaining to a file, such as creation date, expiration date,
date modified, and so on. I suspect these errors indicate a problem with
the attributes of some of the files on the customer system.
If anyone sees this problem again, please try and identify the files involved.
For example, a save request generates a backup command, and sends the "listing"
from the backup command to a mailbox. We read the mailbox and parse out
the dates. It is possible the listing format was somehow broken, or that the
dates on some of the files were invalid. If you do the same backup command
that ABS generates, and specify the listing file to a file, then compare the
file with the abs log entry which contains this error, we may be able to narrow
down which files were involved. (basically compare the abs$log and the vms
backup listing and narrow down the files) Then we can look more closely at
the files, or the listing from VMS backup and see which looks incorrect.
Hope this helps for futures.
Jim
|