Problem in backup

[Jan van den Ende]

Re Richard

>>>
$ BACKUP/VERIFY NUS$MKC600:JZIEGLER.SAV /BY_OWNER=[130,220] NUS$DKD400:[000000...]
<<<

Better make that
... NUS$DKD400:[*...]

or you might create an extra directory level of
000000.DIR

And IF you do that, it can be pretty convoluted to untie that knot.

As a general rule, always try to prevent using 000000 as directory in ANY command. Either specifying * or leaving it out totally will prevent (sometimes MUCH later) problems.

fwiw

Proost.

Have one on me.

jpe

[Jon Pinkley]

> > Something like:
> > [...] /BY_OWNER= [...]
>
> Not really. HELP BACKUP /BY_OWNER explains
> the difference between /BY_OWNER as an input
> file-selection qualifier and as an output
> file (or save set) qualifier.

Regardless of what the help says, it does work as suggested by Richard. The /BY_OWER is treated as an input qualifier whether it is a disk or a save set, at least in 8.3 (this is the only one I have tested with, but I believe it has been this way for a long time). It still has limited usefulness, because it can only be used to match a single UIC, and using /NOBY_OWNER is the same as leaving the qualifier off. In other words, I don't think there is a way to choose files that don't belong to a UIC (the way that the ACCOUNTING utility can exclude PIDs)

See attachment for a reproducer.

Jon

[Richard Brodie_1]

> Better make that ... NUS$DKD400:[*...]

Oh yes, I just rearranged the original command without looking too hard.

[Steven Schweda]

> Not really. [...]

Oops.

> Regardless of what the help says, it does
> work [...]

Right. My feeble brain was thinking "save"
and "restore", but BACKUP works with "input"
and "output", as the HELP says.

So, we seen to agree that a separate save set
for each user is not a good idea.