[Info-vax] Command Procedure Pipe output to a variable

[Stephen Hoffman]

On 2021-10-01 16:10:29 +0000, HCorte said:

> Thanks for the links to the documentation Stephen, reading the 
> "Run-Time Library LIB$ Routines" for the lib$spawn and status that can 
> return SS$_NORMAL,SS$_ACCVIO,SS$_DUPLNAM ,fac$_xxx,LIB$_INVARG 
> ,LIB$_INVSTRDES,LIB$_NOCLI
> 
> with INCLUDE '($SSDEF)' know that the values of
> SS$_NORMAL:           1
> SS$_ACCVIO:          12
> SS$_DUPLNAM:         148
> 
> but can't find what is the library to include for remaining constants 
> LIB$_INVARG ,LIB$_INVSTRDES,LIB$_NOCLI and fac$_xxx
> 
> getting the following value retuned by the SPAWN routine: 231666
> 
> know that its not LIB$_INVARG and LIB$_INVSTRDES since was able to run 
> in simple program (lib$spawn) where the params are the same, so most 
> likely is LIB$_NOCLI or fac$_xxx.
> 
> could someone help in what is the name of library for the constants 
> Status return by the routine and 231666 means what? perhaps its 
> fac$_xxx "Other error trying to create subprocess." if so a bit vague 
> in the probleam...

LIBDEF, and HELP /MESSAGE, and the rest, as mentioned in previous 
replies to this reply.

Best to use STSDEF to capture whole ranges of errors, and not try to 
list all specific errors in the error-handling code, though.

Low bit set is success, clear is failure.  Success is odd. Failure is 
even.  The condition values are further broken down into success, 
informational, warning, error, and fatal ranges.

There are lots of potential errors.

And new errors can be added.

In the debugger, the command EXAMINE /CONDITION {variablename} helps 
speed the whole development and debug process.

If you're not using the debugger here, well, it's an invaluable tool 
for these and other development-related tasks.


-- 
Pure Personal Opinion | HoffmanLabs LLC