Problem with Tapesys

[Steven Bearden]

I am running Tapesys 6r1 on ans ES40 with OVMS 7.3-2 and when running the weekly or monthly backups (full backups) I get the following message from tapesys "image backup must be physical disk device" and the backup(s) fail. The strange thing is that the daily backups (incrementals) are running fine. If anyone can provide assistance it would be greatly appreciated.

[Guenther Froehlin]

Did you specify more than just the device name in this case (image backup)?

/Guenther

[Steven Bearden]

No here are the disks and the backup command in the .sbk file. As far as I know they have never been changes and all of a sudden last weekend quit working and giving the message I sent earlier:

$ FILES_1 :== $1$DGA3: ! AX4000
$ HISTORY_SET_1 :== FULL5 ! ODS-5
$ FILES_2 :== $9$DKA0: ! ITVMS1
$ HISTORY_SET_2 :== FULL5 ! ODS-5
$ FILES_3 :== $9$DKA100: ! ITVMS1
$ HISTORY_SET_3 :== FULL5 ! ODS-5
$ FILES_4 :== $3$DKA300: ! AX4000
$ HISTORY_SET_4 :== FULL5 ! ODS-5

$ QUALIFIERS == "/IMAGE/BLOCK=61440/NOCRC/GROUP=0/IGNORE=INTERLOCK
/MEDIA_FORMAT=COMPACTION/RECORD"

[EdgarZamora]

The way TAPESYS backups are usually formed, multiple command files are pulled in for information. Check the dates on the files in the directory where you keep the SBKs and see if anything has changed recently. Another suggestion would be to examine the log file of the backup and check the actual VMS BACKUP command being executed. Please post it here if you want us to take a look. Good luck.

[Steven Bearden]

Thanks. I found out the problem. Someone had modified the sylogin.com file and did a
set proc/parse=extended in one of the command files. Modified tapesys login to do a set proc/parse=traditional and tested and everything is running fine now.

[Steven Bearden]

Found solution.