[Info-vax] 64 bit DCL ?

[JF Mezei]

Just so I can understand the role of DCL.exe : (so this is all conceptually)

say one were to port bash to vms and create bash.EXE and set a user's
command to bash.exe :

when use uses the dcl PIPE command, is this a DCL.exe construct, or doe
DCL use VMS system services to accomplish the task and could these
services be used by bash implement the piping ?

In terms of symbols, are those entirely native to DCL.EXE, or are the
services needed to create/translate symbols part of VMS and thus
available if DCL.EXE is not the current command processor ?

Could bash use its own native symbols (environment variables),
allocating its own memory space the same way DCL does it ?


Now the tough part:

in DCL, when I "show queue/all/this/that=hello"

when SHOW.EXE calls the dcl parsing routines, are those in DCL.EXE or
available elsewhere in VMS ?

if bash were to take this command
show queue -a -this -that hello

and put "show queue/all/this/that=hello" in memory somewhere, could
SHOW.EXEC then call the DCL parsing routines to see what arguments were
passed ?

akaL bash gets some sort of translation table to convert unix style to
DCL commands, and then lets the called application call the parsing
routines to get the list of arguments ?