A customer asked me to explain how SUBMIT/CONFIRM works. I had never
used this command combination so I checked $ HELP SUBMIT /CONFIRM and
then made a simple TEST.COM that just did a $DIR and tried
"$ SUBMIT/CONFIRM TEST"

If you answer Y (or T or 1) it submits the job but if you accept the
default or enter N you get:

VMS3 $ SUBMIT/CONFIRM TEST.COM
SUBMIT SYS$SYSDEVICE:[JEFFREY]TEST.COM;1 ? [N]:
%SUBMIT-F-CREJOB, error creating job
-UTIL-W-FILFAIMAT, file failed to match selection criteria
VMS3 $

with $STATUS as %X10C1800C.

Although I showed the customer a better way to do what he really wanted
to do, this seems to be a bug in SUBMIT. "/CONFIRM" on any command
should not throw an error if you enter "N". I use DELETE/CONFIRM and
COPY/CONFIRM very often and entering "N" doesn't throw an error.

The same thing happens on Alpha OpenVMS V8.3, Itanium OpenVMS V8.4 and
Itanium OpenVMS V8.4-2L1

Any ideas?

Jeff
www.digitalsynergyinc.com

Den 2021-12-07 kl. 05:59, skrev Jeffrey H. Coffield:
> A customer asked me to explain how SUBMIT/CONFIRM works. I had never used
> this command combination so I checked $ HELP SUBMIT /CONFIRM and then made
> a simple TEST.COM that just did a $DIR and tried
> "$ SUBMIT/CONFIRM TEST"
>
> If you answer Y (or T or 1) it submits the job but if you accept the
> default or enter N you get:
>
> VMS3 $ SUBMIT/CONFIRM TEST.COM
> SUBMIT SYS$SYSDEVICE:[JEFFREY]TEST.COM;1 ? [N]:
> %SUBMIT-F-CREJOB, error creating job
> -UTIL-W-FILFAIMAT, file failed to match selection criteria
> VMS3 $
>
> with $STATUS as %X10C1800C.
>
> Although I showed the customer a better way to do what he really wanted to
> do, this seems to be a bug in SUBMIT. "/CONFIRM" on any command should not
> throw an error if you enter "N". I use DELETE/CONFIRM and COPY/CONFIRM very
> often and entering "N" doesn't throw an error.
>
> The same thing happens on Alpha OpenVMS V8.3, Itanium OpenVMS V8.4 and
> Itanium OpenVMS V8.4-2L1
>
> Any ideas?
>
> Jeff
> www.digitalsynergyinc.com

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...

Regards,

Jan-Erik.

PS:
And it still expects that you want to submit at least one file. :-)

$ subm/noprint sub*.com /confirm
SUBMIT $1$DGA3610:[JES]SUB.COM;1 ? [N]: N
SUBMIT $1$DGA3610:[JES]SUB2.COM;1 ? [N]: N
%SUBMIT-F-CREJOB, error creating job
-UTIL-W-FILFAIMAT, file failed to match selection criteria
$

In article <sonie5$m41$1@dont-email.me>,
=?UTF-8?Q?Jan-Erik_S=c3=b6derholm?= <jan-erik.soderholm@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-.

On Tuesday, December 7, 2021 at 12:36:32 PM UTC, Phillip Helbig (undress to reply) wrote:
> In article <sonie5$m41$1...@dont-email.me>,
> =?UTF-8?Q?Jan-Erik_S=c3=b6derholm?= <jan-erik....@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.

In article <6eebef98-0557-4e33-a4c0-1464fbb63fe9n@googlegroups.com>, Ian
Miller <gxys@uk2.net> writes:

> > 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.

I can sort of understand it. However, consider that one is creating a
new shadow set and enters the proper commands then gets a fatal error.

Jeff,

please consider to log a call with VSI. Maybe just a mail with a historical reference to the good old 'SPR system' is sufficient to fix this problem in the distant future...

Volker.