Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.os.vms    |    DEC's VAX* line of computers & VMS.    |    264,096 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 262,690 of 264,096    |
|    Craig A. Berry to bill    |
|    Re: Capturing DCL output in symbol    |
|    11 May 25 21:15:49    |
   
   From: craigberry@nospam.mac.com   
      
   On 5/11/25 6:24 PM, bill wrote:   
   > 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.   
      
   On OpenVMS x86, Perl is part of the base install, so it's always there.   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   
|
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca