I assume you're referring to long running internally invoked CICS transactions? If you are, then you can monitor these, but.....
As these invariably run a long time Dynatrace will not hold a Pure Path open for that full duration, it will be timed out. Also the number of Nodes created in that Pure Path as in the " PurePath node limit: maximum number of nodes per CICS/IMS program call" will exceed the default value of 500.
Hi, if you do change that Node value be aware of the extra load it could cause. Not sure where the Pure Path time out is set or if there is one (I might be thinking of AppMon)
As for Batch CICS transactions all you should need to do is add the Transaction name or a naming pattern match to the Transaction Start Sensor setting.
Settings > Mainframe > Transaction start filters
Transactions that start on the mainframe, on a terminal, or are called by unmonitored services need to be explicitly listed in order to be monitored. This will allow to be picked up.
Today I sat with the Mainframe team to discuss this topic once again. They said, first off, these are not the CICS transactions but the batch jobs executed by IWS (IBM Workload Scheduler).
Also, they asked, if we can monitor SDSF Spool where the failed/succeeded batch jobs are stored.