Unfortunately, it is not possible to run the reports from the command line at this time. I was able to write a PowerShell script that approximates this functionality; you can find it over on my GitHub repository with basic instructions.
Given a LOG file to search for, it will discover the FAPs which reference the LOG, and FORs which reference those FAPs. Output is given to a file like this, and indicates the FAP and FOR references with version/revision details:
Search for CEOSIG (LOG) started on Friday 10/11/2019 17:07
CEOSIG located in SIGNATURE JONES (00001.00001)
SIGNATURE JONES located in:
AM-472 (FOR) 00001.00001
AM-LI-9642 (FOR) 00001.00001
LI-529 (FOR) 00001.00001
LIFE WELCOME (FOR) 00001.00001
LIFE-WELCOME (FOR) 00001.00001
MI-2876 (FOR) 00001.00001
PA-5921 (FOR) 00001.00001
UL APPLICATION REJECTION NOTICE (FOR) 00001.00001
UL APPLICATION RESPONSE (FOR) 00001.00001
Finished on Friday 10/11/2019 17:07
Hope this helps!
I'm not sure how I missed this reply earlier, but I finally saw it at the end of the day yesterday. It took a little bit for me to figure out how to configure it for our environment but once I had that setup it works like a charm! Thanks so much for this!