NOTES:
sections that were commented out or omitted have some notes on reasoning in code comments:

Process status information relied on ProcMon/ProcMgr heavily and processes status and pid information can be collected by scraping logfiles so this was omitted.

ModuleResourceUsage information seems of little use and was not ported from ProcMon/ProcMgr messaging. this could be done if someone deems it necessary

getActiveSQL statements functionally just scrapes the log file and can be done manually with log files. did not port.

dbms collection commands were moved to a shell script matching pattern of other report types.

there was something called databaseSizeReport that did nothing so it was commented out.

cnf and xml files were written to files via cat. now they are included in tarball as a separate copy of the configuration file.

Re-assigning to me so that storagemanager.cnf can be added with customer keys scrubbed.

What is this tool and how do I run it?

[test@localhost ~]$ columnstoreSupport -h

'columnstoreSupport' generates a Set of System Support Report Files in a tar file
called columnstoreSupportReport.'system-name'.tar.gz in the local directory.
It should be run on the server with the DBRM front-end.
Check the Admin Guide for additional information.

Usage: columnstoreSupport [-h][-a][-hw][-s][-c][-db][-r][-l][-bl][-lc][-p 'root-password'][-de]
-h help
-a Output all Reports (excluding Bulk Logs Reports)
-hw Output Hardware Reports only
-s Output Software Reports only
-c Output Configuration/Status Reports only
-db Output DBMS Reports only
-r Output Resource Reports only
-l Output Columnstore Log/Alarms Reports only
-bl Output Columnstore Bulk Log Reports only
-lc Output Reports for Local Server only
-p password (multi-server systems), root-password or 'ssh' to use 'ssh keys'
-de Debug Flag

Build tested: 1.5.3-1 first build from staging server
commit: 20e131299ded9fa090cad34e62c6287672c6f0cb

Test on single server installation only. Multiple-node installation is not yet available.

Passed.

Need to retest for multi-node configurations when available.

Only single node is supported in 1.5.3