|From:||John E. Malmberg|
|Subject:||VMS exit status fixes.|
|Date:||Sat, 08 Mar 2014 11:05:42 -0600|
|User-agent:||Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3|
As this is considered a failure status on Unix (non-zero), it should also be considered a failure status on VMS.
It best matched to a failure status of STS$K_WARNING, with the error code 2 be STS$K_ERROR as it is now.
The other logical alternative would be for severity for MAKE_TROUBLE to also to be STS$K_ERROR, which would force DCL scripts to actually look at the status code to determine the difference.
To have MAKE_TROUBLE be informational status would not be correct since it is documented to be a failure condition.
|[Prev in Thread]||Current Thread||[Next in Thread]|