VMS: have the IVP verify that a well known engine loads properly

Reviewed-by: Rich Salz <rsalz@openssl.org>

diff --git a/VMS/openssl_ivp.com.in b/VMS/openssl_ivp.com.in
index 3555bf60236e2e45505ce614081de2d273345461..a4c67b26a9acceb3df0153fc968d983401201ef6 100644 (file)
--- a/VMS/openssl_ivp.com.in
+++ b/VMS/openssl_ivp.com.in
@@ -32,9 +32,19 @@ $        WRITE SYS$ERROR "Installation inconsistent"
 $          EXIT %x00018292 ! RMS$_FNF, file not found
 $      ENDIF
 $
 $          EXIT %x00018292 ! RMS$_FNF, file not found
 $      ENDIF
 $

+$      ON ERROR THEN GOTO error
+$

 $      ! If something else is wrong with the installation, we're likely
 $      ! to get an image activation error here
 $      openssl version -a
 $
 $      ! If something else is wrong with the installation, we're likely
 $      ! to get an image activation error here
 $      openssl version -a
 $

+$      ! Verify that engines are where they should be.
+$      openssl engine -c -t dasync
+$

 $      WRITE SYS$ERROR "OpenSSL IVP passed"
 $      EXIT %x10000001
 $      WRITE SYS$ERROR "OpenSSL IVP passed"
 $      EXIT %x10000001

+$
+$ error:
+$      save_status = $STATUS
+$      WRITE SYS$ERROR "OpenSSL IVP failed"
+$      EXIT 'save_status'