Why doesn't this simple PIPE command work? Why doesn't it recognize DIRSORT as a verb? It works fine directly at the DCL prompt. And VMS native commands work fine.

I can DEFINE/USER SYS$OUTPUT to file and SEARCH that file. But shouldn't this work? Why doesn't it? TIA.

$ PIPE DIRSORT TO%.COM;* /DA=CR | SEAR SYS$INPUT "Dec","Nov"
%SEARCH-I-NOMATCHES, no strings matched
$ PIPE DIRSORT TO%.COM;* /DA=CR | TYPE SYS$INPUT
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\DIRSORT\
$ VERB DIRSORT
define verb DIRSORT
image DIRSORT
parameter P1, label=PATH
value (type=$file)
qualifier DATE, nonnegatable
value (required,type=DATE_KEYWORDS)
qualifier DELTATIME, nonnegatable
qualifier LAYOUT, nonnegatable
value (required,type=LAYOUT_KEYWORDS)
qualifier SORT, nonnegatable
value (required,type=SORT_KEYWORDS)
qualifier HELP
qualifier VERSION, nonnegatable

define type DATE_KEYWORDS
keyword BACKUP
keyword CREATE
keyword EXPIRE
keyword REVISE, default

define type LAYOUT_KEYWORDS
keyword DATEFIRST, default
keyword FILEFIRST
keyword TRUNCATE

define type SORT_KEYWORDS
keyword ASCENDING, default
keyword DESCENDING

$

On 2022-10-12, alanfe...@gmail.com <alanfeldman48@gmail.com> wrote:
> Why doesn't this simple PIPE command work? Why doesn't it recognize DIRSORT as a verb? It works fine directly at the DCL prompt. And VMS native commands work fine.
>

Is the command defined as part of DCLTABLES or did you define it for the
current process only by using $ SET COMMAND ?

If it's the latter, that will not work with PIPE.

Simon.

--
Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.

> Why doesn't this simple PIPE command work? [...]

Did you define DIRSORT as a foreign-command symbol, or what, exactly?
Sometimes the results you get depend on your own (invisible/unreported)
actions.

DIRSORT has a command-line parsing scheme which has some oddities.
For example:

ITS $ mcr sys$disk:[]DIRSORT.EXE /version

MCR by Lyle W West
Version: V1.2-4 (Vax)
Image Build: Sep 25 2022 (DecC)
Required Privs: SYSPRV (or READALL)

The program is not named "MCR", it's not running on a VAX, and the
compiler used is not called "DecC".

I started to look into this mess, but haven't spent as much time on
it as it needs.

On Wednesday, October 12, 2022 at 1:03:39 PM UTC-4, Simon Clubley wrote:
> On 2022-10-12, alanfe...@gmail.com <alanfe...@gmail.com> wrote:
> > Why doesn't this simple PIPE command work? Why doesn't it recognize DIRSORT as a verb? It works fine directly at the DCL prompt. And VMS native commands work fine.
> >
> Is the command defined as part of DCLTABLES or did you define it for the
> current process only by using $ SET COMMAND ?

Just SET COMMAND.

So that's the answer. Thank you, sir!

Can I put it in my own copy of DCLTABLES, if there even is one? I'm just a user on EISNER working on a few DCL command procedures.

Probably not worth it, as I don't use it that often. So I guess it's easier to use the DEFINE/USER SYS$OUTPUT <filespec>.

> If it's the latter, that will not work with PIPE.

Bummer (mild).

>
> Simon.
>
> --
> Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
> Walking destinations on a map are further away than they appear.

AEF

On Wednesday, October 12, 2022 at 2:48:08 PM UTC-4, Steven Schweda wrote:
> > Why doesn't this simple PIPE command work? [...]
>
> Did you define DIRSORT as a foreign-command symbol, or what, exactly?
> Sometimes the results you get depend on your own (invisible/unreported)
> actions.

I posted the output of VERB DIRSORT. Isn't that enough?

> DIRSORT has a command-line parsing scheme which has some oddities.
> For example:
>
> ITS $ mcr sys$disk:[]DIRSORT.EXE /version
>
> MCR by Lyle W West
> Version: V1.2-4 (Vax)
> Image Build: Sep 25 2022 (DecC)
> Required Privs: SYSPRV (or READALL)
>
> The program is not named "MCR", it's not running on a VAX, and the
> compiler used is not called "DecC".
>
> I started to look into this mess, but haven't spent as much time on
> it as it needs.

Anyway, it does the job.
OK.
AEF

Den 2022-10-12 kl. 22:26, skrev alanfe...@gmail.com:
> On Wednesday, October 12, 2022 at 2:48:08 PM UTC-4, Steven Schweda wrote:
>>> Why doesn't this simple PIPE command work? [...]
>>
>> Did you define DIRSORT as a foreign-command symbol, or what, exactly?
>> Sometimes the results you get depend on your own (invisible/unreported)
>> actions.
>
> I posted the output of VERB DIRSORT. Isn't that enough?

If I'm not wrong, the utility VERB can show DCL commands from
both the system common DCLTABLES and any process defined verbs
using SET COMMAND. The first works with PIPE, the second does not.

So no, It is not enough, if we do not know where the
verb DIRSORT comes from.

On Wednesday, October 12, 2022 at 4:32:20 PM UTC-4, Jan-Erik Söderholm wrote:
> Den 2022-10-12 kl. 22:26, skrev alanfe...@gmail.com:
> > On Wednesday, October 12, 2022 at 2:48:08 PM UTC-4, Steven Schweda wrote:
> >>> Why doesn't this simple PIPE command work? [...]
> >>
> >> Did you define DIRSORT as a foreign-command symbol, or what, exactly?
> >> Sometimes the results you get depend on your own (invisible/unreported)
> >> actions.
> >
> > I posted the output of VERB DIRSORT. Isn't that enough?
> If I'm not wrong, the utility VERB can show DCL commands from
> both the system common DCLTABLES and any process defined verbs
> using SET COMMAND. The first works with PIPE, the second does not.
>
> So no, It is not enough, if we do not know where the
> verb DIRSORT comes from.

Thank you, sir.

On 10/12/2022 12:42 PM, alanfe...@gmail.com wrote:
> Why doesn't this simple PIPE command work? Why doesn't it recognize
> DIRSORT as a verb? It works fine directly at the DCL prompt. And VMS
> native commands work fine. >
> I can DEFINE/USER SYS$OUTPUT to file and SEARCH that file. But shouldn't this work? Why doesn't it? TIA.
>
> $ PIPE DIRSORT TO%.COM;* /DA=CR | SEAR SYS$INPUT "Dec","Nov"
> %SEARCH-I-NOMATCHES, no strings matched
> $ PIPE DIRSORT TO%.COM;* /DA=CR | TYPE SYS$INPUT
> %DCL-W-IVVERB, unrecognized command verb - check validity and spelling
> \DIRSORT\

As other have said then most likely the verb is missing
for the subprocess created by pipe.

So you need to add the verb for the subprocess.

Demo:

$ type hello.c
#include <stdio.h>
#include <stdlib.h>

int main(int argc, char *argv[])
{ int n = atoi(argv[1]);
for(int i = 0; i < n; i++)
{
printf("Hi!\n");
}
return 0;
} $ type hello.cld
define verb hello
image "sys$disk:[]hello"
parameter p1
$ cc hello
$ link hello
$ set command hello
$ hello 3
Hi!
Hi!
Hi!
$ pipe hello 3 | type sys$input
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\HELLO\
$ pipe (set command hello ; hello 3) | type sys$input
Hi!
Hi!
Hi!

Arne

On 10/12/2022 4:24 PM, alanfe...@gmail.com wrote:
> On Wednesday, October 12, 2022 at 1:03:39 PM UTC-4, Simon Clubley
> wrote:
>> On 2022-10-12, alanfe...@gmail.com <alanfe...@gmail.com> wrote:
>>> Why doesn't this simple PIPE command work? Why doesn't it
>>> recognize DIRSORT as a verb? It works fine directly at the DCL
>>> prompt. And VMS native commands work fine.
>>>
>> Is the command defined as part of DCLTABLES or did you define it
>> for the current process only by using $ SET COMMAND ?
>
> Just SET COMMAND.
>
> So that's the answer. Thank you, sir!
>
> Can I put it in my own copy of DCLTABLES, if there even is one? I'm
> just a user on EISNER working on a few DCL command procedures.
>
> Probably not worth it, as I don't use it that often. So I guess it's
> easier to use the DEFINE/USER SYS$OUTPUT <filespec>.

Just put the SET COMMAND in the PIPE command as
in my example.

If you have privs you can:

$ SET COMM foobar /TABLE=sys$share:dcltables /OUT=foobartables.exe

and in SYSUAF/AUTHORIZE set your username to use CLITABLES foobartables.exe.

Arne

In article <b5ae6ac1-9398-45d1-9863-7f562a0e4257n@googlegroups.com>, "alanfe...@gmail.com" <alanfeldman48@gmail.com> writes:
>On Wednesday, October 12, 2022 at 1:03:39 PM UTC-4, Simon Clubley wrote:
>> On 2022-10-12, alanfe...@gmail.com <alanfe...@gmail.com> wrote:
>> > Why doesn't this simple PIPE command work? Why doesn't it recognize DIRSORT as a verb? It works fine directly at the DCL prompt. And VMS native commands work fine.
>> >
>> Is the command defined as part of DCLTABLES or did you define it for the
>> current process only by using $ SET COMMAND ?
>
>Just SET COMMAND.
>
>So that's the answer. Thank you, sir!
>
>Can I put it in my own copy of DCLTABLES, if there even is one? I'm just a user on EISNER working on a few DCL command procedures.
>
>Probably not worth it, as I don't use it that often. So I guess it's easier to use the DEFINE/USER SYS$OUTPUT <filespec>.
>
>> If it's the latter, that will not work with PIPE.
>
>Bummer (mild).
>
>>
>> Simon.
>>
>> --
>> Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP
>> Walking destinations on a map are further away than they appear.
>
>AEF

Define DIRSORT as a foreign command: $ DIRSORT:==$<full-spec-of-DIRSORT.EXE>

When the subprocess of the PIPE command is created it will copy the DCL
symbol table and thus, DIRSORT can be executed.

--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.