arsmaint can be run with the following parm:
-v
Validates cache storage. When you specify this option, the ARSMAINT program inspects all cache storage file systems to make sure that they are correctly linked with the proper file permissions.
I run it in batch on z/OS with the following JCL:
//TMP1 EXEC PGM=IKJEFT01,
// DYNAMNBR=200
//SYSPROC DD DSN=SYS1.SBPXEXEC,DISP=SHR
//*
//SYSTSPRT DD SYSOUT=*
//*
//SYSTSIN DD *
oshell /usr/lpp/ars/V8R4M0/bin/arsmaint -v -I ARCHIVE
//*
Note: on z/OS at least - the output does not go in the job. Rather the output will show up in the ARSSOCKD started task.
If there is no problem, there is no output.
If there is, you can expect to see a message like this in the JESMSGLG:
ARS0198E ARSMAINT INVALID OWNERSHIP AND/OR PERMISSIONS ON CACHE FILE
/DIRECTORY >/ARS2< SRVR->MAGENTA.ZOS.FOO.COM 9.29.129.129<-
Warning - can be rather I/O intensive, try it on a test system first or run it off-shift.