Path: ...!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: bill <bill.gunshannon@gmail.com>
Newsgroups: comp.os.vms
Subject: Re: Capturing DCL output in symbol
Date: Sun, 11 May 2025 19:24:31 -0400
Lines: 27
Message-ID: <m8cptfFqnmiU2@mid.individual.net>
References: <87zfflxmbu.fsf@lucy.meyer21c.net>
 <87v7q9xf02.fsf@lucy.meyer21c.net> <vvqt4d$jomf$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net /tHcgJBUmwH0an5zOnrMmwJ0IBg+gMXYO70mdFCUgrCoww93dF
Cancel-Lock: sha1:70veoLhvbp0gcAChDe8i8x6spFg= sha256:wmqlGev7Ve6VrzWxRn7fzRbj/I6o+Hzz6xbi+wjKUUQ=
User-Agent: Mozilla Thunderbird
Content-Language: en-US
In-Reply-To: <vvqt4d$jomf$1@dont-email.me>
Bytes: 1754

On 5/11/2025 3:17 PM, Craig A. Berry wrote:
> On 5/9/25 11:32 PM, David Meyer wrote:
>> I found that one way to do it is to put all the processing that uses the
>> command output inside subshells in the same PIPE command.
>>
>> One shortcoming of this method is that it's very easy to go over the
>> maximum command element length allowed inside the PIPE. For my
>> procedure, I was able to get around this by choosing lexical functions
>> to minimize the length of the PIPE command.
>>
>> Any other way to do this?
> 
> It's pretty easy with Perl:
> 
> $ perl -"MVMS::DCLsym" -e "$x=`show time`; VMS::DCLsym->setsym('mysym', 
> $x, 'GLOBAL');"
> $ SHOW SYMBOL mysym
>    MYSYM == "   11-MAY-2025 14:10:89."
> 

It's probably easy to do in a lot of scripting languages.
But the original request specified DCL.  Might be he
expects the script to have to run on machines that only
have VMS on them.

bill