[Info-vax] A DCL wish list of sorts...
Arne Vajhøj
arne at vajhoej.dk
Sat Mar 23 14:16:57 EDT 2019
On 3/22/2019 2:59 PM, John Reagan wrote:
> On Friday, March 22, 2019 at 1:17:15 PM UTC-4, pcanagno... at gmail.com wrote:
>> On Friday, March 22, 2019 at 12:55:36 PM UTC-4, dgordo... at gmail.com wrote:
>>> On Friday, March 22, 2019 at 12:42:54 PM UTC-4, pcanagno... at gmail.com wrote:
>>>
>>> In fact it does. It needs CMEXEC to load the table into P1. I made changes around that as well (to only enable it when needed) but that wasn't the issue.
>>
>> The CDU loads the table into P1? Wow, I sure don't remember that. I thought it just wrote a file. But then, how would a user command get into P1?
>>
>> How quickly I forget.
>
> SET COMMAND FOO.CLD will update the existing table in P1
>
> SET COMMAND /TABLE=MYTABLE.EXE loads a fresh new table into P1
>
> SET COMMAND /OUTPUT=MYTABLE.EXE writes out the table from P1
>
> SET COMMAND /TABLE=MYTABLE.EXE /OUTPUT=MYTABLE.EXE reads your table, updates it, writes it out, leaves the P1 table alone.
>
> $ set command /output=mytable.exe /table=sys$library:dcltable.exe
> $ set command /output=mytable.exe /table=mytable.exe [-]bliss_in.cld
> $ set command /table=mytable
I think SET COMMAND is doing too much.
Maybe CREATE COMMAND, LOAD COMMAND and SAVE COMMAND etc. would
have been clearer.
Arne
More information about the Info-vax
mailing list