Created function handler for errors to prevent from the image/process closing when a severe error occurs something alog the lines:

INTEGER*4 FUNCTION HANDLER(SIGARGS, MECHARGS)
IMPLICIT NONE
C INCLUDE '($LIBDEF)'
INCLUDE '($STSDEF)'
INCLUDE '($SSDEF)'
C INTEGER*4 SIGARGS(*)
INTEGER*4 MECHARGS(*)
C INTEGER*4 ERRORCODE

ERRORCODE = 0
CALL MVBITS( SIGARGS(2), 0, 3, ERRORCODE, 0)

IF( ERRORCODE.EQ.STS$K_SEVERE ) THEN
CALL MVBITS( STS$K_ERROR, 0, 3, SIGARGS(2), 0)
ENDIF

HANDLER = SS$_RESIGNAL

RETURN
END

tested with a CALL LIB$SIGNAL(%VAL(4)) to force a severe error and the handler worked well that keeped the process/image running by reducing the severity of the error in case its severe.

1. Now want to log the error message to a file, so how to obtain the error message is it possible to pass SIGARGS(2) to a RTL function or other System function that returns me the message as per example the lexical function f$message(1409041) or should read the bit's of MSG_NO/Message number (3 to 15) that is refered in the "9.5 Condition Values" of "VSI_PROGRAM_CONCEPTS_VOL_I".

so basicaly from the error code get the error message text as the ones printed to console.

2. How to distinguish the error is originated from CALL LIB$SIGNAL(%VAL(4)) or CALL LIB$STOP(%VAL(0)).
Since if its LIB$STOP have to deal with the error using "Unwinding the Call Stack"
CALL SYS$UNWIND (MECHARGS(3),)
or
CALL SYS$UNWIND (,)
as refered in "9.12.4.5. Returning Control to the Program" of "VSI_PROGRAM_CONCEPTS_VOL_I"

3. last but not least when in a program occurs a error that is not handled and its fatal/severe is it treated by the system as a LIB$STOP or a LIB$SIGNAL(%VAL(4))?

note: LIB$SIGNAL(%VAL(4)) alls passing 4 to indicate that the severity of error is sever as stated in "table 9.7 Severity of Error Conditions", while LIB$STOP defaults to sever only passing 0 because yes no reason in specific....

> [...] how to obtain the error message [...]

HELP SYSTEM_SERVICES $GETMSG

HELP RTL_ROUTINES LIB$ LIB$SYS_GETMSG

A sexta-feira, 6 de maio de 2022 à(s) 16:19:02 UTC+1, Steven Schweda escreveu:
> > [...] how to obtain the error message [...]
>
> HELP SYSTEM_SERVICES $GETMSG
>
> HELP RTL_ROUTINES LIB$ LIB$SYS_GETMSG

Thanks @Steven Schweda

In article <7fbd1db1-3e38-433c-8749-df011e4e7884n@googlegroups.com>, Steven Schweda <sms.antinode@gmail.com> writes:
>> [...] how to obtain the error message [...]
>
> HELP SYSTEM_SERVICES $GETMSG
>
> HELP RTL_ROUTINES LIB$ LIB$SYS_GETMSG

PROGRAM GETMSG_DYNSTR
IMPLICIT NONE

INCLUDE '($DSCDEF)'
INCLUDE '($SSDEF)'
INCLUDE '(LIB$ROUTINES)'
INCLUDE '(STR$ROUTINES)'

INTEGER*4 STATUS

RECORD /DSCDEF1/ DYNSTR

DYNSTR.DSC$W_MAXSTRLEN = 0
DYNSTR.DSC$B_DTYPE = DSC$K_DTYPE_T
DYNSTR.DSC$B_CLASS = DSC$K_CLASS_D
DYNSTR.DSC$A_POINTER = 0

STATUS = 2928

STATUS = LIB$SYS_GETMSG(STATUS,,DYNSTR)

STATUS = LIB$PUT_OUTPUT(DYNSTR)

STATUS = LIB$PUT_OUTPUT(DYNSTR)
STATUS = STR$FREE1_DX(DYNSTR)

END

--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.

On 5/6/2022 12:32 PM, VAXman-@SendSpamHere.ORG wrote:
> In article <7fbd1db1-3e38-433c-8749-df011e4e7884n@googlegroups.com>, Steven Schweda <sms.antinode@gmail.com> writes:
>>> [...] how to obtain the error message [...]
>>
>> HELP SYSTEM_SERVICES $GETMSG
>>
>> HELP RTL_ROUTINES LIB$ LIB$SYS_GETMSG
>
> PROGRAM GETMSG_DYNSTR
> IMPLICIT NONE
>
> INCLUDE '($DSCDEF)'
> INCLUDE '($SSDEF)'
> INCLUDE '(LIB$ROUTINES)'
> INCLUDE '(STR$ROUTINES)'
>
> INTEGER*4 STATUS
>
> RECORD /DSCDEF1/ DYNSTR
>
> DYNSTR.DSC$W_MAXSTRLEN = 0
> DYNSTR.DSC$B_DTYPE = DSC$K_DTYPE_T
> DYNSTR.DSC$B_CLASS = DSC$K_CLASS_D
> DYNSTR.DSC$A_POINTER = 0
>
> STATUS = 2928
>
> STATUS = LIB$SYS_GETMSG(STATUS,,DYNSTR)
>
> STATUS = LIB$PUT_OUTPUT(DYNSTR)
>
> STATUS = LIB$PUT_OUTPUT(DYNSTR)
> STATUS = STR$FREE1_DX(DYNSTR)
>
> END

Cute with dynamic in Fortran.

But more oldfashioned:

PROGRAM GETMSG_FIXSTR
INCLUDE '(LIB$ROUTINES)'
INTEGER*4 STATUS,MSGLEN
CHARACTER*256 MSG
STATUS = 2928
CALL LIB$SYS_GETMSG(STATUS,MSGLEN,MSG)
CALL LIB$PUT_OUTPUT(MSG(1:MSGLEN))
END

Arne

In article <6275ba1c$0$696$14726298@news.sunsite.dk>, =?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne@vajhoej.dk> writes:
>On 5/6/2022 12:32 PM, VAXman-@SendSpamHere.ORG wrote:
>> In article <7fbd1db1-3e38-433c-8749-df011e4e7884n@googlegroups.com>, Steven Schweda <sms.antinode@gmail.com> writes:
>>>> [...] how to obtain the error message [...]
>>>
>>> HELP SYSTEM_SERVICES $GETMSG
>>>
>>> HELP RTL_ROUTINES LIB$ LIB$SYS_GETMSG
>>
>> PROGRAM GETMSG_DYNSTR
>> IMPLICIT NONE
>>
>> INCLUDE '($DSCDEF)'
>> INCLUDE '($SSDEF)'
>> INCLUDE '(LIB$ROUTINES)'
>> INCLUDE '(STR$ROUTINES)'
>>
>> INTEGER*4 STATUS
>>
>> RECORD /DSCDEF1/ DYNSTR
>>
>> DYNSTR.DSC$W_MAXSTRLEN = 0
>> DYNSTR.DSC$B_DTYPE = DSC$K_DTYPE_T
>> DYNSTR.DSC$B_CLASS = DSC$K_CLASS_D
>> DYNSTR.DSC$A_POINTER = 0
>>
>> STATUS = 2928
>>
>> STATUS = LIB$SYS_GETMSG(STATUS,,DYNSTR)
>>
>> STATUS = LIB$PUT_OUTPUT(DYNSTR)
>>
>> STATUS = LIB$PUT_OUTPUT(DYNSTR)
>> STATUS = STR$FREE1_DX(DYNSTR)
>>
>> END
>
>Cute with dynamic in Fortran.

Moreso than cute, it was disturbingly eye-opening! There is no SS$_FISH in the
$SSDEF module in FORSYSDEF.TLB.

--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.

In article <00B74568.BC1F735F@SendSpamHere.ORG>, VAXman- @SendSpamHere.ORG writes:
>In article <6275ba1c$0$696$14726298@news.sunsite.dk>, =?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne@vajhoej.dk> writes:
>>On 5/6/2022 12:32 PM, VAXman-@SendSpamHere.ORG wrote:
>>> In article <7fbd1db1-3e38-433c-8749-df011e4e7884n@googlegroups.com>, Steven Schweda <sms.antinode@gmail.com> writes:
>>>>> [...] how to obtain the error message [...]
>>>>
>>>> HELP SYSTEM_SERVICES $GETMSG
>>>>
>>>> HELP RTL_ROUTINES LIB$ LIB$SYS_GETMSG
>>>
>>> PROGRAM GETMSG_DYNSTR
>>> IMPLICIT NONE
>>>
>>> INCLUDE '($DSCDEF)'
>>> INCLUDE '($SSDEF)'
>>> INCLUDE '(LIB$ROUTINES)'
>>> INCLUDE '(STR$ROUTINES)'
>>>
>>> INTEGER*4 STATUS
>>>
>>> RECORD /DSCDEF1/ DYNSTR
>>>
>>> DYNSTR.DSC$W_MAXSTRLEN = 0
>>> DYNSTR.DSC$B_DTYPE = DSC$K_DTYPE_T
>>> DYNSTR.DSC$B_CLASS = DSC$K_CLASS_D
>>> DYNSTR.DSC$A_POINTER = 0
>>>
>>> STATUS = 2928
>>>
>>> STATUS = LIB$SYS_GETMSG(STATUS,,DYNSTR)
>>>
>>> STATUS = LIB$PUT_OUTPUT(DYNSTR)
>>>
>>> STATUS = LIB$PUT_OUTPUT(DYNSTR)
>>> STATUS = STR$FREE1_DX(DYNSTR)
>>>
>>> END
>>
>>Cute with dynamic in Fortran.
>
>Moreso than cute, it was disturbingly eye-opening! There is no SS$_FISH in the
>$SSDEF module in FORSYSDEF.TLB.

Nevermind. I checked on EISNER (a newer FORTRAN) and SS$_FISH is there.

--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.

A sábado, 7 de maio de 2022 à(s) 13:09:12 UTC+1, VAXman- escreveu:
> In article <00B74568...@SendSpamHere.ORG>, VAXman- @SendSpamHere.ORG writes:
> >In article <6275ba1c$0$696$1472...@news.sunsite.dk>, =?UTF-8?Q?Arne_Vajh=c3=b8j?= <ar...@vajhoej.dk> writes:
> >>On 5/6/2022 12:32 PM, VAX...@SendSpamHere.ORG wrote:
> >>> In article <7fbd1db1-3e38-433c...@googlegroups.com>, Steven Schweda <sms.an...@gmail.com> writes:
> >>>>> [...] how to obtain the error message [...]
> >>>>
> >>>> HELP SYSTEM_SERVICES $GETMSG
> >>>>
> >>>> HELP RTL_ROUTINES LIB$ LIB$SYS_GETMSG
> >>>
> >>> PROGRAM GETMSG_DYNSTR
> >>> IMPLICIT NONE
> >>>
> >>> INCLUDE '($DSCDEF)'
> >>> INCLUDE '($SSDEF)'
> >>> INCLUDE '(LIB$ROUTINES)'
> >>> INCLUDE '(STR$ROUTINES)'
> >>>
> >>> INTEGER*4 STATUS
> >>>
> >>> RECORD /DSCDEF1/ DYNSTR
> >>>
> >>> DYNSTR.DSC$W_MAXSTRLEN = 0
> >>> DYNSTR.DSC$B_DTYPE = DSC$K_DTYPE_T
> >>> DYNSTR.DSC$B_CLASS = DSC$K_CLASS_D
> >>> DYNSTR.DSC$A_POINTER = 0
> >>>
> >>> STATUS = 2928
> >>>
> >>> STATUS = LIB$SYS_GETMSG(STATUS,,DYNSTR)
> >>>
> >>> STATUS = LIB$PUT_OUTPUT(DYNSTR)
> >>>
> >>> STATUS = LIB$PUT_OUTPUT(DYNSTR)
> >>> STATUS = STR$FREE1_DX(DYNSTR)
> >>>
> >>> END
> >>
> >>Cute with dynamic in Fortran.
> >
> >Moreso than cute, it was disturbingly eye-opening! There is no SS$_FISH in the
> >$SSDEF module in FORSYSDEF.TLB.
> Nevermind. I checked on EISNER (a newer FORTRAN) and SS$_FISH is there.
> --
> VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
>
> I speak to machines with the voice of humanity.

Thanks @VaxMan and @Arne for the examples,

CHARACTER*256 MSG
INTEGER*4 ERR_NUM
INTEGER*4 LIB$SYS_GETMSG

CALL MVBITS( SIGARGS(2), 0, 32, ERR_NUM, 0)
CALL LIB$SYS_GETMSG(ERR_NUM,MSGLEN,MSG)

tried reading only bit 3 to 15 of SIGARGS(2) but concluded that needed to read the full 4 bytes since
$ write sys$output "FOR$_FILNOTFOU(1605868):",f$message(1605868)
$ write sys$output "FOR$_NO_SUCDEV(1605972):",f$message(1605972)
$ write sys$output "FOR$_FILNAMSPE(1605980):",f$message(1605980)
$ write sys$output "FOR$_OPEFAI(1605876):",f$message(1605876)
$ write sys$output "FOR$_NOTFORSPE(1605644):",f$message(1605644)

the examples that used are all 3 bytes at least (a litle bit less but who cares...)

and its working well.