Hello @Gerry Muyargas,
In addition to what Angus has said, you can also use uxshw tsk tsk=* output=<file>, to see how your uprocs/sessions are being scheduled. Not sure if that is what was meant by "job settings". Furthermore, from the UVMS CLI, you can export entire chains of jobs, including their internal scripts, into XML format using the 'uniadd topkg' and 'uniexp pkg' commands. Ex:
uniadd topkg -company <CMPANY> -node <nodename> -area X -login <UVMS login> -pwd <UVMS password> -full -pkg <package name>
https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/dollar-universe/7-00-11/Univiewer-Administrating/Commands/Packages/uniadd_TOPKG.html
uniexp pkg -pkg <package name> -login <UVMS login> -pwd <UVMS password> -xmlfile </path/to/fil>
https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/dollar-universe/7-00-21/Univiewer-Administrating/Commands/Packages/uniexp_PKG.html
Finally, as Angus alluded to, you can also find execution history by using some command line interface, like uxlst ctl (https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/dollar-universe/7-00-21/Command-Line-Interface/Operations_Commands_1/Executions.html). That said, you will be limited to 7 days of history or whatever retention period you have set for your node before purging.
For audit purposes, what is often important is execution history and possibly audit trail information (to see who took manual actions at what time). Given Dollar Universe's distributed architecture and relatively short retention period for this type of data, it is recommended to use a product like Reporter to store execution history over longer periods of time.
I hope this helps!
Regards,
Domenico Cotugno
Tricise Automation