Seeing this at logon time after implementing a new ARSUSECX -
Error message at logon
"The server failed while accessing folder data"
Error in the system log
"The userexit >/usr/lpp/ars/ed/exits/arsuperm< failed. The return code is -1"
If you have defined in your ars.cfg a custom location for exits, for example:
ARS_USER_EXITS_DIR=usr/lpp/ars/ed/exits/
And of course, there was no arsuperm in that directory of any kind.
But - if you have a modified ARSUSECX, ARSUSECX calls arsuperm and because of the config setting it will look for an arsuperm in that location.
Use SARSINST(ARSUPERJ) on sample exit SARSINST(ARSUPERM) to create member arsuperm in that directory.
After an arssockd recycle voila!, problem resolved.
So the net of it is that if you have a custom ARSUSECX you must ensure that your ARS_USER_EXITS_DIR is populated with an arsuperm.
Ed