[Info-vax] SUBMIT/CONFIRM behavior

[Ian Miller]

On Tuesday, December 7, 2021 at 12:36:32 PM UTC, Phillip Helbig (undress to reply) wrote:
> In article <sonie5$m41$1... at dont-email.me>, 
> =?UTF-8?Q?Jan-Erik_S=c3=b6derholm?= <jan-erik.... at telia.com> 
> writes:
> > This "works" (Alpha 8.4-2L2): 
> > 
> > $ direc sub*.com 
> > 
> > Directory $1$DGA3610:[JES] 
> > 
> > SUB.COM;1 SUB2.COM;1 
> > 
> > Total of 2 files. 
> > $ 
> > $ subm/noprint sub*.com /confirm 
> > SUBMIT $1$DGA3610:[JES]SUB.COM;1 ? [N]: Y 
> > SUBMIT $1$DGA3610:[JES]SUB2.COM;1 ? [N]: N 
> > Job SUB (queue SYS$BATCH, entry 276) started on SYS$BATCH 
> > $ 
> > 
> > I guess that, if you need the /confirm switch, you are expected to 
> > use a file specification that returns more then one file. 
> > 
> > Still shouldn'r return that error...
> > PS: 
> > And it still expects that you want to submit at least one file. :-)
> In that sense, it is different from other /CONFIRM commands. 
> 
> My "favourite" bogus severity: MOUNT/SHADOW. If I enter the command 
> correctly, and it detects that a full copy is needed, then I get -F-.

That behavior of MOUNT/SHADOW is potentially protecting your data.