Getting a handle on the RVMLOGGINGLEVEL argument and violation-counts file

[ayakayorihiro]

Currently, we are assuming that export RVMLOGGINGLEVEL=UNIQUE has been set before emop is run. VMS and RPP also assume that the violation-counts file is stored in a specific location, and moves the file accordingly. However, in the future we should have emop (VMS/RPP) get a handle on javamop such that they automatically set RVMLOGGINGLEVEL and the location where the violation-counts file should be written to.