HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
Showing results for 
Search instead for 
Did you mean: 

BACKUP using 000000

R Fleck
Occasional Contributor

BACKUP using 000000

Is there a reason that the BACKUP command
places all the files from subdirectories in the top
directory when 000000 is used in the directory

BACKUP $1$DIA0:[000000.AERO...]*.*;* DNFS4:[000000.AERO...]*.*;*

places all the files in DNFS4:[000000.AERO...]

BACKUP $1$DIA0:[AERO...]*.*;* DNFS4:[AERO...]*.*;*

works as expected copying the directory tree and placing
the files in the correct subdirectories.

If there was something in the manuals I must have missed it.

John Gillings
Honored Contributor

Re: BACKUP using 000000


You haven't said what version you're running. The command you've given does exactly what I expect on my system (ie: reproduces the directory tree from the input disk to the output disk).

The general rule with BACKUP is to ensure the input and output wildcards match.

Perhaps try:

$ BACKUP $1$DIA0:[000000.AERO...]*.*;* DNFS4:[*...]*.*;*/LOG

Also note that in this particular case the "000000" is redundant, so if you get a more acceptable result without it, maybe just leave it out?
(this is called a "doctor, doctor, my head hurts when I bang it on the wall" problem description ;-)

If you think there's a bug in BACKUP behaviour, please log a case with your local customer support centre to report it. Be sure to include the exact version of OpenVMS (+ any relevant UPDATE or BACKUP patches), the exact command you're issuing, a transcript of the output, and a description of the output you were expecting.
A crucible of informative mistakes
John Gillings
Honored Contributor

Re: BACKUP using 000000


I checked on some other systems, and I have observed the same, incorrect, results as you report. It's definitely a bug.

The good news is it's fixed in V8.3, and should be released as patches to V7.3-2 and V8.2 some time soon. Look for a BACKUP or UPDATE patch with a BACKUP link date after 1-MAY-2006.

In the mean time, work around the problem by omitting the 000000. in input and output filespecs.
A crucible of informative mistakes
Guy Peleg
Respected Contributor

Re: BACKUP using 000000

As John said, this looks like a bug.

If you require a fix, please file a call
with your local support center and have
them escalate the problem to engineering.

Best Regards,

Guy Peleg
Sebastian Bazley
Regular Advisor

Re: BACKUP using 000000

You probably already know this, but just in case...

The command:


does not transfer the protection, ownership and ACLs for the AERO directory itself.

You can do this with the following command:

DISK2:[000000]AERO.DIR;1 -
R Fleck
Occasional Contributor

Re: BACKUP using 000000

Thank You for letting me know
it is a bug that has been fixed
and your advice on
protection, ownership and ACLs