The syntax I used was the one you were using in your post of the "January 30, 2017, 06:44:07 AM". I did only a copy paste.
Now, this is a user exit is a public "hook" from CMOD. So if you want to test it, or use it, you cannot run it.
It will also never work (since there are no main method) as you have seen with the core dump output.
You need to add arsusec in the directory "${CMOD_INSTALL_DIR}/bin/exits" (check the permissions 755), and add in the ars.ini the line SRVR_FLAGS_SECURITY_EXIT=1 as you already did correctly.
Then you can restart CMOD and test it.
At my knowledge, you can only test it with a CMOD server...
When I was doing my user exit development, I was always doing that:
1) Stop CMOD Development
2) Replace the user exit
3) Start CMOD Development
4) Test what I wanted to test
5) If CMOD crashed, then I did something wrong, correct, and restart from step 1)
6) If CMOD didn't crash, then I check that everything I wanted was working, and if not, correct it, and back to step 1)
7) If everything worked as expected, then I could prepare to exit to test in the CMOD test system, that everything works as expected also there... if not, correct it, and back to step 1)
If the test phase was successfully performed, then the next step was to implement it in production, with full documentation on how to deploy it.
Hope that helps on how to develop, test these very special CMOD components.
