Uvm_monitor and class parameter

In reply to verif_learner:

If you are saying you want to send out 2 different types of transactions, then you do not have 2 monitors of the same type.
I do not know how your UVM database is looking like, because a monitor belongs always to an agent, like the driver and the sequencer. The monitor in your agent1 has a specific transaction and the monitor in your agent2 has another transaction.