Using pipe in VMS 7.6

[haibara]

I am using VMS 7.6 and i find there is no "pipe" command in it.
How do i do to input the text when runing the com file like:

pipe type input.txt | @runtest

thanks a lot

[Ian Miller.]

Can you check which version of VMS you have.
I don't recall there being a 7.6 release.

A list of VMS versions can found found at

http://h71000.www7.hp.com/openvms/openvms_supportchart.html

[Steven Schweda]

> I am using VMS 7.6 [...]

What? On what?

As usual, showing actual commands with their
actual output can be more helpful than vague
(and inaccurate) descriptions or
interpretations.

write sys$output f$getsyi( "arch_name")
write sys$output f$getsyi( "version")

> [...] i find [...]

What, exactly, did you do, and what, exactly,
happened when you did it?

[Andy Bustamante]

There was no 7.6 release of OpenVMS.
Please post the results of

$ write sys$output f$getsyi("version")
$ write sys$output f$getsyi("arch_type")
(1 - VAX, 2 - Alphaserver, 3 - Integrity).

[Hoff]

PIPE was added at OpenVMS V7.1.

You either need to upgrade to V7.1 or later to use PIPE, or you need to re-code the DCL to eliminate the use of the PIPE command.

Specifically for the DCL PIPE example shown, you would likely need to re-code RUNTEST to read the file directly.

Here is a general example of using DCL file-processing to perform the necessary file I/O to read and display the contents of a file:

http://labs.hoffmanlabs.com/node/383

[John Gillings]

>pipe type input.txt | @runtest

Regardless of the version of OpenVMS you're running, for this case, (assuming your RUNTEST procedure reads from SYS$PIPE), you should be able to recode your PIPE command as:

$ OPEN/READ SYS$PIPE INPUT.TXT
$ @RUNTEST
$ CLOSE SYS$PIPE

More generally, you can break up your PIPE commands into segments:

$ DEFINE/USER SYS$OUTPUT pipe1.tmp
$ execute 1st pipe segment

$ OPEN/READ SYS$PIPE pipe1.tmp
$ DEFINE/USER SYS$OUTPUT pipe2.tmp
$ execute 2nd pipe segment
$ CLOSE SYS$PIPE

etc...

However, there are cases where this won't work. For example anywhere a pipe segment can't be executed to completion before passing the data to the next segment.

[haibara]

Thanks everyone's help.
I just find that there is typo in my thread.

OpenVMS is in version 6

what i want to do, actually, is instead of
input data from terminal, i want to input data stored in input.txt

here is the example:

testpipe.com


$ write sys$output "please input the value"
$ INQUIRE/NOPUNC in_ans "Enter Value:"
$ write sys$output "answer is ''in_ans'"


==================================
input.txt

HELLO

=================================
I don't want to edit the COM file.
but how can i input "HELLO" to when i run
testpipe.com from input.txt??

thanks a lot

[Hoff]

Here is a general example of using DCL file-processing to perform the necessary file I/O to read and display the contents of a file:

http://labs.hoffmanlabs.com/node/383

The HP VMS documentation is here:

http://www.hp.com/go/openvms/doc

Read the User's Guide first, and then the DCL dictionary.

And do yourself a favor, and don't use the INQUIRE command. That command is far weirder than might be realized, and (because of those behaviors) that command is specifically locked out in various OpenVMS contexts. Use the READ command in place of INQUIRE.

[MarkOfAus]

Hi,
Try this:

pipe type input.txt | @testpipe

But as you have a version without pipe, it's all academic really. Pipe was introduced in 7.1 I believe.

Cheers
Mark

[MarkOfAus]

Hi,
I'm sorry, I should offer a solution. This is based on what I know of your problem (which is very little):


$ define sys$error nl:
$ set message/nofac/noident/notext/nosev
$ spawn /input=input.txt @testpipe
$ deassign sys$error
$ set message/fac/ident/text/nosev

Set message hides the message guff from spawn (there are other ways but...)

Cheers
Mark