Hello Wilfred!

Wednesday December 14 2022 21:41, you wrote to me:

 > Hi Vincent,

 > On 2022-12-14 18:28:42, you wrote to me:

 VC>> Found a wee bug in the .pas code -

 > Good find! ;)

 VC>> IF the following is not set or used  (no parameters used)
 VC>> EXECUTE  then errflags returns after displaying the report  with
 VC>> :

 VC>> An unhandled exception occurred at $000000000042DAB9:

 VC>> EProcess: Cannot execute empty command-line
 VC>>   $000000000042DAB9
 VC>>   $000000000042E283
 VC>>   $0000000000402194
 VC>>   $00000000004022AD
 VC>>   $0000000000408071

 VC>> I suspect caused by not checking that the var that would hold
 VC>> param from EXECUTE is not blank / null  - It should first check
 VC>> it is not '' and only then issue the command.

 > There is a check, only the wrong variable is checked...

 > It's one of the bug fixes I sent in to the maintainer.

Got another bug :

Using the facility to send a msg for both cases of no errors and errors found,
the magic value %file% does not work here as there is just garbage in the
string passed to the utility selected - see log o/p :

--
14-Dec-2022 18:52:42 mbmsg[3402072] MBMSG v1.0.8
14-Dec-2022 18:52:42 mbmsg[3402072] Cmd: post "Vincent_Coen" 9 "Node Segment R
eport" /home/mbse/etc/makenl/0.000000ile
14-Dec-2022 18:52:42 mbmsg[3402072] Post "/home/mbse/etc/makenl/%file%" area 9
to "Vincent_Coen" flavor h
14-Dec-2022 18:52:42 mbmsg[3402072] Subject: "Node Segment Report"
14-Dec-2022 18:52:42 mbmsg[3402072] Can't open /home/mbse/etc/makenl/%file%: 
No
such file or directory
14-Dec-2022 18:52:42 mbmsg[3402072] Terminated with error 131
--

A later attempt is :

--
14-Dec-2022 18:57:21 mbmsg[3402325] MBMSG v1.0.8
14-Dec-2022 18:57:21 mbmsg[3402325] Cmd: post "Vincent_Coen" 9 "Node Segment
Report" 0.000000ile
14-Dec-2022 18:57:21 mbmsg[3402325] Post "%file%" area 9 to "Vincent_Coen"
flavor h
14-Dec-2022 18:57:21 mbmsg[3402325] Subject: "Node Segment Report"
14-Dec-2022 18:57:21 mbmsg[3402325] Can't open %file%: No such file or
directory
14-Dec-2022 18:57:21 mbmsg[3402325] Terminated with error 131
--

In this one the full path was not used as I 'assumed' it was the local
directory

For a valid one done manually it shows :

--
14-Dec-2022 19:00:12 mbmsg[3402520] MBMSG v1.0.8
14-Dec-2022 19:00:12 mbmsg[3402520] Cmd: post "Vincent_Coen" 9 "Node Segment
Report" net_25.rpt h
14-Dec-2022 19:00:12 mbmsg[3402520] Post "net_25.rpt" area 9 to "Vincent_Coen"
flavor h
14-Dec-2022 19:00:12 mbmsg[3402520] Subject: "Node Segment Report"
14-Dec-2022 19:00:12 mbmsg[3402520] Posted message 10
14-Dec-2022 19:00:12 mbmsg[3402520] MBMSG finished in  0.00s
--

The content of file errflags.ctl (having removed most comments) :

--
ZONE 2
NET 25
INBOUND /home/mbse/etc/makenl/outbound
FILE    region25.*      250/1   net_25.rpt
NOTIFY /home/mbse/bin/mbmsg post "Vincent_Coen" 9 "Node Segment Report" %file%
h
NOERR /home/mbse/bin/mbmsg post "Vincent_Coen" 9 "Node Segment Report" %file%
h
NOTIFYPATH /home/mbse/etc/makenl
;
; Key word EXECUTE states any program to execute if any files has been
; processed. This makes it possible for executing MakeNl only when files
; has actually been received.
;
; do not want to so attempt a simple command as blank may be causing the abort
;EXECUTE MAKENL.EXE REGION.CTL /P >> MAKENLOG.LOG
EXECUTE ls
--

Hope it helps,

The python code works though :)

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8/GoldED+/LNX 1.1.5-b20180707